At 21:04 09/11/2006, Hawkins, Joel wrote:
@Nicole: Accessing the classloader corresponding to a particular bundle. It's a back-door cheat like the Declarative Services guys use, and its very implementation-specific. Plus it's nice to have a place to isolate implementation-specific stuff. :-)
The OSGi guys are very receptive to OSGi extensions that might need to be included in future releases. In Spring-OSGi we realized the need to access the BundleContext from the Bundle and for having an appropriate ContextClassLoader set when performing framework operations.
In Spring-OSGi we didn't actually need to access the classloader since we wrote a BundleDelegatingClassloader that deferred to the Bundle. It would be good to know what use cases require this feature.
andy
_______________________________________________________________________ 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. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
