[jsr-291-eg] Use of the system classloader
andyp at bea.com
Tue Aug 15 06:01:16 EDT 2006
Our internal uses of OSGi have come across a number of use cases
where Java SE relies on the system classloader for loading resources
of various types. One example is JNDI factories. Unfortunately this
creates problems when trying to load these resources from OSGi
bundles. OSGi has already solved this problem with the URL Handler
Service. This service makes it possible to register URL handlers from
OSGi bundles, so that there's a way to load them other than by
putting them in the system class path.
We would like this issue to be addressed uniformly across Java SE.
For JNDI this could be solved by providing our own factory
implementation, I'm not sure whether this mechanism would so readily
apply to other scenarios however.
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary, copyrighted and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.
More information about the jsr-291-eg