[jbossws-issues] [JBoss JIRA] Updated: (JBWS-2155) Not supporting JMS endpoints for WS-Addressing
[ http://jira.jboss.com/jira/browse/JBWS-2155?page=all ]
Zach Mabe updated JBWS-2155:
----------------------------
Attachment: SOAPConnectionImpl.java
I am attaching an updated the SOAPConnectionImpl which will create the RemoteConnection
based on the endpoints schema. I've seen some other code within the source that just
uses the startsWith on the string as opposed to actually converting it to a uri and
getting the schema.
If the endpoint address starts with jms, it will construct a new
org.jboss.ws.core.client.SOAPProtocolConnectionJMS, otherwise, it falls back to the
org.jboss.ws.core.client.SOAPProtocolConnectionHTTP
Not supporting JMS endpoints for WS-Addressing
----------------------------------------------
Key: JBWS-2155
URL: http://jira.jboss.com/jira/browse/JBWS-2155
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: ws-addressing, jbossws-native
Affects Versions: jbossws-native-3.0.1
Environment: JBoss 4.2.2.GA, Windows XP, Sun JVM 1.5.0_08
Reporter: Zach Mabe
Attachments: SOAPConnectionImpl.java
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira