In case of wiring, I suggest you build a web application bundle by
yourself.
This way you make sure you have the right import packages.
But you might also add these during the
osgi:install as parameters.
like
osgi:install
mvn:xxx.war/version?Web-ContextPath=/myPath&Import-Package=external.package
regards, Achim
Am 03.06.2011 14:26, schrieb Scott Parkerson:
On Thu, Jun 2, 2011 at 5:42 PM, Achim Nierbeck<[email protected]> wrote:
if you want to convert it into a OSGi compliant WAB (Web-Application-Bundle)
you need to add a Web-ContextPath to the Manifest.
But you might drop it into the deploy folder as a standard war. Pax Web does
take
care of it then.
You shouldn't need a specialized Activator.
Can Pax Web wire the bundle's classpath to other bundles? Or do I need
a fat WAR with all of the dependencies?
Also, are there any issues that I'll run into when using an older
version of Pax Web (circa 0.7.2, as packaged in FUSE ESB 4.2?)
--sgp
