Is there really nobody calling web services with JAX-WS from an OSGi bundle in JBoss 7.1.1? I thought this would be a common problem.

Anybody?

Hi Thomas, thanks for replying.

Just to be clear, I'm not trying to deploy a web service implementation as an OSGi bundle, merely a web service client.

This works on JBoss AS 7.0.2 - are you saying this is no longer posisble on 7.1.1 until the attached JIRA (which seems to refer to service implementations) are resolved?

I'm happy to build a test for you, I just want to be clear about the distinction.

kind regards,

Dawid

Of course, in addition to the missing JAX-WS libraries, I am also missing the JAXB librarfies (upon which JAX-WS depends), hitting lots of instances of:

• java.lang.NoClassDefFoundError: javax/xml/bind/JAXBElement

If somebody could give me a quick indication whether I should be sourcing this javax.* stuff from JBoss-provided libraries, or whether I should imagine I'm running plain Felix (and provision them all manually from, say, CXF, which I imagine might cause problems when I exchange JAX-WS or JAXB types between my Java EE and OSGi bundles...) that'd be great.

As mentioned before, the old (in 7.0.2) "javaee.api" capability provided this for me. Whatever I replace it with, needs to be such that it's the same classes that my Java EE modules use (as they exchange objects).

kind regards,

Dawid

Hi All,

Is there really no way to make web service calls from an OSGi bundle in the latest JBoss release (7.1.1)? This is a critical issue preventing us from upgrading our systems still running on 7.0.2.

Surely somebody else must have encountered the need to access javax.xml.ws (JAX-WS) or javax.xml.bind (JAXB) etc from within your OSGi bundles? If somebody could please clarify how my question relates to https://issues.jboss.org/browse/AS7-5364  (which is not the same thing, I simply want to make calls to a web service as a client, not expose a web service)

thanks,

Dawid

Ah, thank you so much for the update, Thomas.

If this gets merged into JBoss master soon, any ideas when it will find its way into a release?

(I don't think I can run a random build from master in production :-)

Would you mind providing a 10-second explanation of what the fix entails?

Will this ultimately enable me to simply expose JAX-WS/JAXB as a capability in my jboss configuration?

JAX-WS has a direct dependency on JAXB, so I doubt that your test cases could pass if JAXB was not exposed also?

I'm happy to add some tests for you, do I just fork OSGi smoke and add a test, and send a pull request?