|[equinox-dev] Component Resolve Thread and the context classloader|
I’m working on a system that makes heavy use of Declarative Services. In troubleshooting some classloading problems, we’ve noticed that the Component Resolve Thread (backed by the Executor class) sets the context classloader to be null.
This seems to cause problems with Swing and other systems that make use of the context classloader (Esper was the source of our problems).
Is there a reason that this is set as it is? If so, what might be a good work-around?
THIS MESSAGE IS INTENDED FOR THE USE OF THE PERSON TO WHOM IT IS ADDRESSED. IT MAY CONTAIN INFORMATION THAT IS PRIVILEGED, CONFIDENTIAL AND EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW. If you are not the intended recipient, your use of this message for any purpose is strictly prohibited. If you have received this communication in error, please delete the message and notify the sender so that we may correct our records.