[ 
https://issues.apache.org/jira/browse/SANDESHA2-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482978
 ] 

Gilbert Pilz commented on SANDESHA2-75:
---------------------------------------

As far as BEA is concerned, the requirement to include an Offer when an 
WS-RM-enabled service declares any output messages* is specified by the 
following paragraph in WS-RM Policy 200502 
(http://specs.xmlsoap.org/ws/2005/02/rm/WS-RMPolicy.pdf - last paragraph of 
Section 2.3 "Assertion Attachment"):
--------
Per WS-ReliableMessaging [WS-RM], a wsrm:CreateSequence request MAY contain an 
offer to create an "inbound" Sequence. If the RM policy assertion is attached 
to an endpoint declaring only input messages, the endpoint MUST reject a 
wsrm:CreateSequence request containing a wsrm:Offer to create a corresponding 
Sequence. If the assertion is attached to an endpoint declaring both input and 
output messages, the endpoint MUST reject a wsrm:CreateSequence request that 
does not contain a wsrm:Offer to create a corresponding Sequence.
--------
The way WLS implements WS-RM, enabling a service for WS-RM and attaching an 
RMAssertion to the WSDL (even if it's an implicit WSDL that may not be 
available until the service is deployed) are one and the same thing, so we have 
to implement this requirement. From the Sandesha viewpoint I can see that this 
isn't so cut and dried, considering that Sandesha doesn't use WS-RM Policy.

* We also implement the requirement to reject CreateSequence messages that 
contain Offers if the target service declares only input messages.

> Auto-Offer on two-way interactions
> ----------------------------------
>
>                 Key: SANDESHA2-75
>                 URL: https://issues.apache.org/jira/browse/SANDESHA2-75
>             Project: Sandesha2
>          Issue Type: Improvement
>         Environment: Axis2 talking to other WSRM endpoints
>            Reporter: Paul Fremantle
>
> Most WSRM endpoints "expect" an offer if the service they are offering has 
> any in-out operations. We don't make those offers unless the user codes them, 
> meaning that we don't interop as easily as we should. We ought to make an 
> offer if there are any in-out operations on the service.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to