[JBoss JIRA] Created: (JBWS-2724) JBossWS-Native WSRM Server does not set Accept.AckstTo.Address on CreateSequenceResponse
4:12 a.m.
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
Reporter: Hans Guldager Knudsen
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
4:21 a.m.
New subject: [JBoss JIRA] Updated: (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 updated JBWS-2724:
----------------------------------------
Attachment: jbossws_native_cs_response_acks_to.txt
An example of setting the AcksTo Address..
There might have to be some check if the AcksTo should be set or not...
eg for OneWay it might not be needed
but for req/resp it should be there
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
Reporter: Hans Guldager Knudsen
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
3:52 a.m.
New subject: [JBoss JIRA] Updated: (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...
]
Richard Opalka updated JBWS-2724:
---------------------------------
Fix Version/s: jbossws-native-3.2.0
Affects Version/s: jbossws-native-3.1.2
Assignee: Richard Opalka
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
4:34 a.m.
New subject: [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:
---------------------------------------------
Hi!
We have a setup running with AS-5.1+ESB4.6 using the JBossWS-Metro stack - so for now this
is ok...
In the wsdl :
<wsaw:UsingAddressing wsdl:required="true"/>
has been defined - therefor clients (at least WCF) expects that the WSA-Actions specified
are used..
Right now JBossWS-Native does not support UsingAddressing :
https://jira.jboss.org/jira/browse/JBWS-2458
I have not had time to look at how the JBossWS-Native acts as a client.
/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
6:10 a.m.
New subject: [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
5566
days inactive
5568
days old
jbossws-issues@lists.jboss.org
4 comments
2 participants
participants (2)
-
Hans Guldager Knudsen (JIRA) -
Richard Opalka (JIRA)