Don,
I think there is some confusion. The framework, and subsequently main,
do embed the needed OSGi core and compendium classes. The only thing you
need to run Felix, is felix.jar (which is actually
org.apache.felix.main-1.x.x.jar).
Maybe you have the OSGi classes on your class path twice?
-> richard
Don Brown wrote:
We got the puzzling exception:
Caused by: java.lang.NoClassDefFoundError: org.osgi.vendor.framework
property not set
at
org.osgi.framework.FrameworkUtil$ImplHolder.run(FrameworkUtil.java:69)
in one of our integration builds for Resin, but not on any of the
other app servers. Turns out the Felix framework jar "overrides"
several OSGi classes from the osgi core jar, and apparently, Resin
loads the classes differently then other app servers.
I'm a bit puzzled as to why this design would even work in the first
place. How could you ensure that app servers would load the felix
overrides before the osgi core classes? Shouldn't the osgi core jar,
instead, be folded into the framework jar so there are no such
uncertainties?
Don
---------------------------------------------------------------------
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]
