Re: [wsrm] WSDL One-way operation type and Data in Soap envelope of underlyingresponse

[Sunil Kunisetty <Sunil.Kunisetty@oracle.com>]

Tom Rutt wrote:

>  From the minutes of 6/14 meeting, My comments new to this email start
> with <ter> tag
> "
>  2b) The  one-way consumer  interface and Response  RM-Reply pattern  is the
>      most  direct combination to  reliably deliver  one-way messages  from a
>      producer "hidden" behind a firewall.   The matrix in section 5.2 should
>      not  disallow this  combination.   While synchronous  polling at  least
>      works, it always requires an additional round trip.
>
> <ter>  one of Sunil's objections to the above proposal is based on the
> BP 1.0 restriction.

 No, my basis was on WSDL abstract definition of one-way operation itself
 and not on BP. I believe I've clarified this umpteen no. of times on the call.

>
>
> I Quote from BP 1.0a of WS-I
> "
>
>         5.6.10 One-Way Operations
>
> There are differing interpretations of how HTTP is to be used when
> performing one-way operations.
>
> R2714 For one-way operations, an INSTANCE MUST NOT return a HTTP
> response that contains a SOAP envelope. Specifically, the HTTP response
> entity-body must be empty.
>
> R2750 A CONSUMER MUST ignore a SOAP response carried in a response from
> a one-way operation.
>
> R2727 For one-way operations, a CONSUMER MUST NOT interpret a successful
> HTTP response status code (i.e., 2xx) to mean the message is valid or
> that the receiver would process it.
>
> One-way operations do not produce SOAP responses. Therefore, the Profile
> prohibits sending a SOAP envelope in response to a one-way operation.
> This means that transmission of one-way operations can not result in
> processing level responses or errors. For example, a "500 Internal
> Server Error" HTTP response that includes a SOAP message containing a
> SOAP Fault element can not be returned.
>
> The HTTP response to a one-way operation indicates the success or
> failure of the transmission of the message. Based on the semantics of
> the different response status codes supported by the HTTP protocol, the
> Profile specifies that "200" and "202" are the preferred status codes
> that the sender should expect, signifying that the one-way message was
> received. A successful transmission does not indicate that the SOAP
> processing layer and the application logic has had a chance to validate
> the message or have committed to processing it.
>
> Despite the fact that the HTTP 1.1 assigns different meanings to
> response status codes "200" and "202", in the context of the Profile
> they should be considered equivalent by the initiator of the request.
> The Profile accepts both status codes because some SOAP implementations
> have little control over the HTTP protocol implementation and cannot
> control which of these response status codes is sent.
>
> "
>
> <ter> the requirements seem tied to HTTP transport binding for SOAP,
> rather than to SOAP in general. However the first two sentences of
> explanatory text is written regarding Soap in general.
>
> "
> One-way operations do not produce SOAP responses. Therefore, the Profile
> prohibits sending a SOAP envelope in response to a one-way operation "
>
> <ter - If we are going to allow response rm reply pattern with WSDL
> One-Way operation we
> need to explain our way around this Profile restriction.  >
>
> --
> ----------------------------------------------------
> Tom Rutt        email: tom@coastin.com; trutt@us.fujitsu.com
> Tel: +1 732 801 5744          Fax: +1 732 774 5133
>
> To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsrm/members/leave_workgroup.php.