[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[equinox-dev] Use of Thread Context ClassLoader considered harmful?
- From: "Michael Furtak" <mfurtak@xxxxxxx>
- Date: Tue, 6 Oct 2009 13:51:59 -0400
- Delivered-to: email@example.com
- Importance: normal
- Priority: normal
- Thread-index: AcpGrbOjknQ4bcE+S9GO9ROmOwcHog==
- Thread-topic: Use of Thread Context ClassLoader considered harmful?
I am using Apache XMLBeans 2.4 within Equinox 3.5, and am running into
problems. Specifically, I (and others [1,2] - references at bottom) have
noticed that a specific part of the type resolution process breaks when
run in an OSGi environment.
After some investigation, I have found that XMLBeans is creating its
SchemaTypeLoader objects with the current thread's context
classloader. My experience has been that any time a library does this
and then needs to load classes that are in a different OSGi bundle, the
classes can not be resolved.
So I suppose my questions are: Could Equinox do more to prevent this
kind of use-case from breaking down? Alternatively, for compatibility
with an OSGi environment, is using a TCCL considered harmful? If so,
what should I suggest in my XMLBeans ticket as an OSGi-compatible
emaTypeLoaderImpl.getContextTypeLoader%28%29 (Line 131)
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.