Uploaded image for project: 'JBoss Web Services'
  1. JBoss Web Services
  2. JBWS-2430

WS-RX: Anonymous client that offers a sequenceId should not be rejected (sequenceId should be disregarded instead)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • jbossws-native-3.0.4
    • ws-reliable
    • Compatibility/Configuration
    • Low

      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.org/2005/08/addressing/anonymous</wsa:Address>
      </wsrm:AcksTo>
      <wsrm:Offer>
      <wsrm:Identifier xmlns:wsrm='http://docs.oasis-open.org/ws-rx/wsrm/200702'>57540fe2-c21b-1dd1-3acc-001143a00b7a</wsrm:Identifier>
      <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.

              ropalka Richard Opalka
              jdurand_jira Jean-Christophe Durand (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: