[JBoss JIRA] Created: (JBWS-2430) WS-RX: Anonymous client that offers a sequenceId should not be rejected (sequenceId should be disregarded instead)
10:57 a.m.
WS-RX: Anonymous client that offers a sequenceId should not be rejected (sequenceId should
be disregarded instead)
------------------------------------------------------------------------------------------------------------------
Key: JBWS-2430
URL: https://jira.jboss.org/jira/browse/JBWS-2430
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: ws-reliable
Affects Versions: jbossws-native-3.0.4
Environment: JBoss 4.2.2.GA; WS-RX 2007/08
Reporter: Jean-Christophe Durand
Hi,
I had a big fight when I tried to get JBossWS work with WSF/PHP (using WS-RX). Everything
was working fine when using the Java client but for no evident reason, it was failing when
I used WSF as client.
After hours and hours of investigation, I figured out that it was at conversation
initiation that the process was failing. The reason is that the client is registering
under the "http://www.w3.org/2005/08/addressing/anonymous" address and is
proposing a sequence Id under the CreateSequence node:
<wsrm:CreateSequence>
<wsrm:AcksTo>
<wsa:Address
xmlns:wsa='http://www.w3.org/2005/08/addressing'>http://www.w3...
</wsrm:AcksTo>
<wsrm:Offer>
<wsrm:Identifier
xmlns:wsrm='http://docs.oasis-open.org/ws-rx/wsrm/200702'>5754...
<wsrm:Endpoint
xmlns:wsrm='http://docs.oasis-open.org/ws-rx/wsrm/200702'/>
</wsrm:Offer>
</wsrm:CreateSequence>
From what I read in Oasis specification, a server should not accept
the proposed identifier of an anonymous client but I do not see that it MUST reject any
client that provides such a combination.
What I would suggest is that rather than
rejecting the conversation, the server should only disregard the Offer/Identifier value
and behave as if no sequence id had been provided.
I tried to find out where to do this in JBossWS with no luck.
--
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
5:03 a.m.
New subject: [JBoss JIRA] Updated: (JBWS-2430) WS-RX: Anonymous client that offers a sequenceId should not be rejected (sequenceId should be disregarded instead)
[
https://jira.jboss.org/jira/browse/JBWS-2430?page=com.atlassian.jira.plug...
]
Richard Opalka updated JBWS-2430:
---------------------------------
Fix Version/s: jbossws-native-3.0.6
WS-RX: Anonymous client that offers a sequenceId should not be
rejected (sequenceId should be disregarded instead)
------------------------------------------------------------------------------------------------------------------
Key: JBWS-2430
URL: https://jira.jboss.org/jira/browse/JBWS-2430
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: ws-reliable
Affects Versions: jbossws-native-3.0.4
Environment: JBoss 4.2.2.GA; WS-RX 2007/08
Reporter: Jean-Christophe Durand
Assignee: Richard Opalka
Fix For: jbossws-native-3.0.6
Hi,
I had a big fight when I tried to get JBossWS work with WSF/PHP (using WS-RX). Everything
was working fine when using the Java client but for no evident reason, it was failing when
I used WSF as client.
After hours and hours of investigation, I figured out that it was at conversation
initiation that the process was failing. The reason is that the client is registering
under the "http://www.w3.org/2005/08/addressing/anonymous" address and is
proposing a sequence Id under the CreateSequence node:
<wsrm:CreateSequence>
<wsrm:AcksTo>
<wsa:Address
xmlns:wsa='http://www.w3.org/2005/08/addressing'>http://www.w3...
</wsrm:AcksTo>
<wsrm:Offer>
<wsrm:Identifier
xmlns:wsrm='http://docs.oasis-open.org/ws-rx/wsrm/200702'>5754...
<wsrm:Endpoint
xmlns:wsrm='http://docs.oasis-open.org/ws-rx/wsrm/200702'/>
</wsrm:Offer>
</wsrm:CreateSequence>
From what I read in Oasis specification, a server should not accept the proposed
identifier of an anonymous client but I do not see that it MUST reject any client that
provides such a combination.
What I would suggest is that rather than rejecting the conversation, the server should
only disregard the Offer/Identifier value and behave as if no sequence id had been
provided.
I tried to find out where to do this in JBossWS with no luck.
--
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
7:16 a.m.
New subject: [JBoss JIRA] Commented: (JBWS-2430) WS-RX: Anonymous client that offers a sequenceId should not be rejected (sequenceId should be disregarded instead)
[
https://jira.jboss.org/jira/browse/JBWS-2430?page=com.atlassian.jira.plug...
]
Richard Opalka commented on JBWS-2430:
--------------------------------------
The above request message is incorrect according to WS-RX XML schema definition hence the
server doesn't accept it.
Element wsrm:CreateSequence/wsrm:Offer/wsrm:Endpoint element is mandatory once
wsrm:CreateSequence/wsrm:Offer element is specified.
Copy/paste from the WS-RX XSD:
<xs:complexType name="OfferType">
<xs:sequence>
<xs:element ref="wsrm:Identifier"/>
<xs:element name="Endpoint"
type="wsa:EndpointReferenceType"/>
<xs:element ref="wsrm:Expires" minOccurs="0"/>
<xs:element name="IncompleteSequenceBehavior"
type="wsrm:IncompleteSequenceBehaviorType" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##other"
processContents="lax"/>
</xs:complexType>
As you can see there's no minoccurs="0" in Endpoint element (the default
value is 1 - thus this element is required).
And the value of Endpoint element in above request message is incorrect according to the
wsa:EndpointReferenceType definition:
Copy/paste from WS-Addressing schema definition:
<xs:complexType name="EndpointReferenceType" mixed="false">
<xs:sequence>
<xs:element name="Address" type="tns:AttributedURIType"/>
<xs:element name="ReferenceParameters"
type="tns:ReferenceParametersType" minOccurs="0"/>
<xs:element ref="tns:Metadata" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
The above message have to specify at lease Address subelement.
WS-RX: Anonymous client that offers a sequenceId should not be
rejected (sequenceId should be disregarded instead)
------------------------------------------------------------------------------------------------------------------
Key: JBWS-2430
URL: https://jira.jboss.org/jira/browse/JBWS-2430
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: ws-reliable
Affects Versions: jbossws-native-3.0.4
Environment: JBoss 4.2.2.GA; WS-RX 2007/08
Reporter: Jean-Christophe Durand
Assignee: Richard Opalka
Fix For: jbossws-native-3.0.6
Hi,
I had a big fight when I tried to get JBossWS work with WSF/PHP (using WS-RX). Everything
was working fine when using the Java client but for no evident reason, it was failing when
I used WSF as client.
After hours and hours of investigation, I figured out that it was at conversation
initiation that the process was failing. The reason is that the client is registering
under the "http://www.w3.org/2005/08/addressing/anonymous" address and is
proposing a sequence Id under the CreateSequence node:
<wsrm:CreateSequence>
<wsrm:AcksTo>
<wsa:Address
xmlns:wsa='http://www.w3.org/2005/08/addressing'>http://www.w3...
</wsrm:AcksTo>
<wsrm:Offer>
<wsrm:Identifier
xmlns:wsrm='http://docs.oasis-open.org/ws-rx/wsrm/200702'>5754...
<wsrm:Endpoint
xmlns:wsrm='http://docs.oasis-open.org/ws-rx/wsrm/200702'/>
</wsrm:Offer>
</wsrm:CreateSequence>
From what I read in Oasis specification, a server should not accept the proposed
identifier of an anonymous client but I do not see that it MUST reject any client that
provides such a combination.
What I would suggest is that rather than rejecting the conversation, the server should
only disregard the Offer/Identifier value and behave as if no sequence id had been
provided.
I tried to find out where to do this in JBossWS with no luck.
--
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
7:16 a.m.
New subject: [JBoss JIRA] Updated: (JBWS-2430) WS-RX: Anonymous client that offers a sequenceId should not be rejected (sequenceId should be disregarded instead)
[
https://jira.jboss.org/jira/browse/JBWS-2430?page=com.atlassian.jira.plug...
]
Richard Opalka updated JBWS-2430:
---------------------------------
Comment: was deleted
WS-RX: Anonymous client that offers a sequenceId should not be
rejected (sequenceId should be disregarded instead)
------------------------------------------------------------------------------------------------------------------
Key: JBWS-2430
URL: https://jira.jboss.org/jira/browse/JBWS-2430
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: ws-reliable
Affects Versions: jbossws-native-3.0.4
Environment: JBoss 4.2.2.GA; WS-RX 2007/08
Reporter: Jean-Christophe Durand
Assignee: Richard Opalka
Fix For: jbossws-native-3.0.6
Hi,
I had a big fight when I tried to get JBossWS work with WSF/PHP (using WS-RX). Everything
was working fine when using the Java client but for no evident reason, it was failing when
I used WSF as client.
After hours and hours of investigation, I figured out that it was at conversation
initiation that the process was failing. The reason is that the client is registering
under the "http://www.w3.org/2005/08/addressing/anonymous" address and is
proposing a sequence Id under the CreateSequence node:
<wsrm:CreateSequence>
<wsrm:AcksTo>
<wsa:Address
xmlns:wsa='http://www.w3.org/2005/08/addressing'>http://www.w3...
</wsrm:AcksTo>
<wsrm:Offer>
<wsrm:Identifier
xmlns:wsrm='http://docs.oasis-open.org/ws-rx/wsrm/200702'>5754...
<wsrm:Endpoint
xmlns:wsrm='http://docs.oasis-open.org/ws-rx/wsrm/200702'/>
</wsrm:Offer>
</wsrm:CreateSequence>
From what I read in Oasis specification, a server should not accept the proposed
identifier of an anonymous client but I do not see that it MUST reject any client that
provides such a combination.
What I would suggest is that rather than rejecting the conversation, the server should
only disregard the Offer/Identifier value and behave as if no sequence id had been
provided.
I tried to find out where to do this in JBossWS with no luck.
--
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
7:18 a.m.
New subject: [JBoss JIRA] Commented: (JBWS-2430) WS-RX: Anonymous client that offers a sequenceId should not be rejected (sequenceId should be disregarded instead)
[
https://jira.jboss.org/jira/browse/JBWS-2430?page=com.atlassian.jira.plug...
]
Richard Opalka commented on JBWS-2430:
--------------------------------------
The above request message is incorrect according to WS-RX XML schema definition hence the
server doesn't accept it.
Element wsrm:CreateSequence/wsrm:Offer/wsrm:Endpoint element is mandatory once
wsrm:CreateSequence/wsrm:Offer element is specified.
Copy/paste from the WS-RX XSD:
<xs:complexType name="OfferType">
<xs:sequence>
<xs:element ref="wsrm:Identifier"/>
<xs:element name="Endpoint"
type="wsa:EndpointReferenceType"/>
<xs:element ref="wsrm:Expires" minOccurs="0"/>
<xs:element name="IncompleteSequenceBehavior"
type="wsrm:IncompleteSequenceBehaviorType" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##other"
processContents="lax"/>
</xs:complexType>
As you can see there's no minoccurs="0" in Endpoint element (the default
value is 1 - thus this element is required).
And the value of Endpoint element in above request message is incorrect according to the
wsa:EndpointReferenceType definition:
Copy/paste from WS-Addressing schema definition:
<xs:complexType name="EndpointReferenceType" mixed="false">
<xs:sequence>
<xs:element name="Address" type="tns:AttributedURIType"/>
<xs:element name="ReferenceParameters"
type="tns:ReferenceParametersType" minOccurs="0"/>
<xs:element ref="tns:Metadata" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
The above message have to specify at least Address subelement.
The absence of wsrm:CreateSequence/wsrm:Offer/wsrm:Endpoint/wsa:Address element is the
reason of failure user can see.
WS-RX: Anonymous client that offers a sequenceId should not be
rejected (sequenceId should be disregarded instead)
------------------------------------------------------------------------------------------------------------------
Key: JBWS-2430
URL: https://jira.jboss.org/jira/browse/JBWS-2430
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: ws-reliable
Affects Versions: jbossws-native-3.0.4
Environment: JBoss 4.2.2.GA; WS-RX 2007/08
Reporter: Jean-Christophe Durand
Assignee: Richard Opalka
Fix For: jbossws-native-3.0.6
Hi,
I had a big fight when I tried to get JBossWS work with WSF/PHP (using WS-RX). Everything
was working fine when using the Java client but for no evident reason, it was failing when
I used WSF as client.
After hours and hours of investigation, I figured out that it was at conversation
initiation that the process was failing. The reason is that the client is registering
under the "http://www.w3.org/2005/08/addressing/anonymous" address and is
proposing a sequence Id under the CreateSequence node:
<wsrm:CreateSequence>
<wsrm:AcksTo>
<wsa:Address
xmlns:wsa='http://www.w3.org/2005/08/addressing'>http://www.w3...
</wsrm:AcksTo>
<wsrm:Offer>
<wsrm:Identifier
xmlns:wsrm='http://docs.oasis-open.org/ws-rx/wsrm/200702'>5754...
<wsrm:Endpoint
xmlns:wsrm='http://docs.oasis-open.org/ws-rx/wsrm/200702'/>
</wsrm:Offer>
</wsrm:CreateSequence>
From what I read in Oasis specification, a server should not accept the proposed
identifier of an anonymous client but I do not see that it MUST reject any client that
provides such a combination.
What I would suggest is that rather than rejecting the conversation, the server should
only disregard the Offer/Identifier value and behave as if no sequence id had been
provided.
I tried to find out where to do this in JBossWS with no luck.
--
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
5586
days inactive
5609
days old
jbossws-issues@lists.jboss.org
4 comments
2 participants
participants (2)
-
Jean-Christophe Durand (JIRA) -
Richard Opalka (JIRA)