ws-sandesha-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Parsons (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SANDESHA2-178) One way Addressible Client senario does not work.
Date Wed, 08 Oct 2008 13:48:44 GMT

    [ https://issues.apache.org/jira/browse/SANDESHA2-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637927#action_12637927
] 

Dave Parsons commented on SANDESHA2-178:
----------------------------------------

The fix to the RMMsgCreator may cause problems with logging a warning if makeConnection has
been turned off for RM 1.1.

Could you not have a client making more than one request to the same service but to different
operations in the service.  If the first operation invoked was oneway, the sequence would
be setup not warning the user that they have to have makeConnection enabled.  This would be
fine for the oneway invoke but if they were then to invoke a twoway operation in the same
service the same seq could be used and then the user wouldn;t have had that warning that makeConnection
wasn't enabled. 

If were not worried about this could we not remove the use of the Sandesha2Constants.SERVICE_CONTAINS_OUT_IN_MEPS
property and in RMMsgCreator just have the this line decide whether or not to offer:

			if(applicationMsgContext.getOperationContext().getAxisOperation().getAxisSpecificMEPConstant()
== org.apache.axis2.wsdl.WSDLConstants.MEP_CONSTANT_OUT_IN
			     || applicationMsgContext.getOperationContext().getAxisOperation().getAxisSpecificMEPConstant()
== org.apache.axis2.wsdl.WSDLConstants.MEP_CONSTANT_OUT_OPTIONAL_IN){
				autoOffer = true;
			}

Dave

> One way Addressible Client senario does not work.
> -------------------------------------------------
>
>                 Key: SANDESHA2-178
>                 URL: https://issues.apache.org/jira/browse/SANDESHA2-178
>             Project: Sandesha2
>          Issue Type: Improvement
>            Reporter: Amila Chinthaka Suriarachchi
>         Attachments: patch.txt
>
>
> 1. Sandesha2 does not read the useSeperateListner option and make the client Addressable
for One way scenarios. Although there are work around for this  they are not user friendly.
> 2. Sandesha2 adds sequence offer even for in only messages. 
>  

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


Mime
View raw message