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 "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org> on 2008/10/08 12:11:44 UTC
[jira] Created: (SANDESHA2-178) One way Addressible Client senario
does not work.
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
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
[jira] Updated: (SANDESHA2-178) One way Addressible Client senario
does not work.
Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amila Chinthaka Suriarachchi updated SANDESHA2-178:
---------------------------------------------------
Attachment: patch.txt
For some interop senarios it won't work if Sandesha2 sends an sequence offer. So there must be a way to stop that as well.
To solve this I added a new constant using which users and explicitly set the sequence as an one way sequence. If this property is not set then it works as earlier.
> 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, 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
[jira] Updated: (SANDESHA2-178) One way Addressible Client senario
does not work.
Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amila Chinthaka Suriarachchi updated SANDESHA2-178:
---------------------------------------------------
Attachment: patch.txt
This patch solves the problems above.
1. it gets the ReplyTo address from the in transport if the operation is out only and useSeperateListner set
2. set the twoWayOperation parameter only if the operation is two way.
> 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
[jira] Commented: (SANDESHA2-178) One way Addressible Client
senario does not work.
Posted by "Dave Parsons (JIRA)" <ji...@apache.org>.
[ 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
[jira] Resolved: (SANDESHA2-178) One way Addressible Client senario
does not work.
Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amila Chinthaka Suriarachchi resolved SANDESHA2-178.
----------------------------------------------------
Resolution: Fixed
commited the patch with revision 706119
> 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, 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