[jbossws-issues] [JBoss JIRA] Commented: (JBWS-2724) JBossWS-Native WSRM Server does not set Accept.AckstTo.Address on CreateSequenceResponse
[
https://jira.jboss.org/jira/browse/JBWS-2724?page=com.atlassian.jira.plug...
]
Hans Guldager Knudsen commented on JBWS-2724:
---------------------------------------------
btw..
we also have to be able to handle custom soap header - which at first look was not present
when using 'Native' - but I will follow up on this when I get time - and report a
bug if necessary....
otherwise the profile looks something like :
wsdl 1.1
soap 1.1
wsa 1.0
ws-rm 1.1
+ custom headers...
eventually we also have to handle SSL transport
and
SAML tokens..
/hans
JBossWS-Native WSRM Server does not set Accept.AckstTo.Address on
CreateSequenceResponse
----------------------------------------------------------------------------------------
Key: JBWS-2724
URL: https://jira.jboss.org/jira/browse/JBWS-2724
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: jbossws-native, ws-reliable
Affects Versions: jbossws-native-3.1.2
Reporter: Hans Guldager Knudsen
Assignee: Richard Opalka
Fix For: jbossws-native-3.2.0
Attachments: jbossws_native_cs_response_acks_to.txt
Trying to interact with at JBossWS-Native WS-RM enabled endpoint using
- MS WCF and Sun Metro 1.4/1.5 clients
I noticed that 'native' wsrm server does/can not set the Accept.AckstTo.Address
on CreateSequenceResponse.
--
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