[ http://jira.jboss.com/jira/browse/JBWS-2102?page=all ] Thomas Diesler updated JBWS-2102: --------------------------------- Component/s: jbossws-integration -- 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

[ http://jira.jboss.com/jira/browse/JBWS-2102?page=all ] Thomas Diesler updated JBWS-2102: --------------------------------- Fix Version/s: jbossws-3.0.2 -- 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

[ http://jira.jboss.com/jira/browse/JBWS-2102?page=comments#action_12409940 ] Richard Opalka commented on JBWS-2102: -------------------------------------- Users have to use: * javax.xml.ws.Action instead of javax.xml.ws.addressing.Action * javax.xml.ws.FaultAction instead of javax.xml.ws.addressing.FaultAction See https://jax-ws.dev.java.net/jax-ws-21-ea3/docs/wsaddressing.html Both javax.xml.ws.Action and javax.xml.ws.FaultAction are available in JBossWS-Metro integration. -- 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

[ http://jira.jboss.com/jira/browse/JBWS-2102?page=all ] Richard Opalka reopened JBWS-2102: ---------------------------------- Right, we need to verify that Addressing api is provided by Metro runtime too. -- 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

[ http://jira.jboss.com/jira/browse/JBWS-2102?page=comments#action_12410493 ] Andrew Dinn commented on JBWS-2102: ----------------------------------- Well, that's maybe what the blog entry says but is it actually what the JaxWS committee have decided? Have you asked Thomas Diesler (since he is JBoss' representative) whether this is the official position of the committee? Personally, I think this decision makes provision of the WS Addressing capability in JaxWS utterly pointless. JaxWS might just as well not bother attaching WS Addressing headers to messages if there is no simple API for clients/SEIs to set/detect the header values. If they have to resort to installing SOAP handlers to do this then they might as well either i) implement WS Addressing themselves or ii) invent their own (simpler) custom header protocol. The latter is not an option for me as the WSTX specs I am working to require WS-Addressing headers with quite specific values. So, if this is a final decision then it means I will have to provide my own implementation of the JBossWS AddressingProperties class and associated handlers and ensure it runs on all 3 stacks -- a pointless fork of the code. -- 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

[ http://jira.jboss.com/jira/browse/JBWS-2102?page=comments#action_12410524 ] Andrew Dinn commented on JBWS-2102: ----------------------------------- My requirement is to be able both to set headers in the client and detect them in the SEI. Specifically, I need to be able to associate pairs of asynchronous (OneWay) messages by setting the MessageId in the outgoing message and using it to populate the RelatesTo list in the response message. The SEI which handles the outgoing message retrieves the MessageId and passes it to a local client. This client subsequently sends either a response or an error to an SEI on the original client side. This passes the result and the RelatesTo list back to the original client, allowing the relationship between the two messages to be established. I cannot pass these values in the message body because the WSTX specs require them to be passed using WSA headers. I also need to specify ReplyTo and FaultTo in the outgoing message so that I can correctly route the returning message/error as appropriate. The ReplyTo in the response message is required by the spec to be set to address None. So, to implement this using SOAP handlers I will need an addressing properties datatype located on the MessageContext in order to communicate the values to the client handler and to propagate the values form the service handler to the SEI. The handlers will have to read thsi value and populate WSA soap headers on the client side and read/remove them on the server side installing them into the addressing properties. In other words I'll need to fork exactly what you already have in JBossW and make it part of the JBossTS code. -- 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

[ http://jira.jboss.com/jira/browse/JBWS-2102?page=all ] Richard Opalka updated JBWS-2102: --------------------------------- Fix Version/s: (was: jbossws-metro-3.0.3) -- 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

[ https://jira.jboss.org/jira/browse/JBWS-2102?page=com.atlassian.jira.plug... ] Richard Opalka updated JBWS-2102: --------------------------------- Assignee: (was: Richard Opalka) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBWS-2102?page=com.atlassian.jira.plug... ] Alessio Soldano commented on JBWS-2102: --------------------------------------- Andrew kindly pointed me to the source code of what he did for this in WS-TX project. See: https://svn.jboss.org/repos/labs/labs/jbosstm/workspace/adinn/wsbrew Apart from some minor clean up, this should work and fill in this gap in terms of features. Where this has to leave is still to be evaluated (most probably the jbossws-metro integration). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBWS-2102?page=com.atlassian.jira.plug... ] Alessio Soldano updated JBWS-2102: ---------------------------------- Fix Version/s: jbossws-metro-3.0.6 (was: jbossws-metro-3.0.5) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBWS-2102?page=com.atlassian.jira.plug... ] Alessio Soldano updated JBWS-2102: ---------------------------------- Fix Version/s: (was: jbossws-metro-3.1.1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira