ok, I'll try with jbossws native 3.4.1 as soon as it is available.
in the mean time, I tried to declare the handler like that:
@HandlerChain(file = "handler-chain.xml")
and I get:
DEPLOYMENTS IN ERROR:
Deployment "vfs:///home/abr/workspace/api/dist/ubi-api.ear" is in error due to the following reason(s): javax.xml.ws.WebServiceException: Could not find the handler configuration file handler-chain.xml specified by @HandlerChain annotation
so next I tried:
@HandlerChain(file = "/handler-chain.xml")
and I get:
DEPLOYMENTS IN ERROR:
Deployment "vfs:///home/abr/workspace/api/dist/ubi-api.ear" is in error due to the following reason(s): javax.xml.ws.WebServiceException: false false Element <?xml version="1.0" encoding="utf-8"?><handler-config>
<handler-chain>
<handler-chain-name>SoapHandler</handler-chain-name>
<handler>
<handler-name>SoapMessageValidationHandler</handler-name>
<handler-class>com.ubiqube.api.ws.soapHandler.MessageValidationSoapHandler</handler-class>
</handler>
</handler-chain>
</handler-config> is not a valid root element in file vfs:/home/abr/workspace/api/dist/ubi-api.ear/ubi-api-ejb.jar/handler-chain.xml
So with CXF 3.4.1the "/" must be there, wheras with native 3.4.0 it was not necessary (note that I did not try with the / and native 3.4.0).
Do you know when the jbossws native 3.4.1 will be available for download?
Another question, maybe you can point me to some doc: why choosing jbossws CXF against native? Is it a certification issue?
Thank you for your time and answer
Antoine