Using Jax-WS RI with JBoss AS 4.2.2?

[pisce]

Hello all,

I have a simple question. How do you make an EAR app (EJB endpoints) work with Jax-ws RI on JBoss AS 4.2.2, instead of (or in collaboration with) JBossWs?

I tried to remove 'jbossws.sar' from server/default/deploy, and ship Jax-ws RI 2.1.4's jars into my EAR's /lib directory. JBoss AS seems to hot-deploy fine, but the Endpoint is never registered, and the WSDL is never published. I guess I could need several descriptors that are located in 'jbossws.sar', but they all refer to JBossWs beans...

If I ship Jax-ws RI's jars into my EAR, and don't remove 'jbossws.sar', I get weird errors probably due to conflictual jars versions.

Any help is welcome

[asoldano]

You can't change the webservice stack that way, at least it's not that simple. Since JBossWS 3.0 we however support the Metro (jaxws RI) stack, see http://jbws.dyndns.org/mediawiki/index.php?title=WSF.
In short, simply download the latest jbossws-metro-3.0.2, install it and you're ready to go with your jaxws-ri based application.