Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ObjectInputStream getting wrong classloader #806

Open
Thrameos opened this issue Jul 20, 2020 · 0 comments
Open

ObjectInputStream getting wrong classloader #806

Thrameos opened this issue Jul 20, 2020 · 0 comments
Labels
bug Unable to deliver desired behavior (crash, fail, untested)

Comments

@Thrameos
Copy link
Contributor

It appears that ObjectInputStream is caller sensitive but is not marked as such. If you manually create an ObjectInputStream and then use it to read objects from a jar loaded in the class path it will fail with class not found even through the class is clearly available. If the same calls are made from a class called from JPype which just adds an intermediate layer, the same calls work.

This will require a special catch for this one constructor. Not sure how much effort to put on this one.

@Thrameos Thrameos added the bug Unable to deliver desired behavior (crash, fail, untested) label Jul 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Unable to deliver desired behavior (crash, fail, untested)
Projects
None yet
Development

No branches or pull requests

1 participant