Wildfly 9 using Metro for JAX-WS.

nucahx Nov 20, 2015 12:43 PM

All,

We are evaluating a move from Glassfish to Wildfly as our EE application server of choice. However I cannot get our Soap Client implementation to work due to the dependency on Metro. Most of these issues can be fixed with code, however one issue in particular with custom SSL connections in CXF I cannot seem to crack. I would like to solve it without explicit dependencies on CXF libraries if at all possible. I am willing to hammer on the CXF problem to find a solution, but I was wondering if anyone have successfully used Metro as their JAX-WS stack in WF.

Thanks in advance,

Marlin

1. Re: Wildfly 9 using Metro for JAX-WS.

ctomc Nov 23, 2015 7:24 AM (in response to nucahx)

You can use metro or any other WS stack as part of your deployment.
Just make sure you disable webservices subsystem and bundle whole metro as part of your deployment.
Actions
2. Re: Wildfly 9 using Metro for JAX-WS.

a.bader May 12, 2016 2:46 AM (in response to ctomc)

Dear Tomaz

I have a similar question: I have Wildfly 8 and I should be able to use JAX-WS RI reather than Apache CXF (I do need only WebService client; I have no WebService endpoints to serve). I deactivated the webservices subsystem in my standalone.xml but still apache cxf is used as JAX-WS client. What can I do?

You may probably also have a look at my full problem: http://stackoverflow.com/questions/37158821/wildfly-how-to-use-jaxws-ri-instead-of-apache-cxf-webservice-client-only
Actions

Go to original post