[ https://jira.jboss.org/jira/browse/JBWS-2775?page=com.atlassian.jira.plug... ] Hans Guldager Knudsen updated JBWS-2775: ---------------------------------------- Attachment: jboss_1_create_sequence.txt jboss_2_payload_request.txt Attaching log of CreateSequence (Request) and CreateSequenceResponse Payload request - and Paylod response -- 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-2775?page=com.atlassian.jira.plug... ] Hans Guldager Knudsen updated JBWS-2775: ---------------------------------------- Attachment: metro_4_terminate_squence.txt Attach Metro Terminate Sequence -- 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-2775?page=com.atlassian.jira.plug... ] Hans Guldager Knudsen updated JBWS-2775: ---------------------------------------- Description: Hi! I tried to use the JBoss-native WS-RM client - but it seems that WS Addressing is not applied correctly. I tried following the tuturial at : http://www.jboss.org/community/wiki/JBossWS-NativeWS-ReliableMessagingTut... also present as testcase in modules/testsuite/native-tests/src/test/java/org/jboss/test/ws/jaxws/samples/wsrm When Using the JBoss WS RM client 1. SOAPAction is not set on the HTTP Request - for both CreateSequnece + Payload 2. On CreateSequnece - WSA Action is not the Payload request Action but : <wsa:Action>http://docs.oasis-open.org/ws-rx/wsrm/200702/CreateSequence... and therefor invocation failes. My Service is running on SUN's Metro. I will attach logs from my HTTP monitor from JBoss + SUN's Metro - to show the differences - invoking the 'echo' method. was: Hi! I tried to use the JBoss-native WS-RM client - but it seems that WS Addressing is not applied correctly. I tried following the tuturial at : http://www.jboss.org/community/wiki/JBossWS-NativeWS-ReliableMessagingTut... also present as testcase in modules/testsuite/native-tests/src/test/java/org/jboss/test/ws/jaxws/samples/wsrm When Using the JBoss WS RM client 1. SOAPAction is not set on the HTTP Request - for both CreateSequnece + Payload 2. On CreateSequnece - WSA Action is not the Payload request Action but : <wsa:Action>http://docs.oasis-open.org/ws-rx/wsrm/200702/CreateSequence... My Service is running on SUN's Metro. I will attach logs from my HTTP monitor from JBoss + SUN's Metro - to show the differences - invoking the 'echo' method. -- 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-2775?page=com.atlassian.jira.plug... ] Richard Opalka updated JBWS-2775: --------------------------------- Fix Version/s: jbossws-native-3.2.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

[ https://jira.jboss.org/jira/browse/JBWS-2775?page=com.atlassian.jira.plug... ] Richard Opalka updated JBWS-2775: --------------------------------- Summary: WSRM Client does not apply WS-Addressing correctly (was: WSRM Client does apply WS-Addressing correctly) Fix Version/s: (was: jbossws-native-3.2.1) Affects Version/s: (was: jbossws-native-3.2.0) -- 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-2775?page=com.atlassian.jira.plug... ] Hans Guldager Knudsen updated JBWS-2775: ---------------------------------------- Affects Version/s: jbossws-native-3.2.1 Description: Hi! I tried to use the JBoss-native WS-RM client - but it seems that WS Addressing is not applied correctly. I tried following the tuturial at : http://www.jboss.org/community/wiki/JBossWS-NativeWS-ReliableMessagingTut... also present as testcase in modules/testsuite/native-tests/src/test/java/org/jboss/test/ws/jaxws/samples/wsrm When Using the JBoss WS RM client 1. SOAPAction is not set on the HTTP Request - for both CreateSequnece + Payload 2. On ** Payload Request ** - WSA Action is not the Payload request Action but : <wsa:Action>http://docs.oasis-open.org/ws-rx/wsrm/200702/CreateSequence... and therefor invocation failes. My Service is running on SUN's Metro. I will attach logs from my HTTP monitor from JBoss + SUN's Metro - to show the differences - invoking the 'echo' method. was: Hi! I tried to use the JBoss-native WS-RM client - but it seems that WS Addressing is not applied correctly. I tried following the tuturial at : http://www.jboss.org/community/wiki/JBossWS-NativeWS-ReliableMessagingTut... also present as testcase in modules/testsuite/native-tests/src/test/java/org/jboss/test/ws/jaxws/samples/wsrm When Using the JBoss WS RM client 1. SOAPAction is not set on the HTTP Request - for both CreateSequnece + Payload 2. On CreateSequnece - WSA Action is not the Payload request Action but : <wsa:Action>http://docs.oasis-open.org/ws-rx/wsrm/200702/CreateSequence... and therefor invocation failes. My Service is running on SUN's Metro. I will attach logs from my HTTP monitor from JBoss + SUN's Metro - to show the differences - invoking the 'echo' method. Change initial descripiton -- 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