Luke Patterson wrote:
On Thu, Jan 29, 2009 at 3:10 PM, Richard S. Hall <[email protected]> wrote:
Patrick Forhan wrote:
Note that a bundle is simply a JAR file with extra metadata. A
non-osgi container can use them as-is. To that end, when we have
bundles that end up on a server, we simply leave them as bundles and
add them to the classpath or WAR, etc that is deployed.
Keep in mind that a normal JAR file is always a bundle, but a bundle is not
always a normal JAR file. If you embed JAR files or native libraries in your
bundle, then you cannot use it as a normal JAR file.
If you add the same JARs that are embedded to the assembly, it should
work fine right? Granted, you would have bloat with the duplication,
but the mere presence of embedded JARs wouldn't prevent running in
non-OSGi, correct?
That is correct...you'd have to manually resolve any dependencies it has
from its Bundle-ClassPath or Bundle-NativeLibrary.
-> richard
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
