On 07/16/2009 03:18 PM, Kris Pruden wrote:
On Jul 16, 2009, at 7:03 AM, Richard S. Hall wrote:
It looks like I could make it work cleanly (from the client bundle
implementors' perspective anyway) by putting the cglib code in a
"bootclasspath" extension fragment. Is this what you were referring
to by "boot delegation?"
I don't think any framework implements the boot class path extension
fragment, but yes that would be the approach. In absence of that, I
was referring to adding the packages to the app class path when
launching and setting the org.osgi.framework.bootdelegation property
to include the package. If you are using trunk, you will also need to
set org.osgi.framework.bundle.parent=app, which is part of the new
standard launching and embedding API for R4.2.
Hm, thanks for the info. I'll have to give some thought into which
option I dislike the least :)
Out of curiosity: I know the the boot class path extension feature is
not required by the spec, but are there any plans to provide that
feature in felix?
It is more a feature of a launcher, not the framework, probably, but I
haven't given too much thought about how it would be implemented.
I don't see it on the horizon, but never say never. :-)
-> richard
-> richard
Thanks again,
Kris
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
