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

Set thread contextClassLoader to the one from the bundle when activating a bundle #7

Open
pierre opened this issue Apr 24, 2015 · 2 comments

Comments

@pierre
Copy link
Member

pierre commented Apr 24, 2015

See #5.

@pierre pierre added this to the Release-0.2.0 milestone Apr 24, 2015
@sbrossie
Copy link
Member

Unfortunately this is not solvable because we don't have the class loader available before we start the bundle (and enter the Felix machine), and when we hit the start method from the activator, this is too late-- we are already in the plugin.

Looks like the solution is to set that context class loader in the plugin itself but that requires to be done in each plugin (or at least the subset that need it for their start sequence to happen correctly).

There is a SO thread on that topic (http://stackoverflow.com/questions/2198928/better-handling-of-thread-context-classloader-in-osgi)

@pierre
Copy link
Member Author

pierre commented Apr 29, 2015

Looks like the solution is to set that context class loader in the plugin itself but that requires to be done in each plugin (or at least the subset that need it for their start sequence to happen correctly).

For reference, the only plugin that requires it today is Forte.

@pierre pierre removed this from the Release-0.2.0 milestone Jun 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants