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 "Davanum Srinivas (JIRA)" <ji...@apache.org> on 2007/09/28 14:53:54 UTC

[jira] Updated: (SAND-3) Deciding whether the message is an IN-ONLY or IN-OUT should have an overriding mechanism to the default value

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

Davanum Srinivas updated SAND-3:
--------------------------------

    Assignee:     (was: Davanum Srinivas)

> Deciding whether the message is an IN-ONLY or IN-OUT should have an overriding mechanism to the default value
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: SAND-3
>                 URL: https://issues.apache.org/jira/browse/SAND-3
>             Project: Sandesha
>          Issue Type: Bug
>            Reporter: Jaliya Ekanayake
>
> Sandesha decide whether the request message is IN-ONLY or IN-OUT by looking at the call.getReturnType value. This default mechanism shold always check a flag set by the client, so that client can use Sandesha without setting the return type in Call.

-- 
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