-
Bug
-
Resolution: Done
-
Major
-
jbossws-native-3.0.1
-
None
when using a JMS endpoint at the EPR for either the faultTo or ReplyTo address within the WS-Addressing headers, the server always fails with the message
ClassNotFound org.jboss.remoting.transport.jms.TransportClientFactory.
How the faultTo is set on the client side
AddressingProperties props = (AddressingProperties) reqContext.get(JAXWSAConstants.CLIENT_ADDRESSING_PROPERTIES);
EndpointReference ep =ADDRESS_BUILDER.newEndpointReference(new URI("jms://queue/WSDropQueue"));
props.setFaultTo(ep);
This issue seems to be rooted in the fact that, on the server side, when the org.jboss.ws.core.soap.SOAPConnectionImpl is called to send the response/fault, it uses a org.jboss.ws.core.client.SOAPProtocolConnectionHTTP which in turns uses the JBoss-Remoting client which doesn't provide JMS support.