You are viewing a plain text version of this content. The canonical link for it is here.
Posted to sandesha-dev@ws.apache.org by "Gilbert Pilz (JIRA)" <ji...@apache.org> on 2007/03/09 20:04:09 UTC

[jira] Updated: (SAND-12) Sandesha1 overrides SandeshaContext.setSendOffer(true)

     [ https://issues.apache.org/jira/browse/SAND-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gilbert Pilz updated SAND-12:
-----------------------------

    Attachment: setSendOffer-patch.txt

Fix problem by removing the override based on whether or not the operation has a response.

> Sandesha1 overrides SandeshaContext.setSendOffer(true)
> ------------------------------------------------------
>
>                 Key: SAND-12
>                 URL: https://issues.apache.org/jira/browse/SAND-12
>             Project: Sandesha
>          Issue Type: Bug
>         Environment: Java 1.5.0_06; Axis 1.4
>            Reporter: Gilbert Pilz
>         Assigned To: Davanum Srinivas
>         Attachments: setSendOffer-patch.txt
>
>
> Setting SandeshaContext.setSendOffer(true) does not always result in an Offer. This happens when the operation being invoked does not have any output messages. Although this makes sense when considered in the narrow context of Axis, it creates interoperability problems when you try to interoperate with systems such as WebLogic in which the scope of a Sequence encompasses all the operations that may be invoked from a particular endpoint. In order to interoperate with these systems, the programmer needs to force an Offer to occur, even in situations where it may not make sense from an Axis/JAX-RPC point of view.

-- 
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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org