[ffang]

Hi,

You can OSGi-fied jbossall-client.jar using mvn-bundle-plugin in pom.xml to get more control of package export version, it's more flexible then using wrap.

Take a look at what we do it for lots of non-osgi jars in smx bundle repo[1]

https://svn.apache.org/repos/asf/servicemix/smx4/bundles/trunk/

Freeman

[yusuf.jakoet]

almost there...

created a pom.xml for jbossall-client.

if i get missing contraints when i try to start the jbossall-client bundle, would i just add the missing package to <servicemix.osgi.import.pkg>?

Thanks

[ffang]

Hi,

Yes. As servicemix.osgi.import.pkg property is actually used in bundles-pom/pom.xml[1] for the maven-bundle-plugin, which you can used as parent of your bundle pom.

Or you can configure import-package directly on maven-bundle-plugin in your own bundle pom.

https://svn.apache.org/repos/asf/servicemix/smx4/bundles/trunk/bundles-pom/pom.xml

Freeman

[yusuf.jakoet]

Hi

Are wildcards supports in the imports section of the pom file?

This is turning out to be a painstakingly slow process because my wildcards don't seem to work...  They do work in the export section however...

Ideas?

[solly]

has anyone solved the issue?

[ranthyreddy]

Hi,

Wondering if you ever got around to solving this issue with EJB + SMX (OSGi) stuff.

If so, could you post your solution, as I am using FUSE-4.4.1 currently and have a need to invoke an EJB2.x from within OSGI Web Service.

thanks a lot,

RR.