You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by "Thomas McKiernan (JIRA)" <ji...@apache.org> on 2006/08/30 10:37:25 UTC
[jira] Updated: (SANDESHA2-22) Set unreliable property into
operation ctx
[ http://issues.apache.org/jira/browse/SANDESHA2-22?page=all ]
Thomas McKiernan updated SANDESHA2-22:
--------------------------------------
Attachment: unreliable_on_op_ctx.txt
This should fix the problem
> Set unreliable property into operation ctx
> ------------------------------------------
>
> Key: SANDESHA2-22
> URL: http://issues.apache.org/jira/browse/SANDESHA2-22
> Project: Apache Sandesha2
> Issue Type: Improvement
> Reporter: Thomas McKiernan
> Priority: Minor
> Attachments: unreliable_on_op_ctx.txt
>
>
> At the moment the "unreliable" property is set in the msgCtx and is examined in the sandeshaOutHandler.
> It would be useful to also specify it at the operation level, such that an unreliable operation would never require sandesha processing. If the value is set at either ctx then the msg should not be processed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org