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 "Takahide Nogayama (JIRA)" <ji...@apache.org> on 2006/11/29 16:47:21 UTC
[jira] Created: (SANDESHA2-55) pass options to
responseMessageContext
pass options to responseMessageContext
--------------------------------------
Key: SANDESHA2-55
URL: http://issues.apache.org/jira/browse/SANDESHA2-55
Project: Apache Sandesha2
Issue Type: Bug
Reporter: Takahide Nogayama
Priority: Critical
org.apache.sandesha2.workers.SenderWorker.checkForSyncResponses(MessageContext msgCtx) creates responseMessageContext and set some information from input argument messagecontext to responseMessageContext. I think that MessageContext.options should also be set to responseMessageContext. In current implementation, it is discarded.
We can see similar case in org.apache.axis2.description.OutInAxisOperation.send(MessageContext msgctx). And the fix code is from here.
-current------------------------------------------------------------------------------------------
// create the responseMessageContext
MessageContext responseMessageContext = new MessageContext();
------------------------------------------------------------------------------------------------------
-fix-----------------------------------------------------------------------------------------------------
// create the responseMessageContext
MessageContext responseMessageContext = new MessageContext();
responseMessageContext.setOptions(msgCtx.getOptions()); // set options.
------------------------------------------------------------------------------------------------------
--
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
[jira] Commented: (SANDESHA2-55) pass options to
responseMessageContext
Posted by "Matt Lovett (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/SANDESHA2-55?page=comments#action_12455951 ]
Matt Lovett commented on SANDESHA2-55:
--------------------------------------
I committed the patch into SVN revision 482995.
> pass options to responseMessageContext
> --------------------------------------
>
> Key: SANDESHA2-55
> URL: http://issues.apache.org/jira/browse/SANDESHA2-55
> Project: Apache Sandesha2
> Issue Type: Bug
> Reporter: Takahide Nogayama
> Assigned To: Matt Lovett
> Priority: Critical
> Attachments: patch3.txt, patch3copied.txt
>
>
> org.apache.sandesha2.workers.SenderWorker.checkForSyncResponses(MessageContext msgCtx) creates responseMessageContext and set some information from input argument messagecontext to responseMessageContext. I think that MessageContext.options should also be set to responseMessageContext. In current implementation, it is discarded.
> We can see similar case in org.apache.axis2.description.OutInAxisOperation.send(MessageContext msgctx). And the fix code is from here.
> -current------------------------------------------------------------------------------------------
> // create the responseMessageContext
> MessageContext responseMessageContext = new MessageContext();
> ------------------------------------------------------------------------------------------------------
> -fix-----------------------------------------------------------------------------------------------------
> // create the responseMessageContext
> MessageContext responseMessageContext = new MessageContext();
> responseMessageContext.setOptions(msgCtx.getOptions()); // set options.
> ------------------------------------------------------------------------------------------------------
--
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
[jira] Resolved: (SANDESHA2-55) pass options to
responseMessageContext
Posted by "Matt Lovett (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Lovett resolved SANDESHA2-55.
----------------------------------
Resolution: Fixed
> pass options to responseMessageContext
> --------------------------------------
>
> Key: SANDESHA2-55
> URL: https://issues.apache.org/jira/browse/SANDESHA2-55
> Project: Sandesha2
> Issue Type: Bug
> Reporter: Takahide Nogayama
> Assigned To: Matt Lovett
> Priority: Critical
> Attachments: patch3.txt, patch3copied.txt
>
>
> org.apache.sandesha2.workers.SenderWorker.checkForSyncResponses(MessageContext msgCtx) creates responseMessageContext and set some information from input argument messagecontext to responseMessageContext. I think that MessageContext.options should also be set to responseMessageContext. In current implementation, it is discarded.
> We can see similar case in org.apache.axis2.description.OutInAxisOperation.send(MessageContext msgctx). And the fix code is from here.
> -current------------------------------------------------------------------------------------------
> // create the responseMessageContext
> MessageContext responseMessageContext = new MessageContext();
> ------------------------------------------------------------------------------------------------------
> -fix-----------------------------------------------------------------------------------------------------
> // create the responseMessageContext
> MessageContext responseMessageContext = new MessageContext();
> responseMessageContext.setOptions(msgCtx.getOptions()); // set options.
> ------------------------------------------------------------------------------------------------------
--
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-55) pass options to
responseMessageContext
Posted by "Matt Lovett (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Lovett resolved SANDESHA2-55.
----------------------------------
Resolution: Fixed
> pass options to responseMessageContext
> --------------------------------------
>
> Key: SANDESHA2-55
> URL: https://issues.apache.org/jira/browse/SANDESHA2-55
> Project: Sandesha2
> Issue Type: Bug
> Reporter: Takahide Nogayama
> Assigned To: Matt Lovett
> Priority: Critical
> Attachments: patch3.txt, patch3copied.txt
>
>
> org.apache.sandesha2.workers.SenderWorker.checkForSyncResponses(MessageContext msgCtx) creates responseMessageContext and set some information from input argument messagecontext to responseMessageContext. I think that MessageContext.options should also be set to responseMessageContext. In current implementation, it is discarded.
> We can see similar case in org.apache.axis2.description.OutInAxisOperation.send(MessageContext msgctx). And the fix code is from here.
> -current------------------------------------------------------------------------------------------
> // create the responseMessageContext
> MessageContext responseMessageContext = new MessageContext();
> ------------------------------------------------------------------------------------------------------
> -fix-----------------------------------------------------------------------------------------------------
> // create the responseMessageContext
> MessageContext responseMessageContext = new MessageContext();
> responseMessageContext.setOptions(msgCtx.getOptions()); // set options.
> ------------------------------------------------------------------------------------------------------
--
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-55) pass options to
responseMessageContext
Posted by "Takahide Nogayama (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/SANDESHA2-55?page=all ]
Takahide Nogayama updated SANDESHA2-55:
---------------------------------------
Attachment: patch3.txt
Hi,
The problem here is, some parameters were changed in TransportUtils.createSOAPMessage(MessageContext, String). and the change might be used in axisEngine or handler. So that TransportUtils , AxisEngine, and handlers share the same MessageContext, responseMessageContext is put to TransportUtils.createSOAPMessage(MessageContext, String).
This patch3.txt fix this problem and this patch passed all unit test.
# my environment is maven1.1-beta2 with Sun JDK 5.0 @ FC6 linux
Thanks.
> pass options to responseMessageContext
> --------------------------------------
>
> Key: SANDESHA2-55
> URL: http://issues.apache.org/jira/browse/SANDESHA2-55
> Project: Apache Sandesha2
> Issue Type: Bug
> Reporter: Takahide Nogayama
> Assigned To: Matt Lovett
> Priority: Critical
> Attachments: patch3.txt
>
>
> org.apache.sandesha2.workers.SenderWorker.checkForSyncResponses(MessageContext msgCtx) creates responseMessageContext and set some information from input argument messagecontext to responseMessageContext. I think that MessageContext.options should also be set to responseMessageContext. In current implementation, it is discarded.
> We can see similar case in org.apache.axis2.description.OutInAxisOperation.send(MessageContext msgctx). And the fix code is from here.
> -current------------------------------------------------------------------------------------------
> // create the responseMessageContext
> MessageContext responseMessageContext = new MessageContext();
> ------------------------------------------------------------------------------------------------------
> -fix-----------------------------------------------------------------------------------------------------
> // create the responseMessageContext
> MessageContext responseMessageContext = new MessageContext();
> responseMessageContext.setOptions(msgCtx.getOptions()); // set options.
> ------------------------------------------------------------------------------------------------------
--
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
[jira] Updated: (SANDESHA2-55) pass options to
responseMessageContext
Posted by "Takahide Nogayama (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/SANDESHA2-55?page=all ]
Takahide Nogayama updated SANDESHA2-55:
---------------------------------------
Attachment: patch3copied.txt
patch3copied.txt is same file as patch3.txt.
This patch is attached with "Grant license to ASF for inclusion in ASF works" check box.
> pass options to responseMessageContext
> --------------------------------------
>
> Key: SANDESHA2-55
> URL: http://issues.apache.org/jira/browse/SANDESHA2-55
> Project: Apache Sandesha2
> Issue Type: Bug
> Reporter: Takahide Nogayama
> Assigned To: Matt Lovett
> Priority: Critical
> Attachments: patch3.txt, patch3copied.txt
>
>
> org.apache.sandesha2.workers.SenderWorker.checkForSyncResponses(MessageContext msgCtx) creates responseMessageContext and set some information from input argument messagecontext to responseMessageContext. I think that MessageContext.options should also be set to responseMessageContext. In current implementation, it is discarded.
> We can see similar case in org.apache.axis2.description.OutInAxisOperation.send(MessageContext msgctx). And the fix code is from here.
> -current------------------------------------------------------------------------------------------
> // create the responseMessageContext
> MessageContext responseMessageContext = new MessageContext();
> ------------------------------------------------------------------------------------------------------
> -fix-----------------------------------------------------------------------------------------------------
> // create the responseMessageContext
> MessageContext responseMessageContext = new MessageContext();
> responseMessageContext.setOptions(msgCtx.getOptions()); // set options.
> ------------------------------------------------------------------------------------------------------
--
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
[jira] Updated: (SANDESHA2-55) pass options to
responseMessageContext
Posted by "Takahide Nogayama (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/SANDESHA2-55?page=all ]
Takahide Nogayama updated SANDESHA2-55:
---------------------------------------
Attachment: patch3copied.txt
patch3copied.txt is same file as patch3.txt.
This patch is attached with "Grant license to ASF for inclusion in ASF works" check box.
> pass options to responseMessageContext
> --------------------------------------
>
> Key: SANDESHA2-55
> URL: http://issues.apache.org/jira/browse/SANDESHA2-55
> Project: Apache Sandesha2
> Issue Type: Bug
> Reporter: Takahide Nogayama
> Assigned To: Matt Lovett
> Priority: Critical
> Attachments: patch3.txt, patch3copied.txt
>
>
> org.apache.sandesha2.workers.SenderWorker.checkForSyncResponses(MessageContext msgCtx) creates responseMessageContext and set some information from input argument messagecontext to responseMessageContext. I think that MessageContext.options should also be set to responseMessageContext. In current implementation, it is discarded.
> We can see similar case in org.apache.axis2.description.OutInAxisOperation.send(MessageContext msgctx). And the fix code is from here.
> -current------------------------------------------------------------------------------------------
> // create the responseMessageContext
> MessageContext responseMessageContext = new MessageContext();
> ------------------------------------------------------------------------------------------------------
> -fix-----------------------------------------------------------------------------------------------------
> // create the responseMessageContext
> MessageContext responseMessageContext = new MessageContext();
> responseMessageContext.setOptions(msgCtx.getOptions()); // set options.
> ------------------------------------------------------------------------------------------------------
--
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
[jira] Assigned: (SANDESHA2-55) pass options to
responseMessageContext
Posted by "Matt Lovett (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/SANDESHA2-55?page=all ]
Matt Lovett reassigned SANDESHA2-55:
------------------------------------
Assignee: Matt Lovett
> pass options to responseMessageContext
> --------------------------------------
>
> Key: SANDESHA2-55
> URL: http://issues.apache.org/jira/browse/SANDESHA2-55
> Project: Apache Sandesha2
> Issue Type: Bug
> Reporter: Takahide Nogayama
> Assigned To: Matt Lovett
> Priority: Critical
>
> org.apache.sandesha2.workers.SenderWorker.checkForSyncResponses(MessageContext msgCtx) creates responseMessageContext and set some information from input argument messagecontext to responseMessageContext. I think that MessageContext.options should also be set to responseMessageContext. In current implementation, it is discarded.
> We can see similar case in org.apache.axis2.description.OutInAxisOperation.send(MessageContext msgctx). And the fix code is from here.
> -current------------------------------------------------------------------------------------------
> // create the responseMessageContext
> MessageContext responseMessageContext = new MessageContext();
> ------------------------------------------------------------------------------------------------------
> -fix-----------------------------------------------------------------------------------------------------
> // create the responseMessageContext
> MessageContext responseMessageContext = new MessageContext();
> responseMessageContext.setOptions(msgCtx.getOptions()); // set options.
> ------------------------------------------------------------------------------------------------------
--
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
[jira] Assigned: (SANDESHA2-55) pass options to
responseMessageContext
Posted by "Matt Lovett (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/SANDESHA2-55?page=all ]
Matt Lovett reassigned SANDESHA2-55:
------------------------------------
Assignee: Matt Lovett
> pass options to responseMessageContext
> --------------------------------------
>
> Key: SANDESHA2-55
> URL: http://issues.apache.org/jira/browse/SANDESHA2-55
> Project: Apache Sandesha2
> Issue Type: Bug
> Reporter: Takahide Nogayama
> Assigned To: Matt Lovett
> Priority: Critical
>
> org.apache.sandesha2.workers.SenderWorker.checkForSyncResponses(MessageContext msgCtx) creates responseMessageContext and set some information from input argument messagecontext to responseMessageContext. I think that MessageContext.options should also be set to responseMessageContext. In current implementation, it is discarded.
> We can see similar case in org.apache.axis2.description.OutInAxisOperation.send(MessageContext msgctx). And the fix code is from here.
> -current------------------------------------------------------------------------------------------
> // create the responseMessageContext
> MessageContext responseMessageContext = new MessageContext();
> ------------------------------------------------------------------------------------------------------
> -fix-----------------------------------------------------------------------------------------------------
> // create the responseMessageContext
> MessageContext responseMessageContext = new MessageContext();
> responseMessageContext.setOptions(msgCtx.getOptions()); // set options.
> ------------------------------------------------------------------------------------------------------
--
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
[jira] Commented: (SANDESHA2-55) pass options to
responseMessageContext
Posted by "Matt Lovett (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/SANDESHA2-55?page=comments#action_12455951 ]
Matt Lovett commented on SANDESHA2-55:
--------------------------------------
I committed the patch into SVN revision 482995.
> pass options to responseMessageContext
> --------------------------------------
>
> Key: SANDESHA2-55
> URL: http://issues.apache.org/jira/browse/SANDESHA2-55
> Project: Apache Sandesha2
> Issue Type: Bug
> Reporter: Takahide Nogayama
> Assigned To: Matt Lovett
> Priority: Critical
> Attachments: patch3.txt, patch3copied.txt
>
>
> org.apache.sandesha2.workers.SenderWorker.checkForSyncResponses(MessageContext msgCtx) creates responseMessageContext and set some information from input argument messagecontext to responseMessageContext. I think that MessageContext.options should also be set to responseMessageContext. In current implementation, it is discarded.
> We can see similar case in org.apache.axis2.description.OutInAxisOperation.send(MessageContext msgctx). And the fix code is from here.
> -current------------------------------------------------------------------------------------------
> // create the responseMessageContext
> MessageContext responseMessageContext = new MessageContext();
> ------------------------------------------------------------------------------------------------------
> -fix-----------------------------------------------------------------------------------------------------
> // create the responseMessageContext
> MessageContext responseMessageContext = new MessageContext();
> responseMessageContext.setOptions(msgCtx.getOptions()); // set options.
> ------------------------------------------------------------------------------------------------------
--
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
[jira] Updated: (SANDESHA2-55) pass options to
responseMessageContext
Posted by "Takahide Nogayama (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/SANDESHA2-55?page=all ]
Takahide Nogayama updated SANDESHA2-55:
---------------------------------------
Attachment: patch3.txt
Hi,
The problem here is, some parameters were changed in TransportUtils.createSOAPMessage(MessageContext, String). and the change might be used in axisEngine or handler. So that TransportUtils , AxisEngine, and handlers share the same MessageContext, responseMessageContext is put to TransportUtils.createSOAPMessage(MessageContext, String).
This patch3.txt fix this problem and this patch passed all unit test.
# my environment is maven1.1-beta2 with Sun JDK 5.0 @ FC6 linux
Thanks.
> pass options to responseMessageContext
> --------------------------------------
>
> Key: SANDESHA2-55
> URL: http://issues.apache.org/jira/browse/SANDESHA2-55
> Project: Apache Sandesha2
> Issue Type: Bug
> Reporter: Takahide Nogayama
> Assigned To: Matt Lovett
> Priority: Critical
> Attachments: patch3.txt
>
>
> org.apache.sandesha2.workers.SenderWorker.checkForSyncResponses(MessageContext msgCtx) creates responseMessageContext and set some information from input argument messagecontext to responseMessageContext. I think that MessageContext.options should also be set to responseMessageContext. In current implementation, it is discarded.
> We can see similar case in org.apache.axis2.description.OutInAxisOperation.send(MessageContext msgctx). And the fix code is from here.
> -current------------------------------------------------------------------------------------------
> // create the responseMessageContext
> MessageContext responseMessageContext = new MessageContext();
> ------------------------------------------------------------------------------------------------------
> -fix-----------------------------------------------------------------------------------------------------
> // create the responseMessageContext
> MessageContext responseMessageContext = new MessageContext();
> responseMessageContext.setOptions(msgCtx.getOptions()); // set options.
> ------------------------------------------------------------------------------------------------------
--
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
[jira] Commented: (SANDESHA2-55) pass options to
responseMessageContext
Posted by "Matt Lovett (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/SANDESHA2-55?page=comments#action_12454686 ]
Matt Lovett commented on SANDESHA2-55:
--------------------------------------
Unfortunately, copying over the options at this point seems to break the sandesha unit tests. From the look of the tcpmon output, we are failing to create the RM sequence. Perhaps you should try to come up with a better patch, contact me offline, or start a discussion on the mailing list.
Thanks, Matt
> pass options to responseMessageContext
> --------------------------------------
>
> Key: SANDESHA2-55
> URL: http://issues.apache.org/jira/browse/SANDESHA2-55
> Project: Apache Sandesha2
> Issue Type: Bug
> Reporter: Takahide Nogayama
> Assigned To: Matt Lovett
> Priority: Critical
>
> org.apache.sandesha2.workers.SenderWorker.checkForSyncResponses(MessageContext msgCtx) creates responseMessageContext and set some information from input argument messagecontext to responseMessageContext. I think that MessageContext.options should also be set to responseMessageContext. In current implementation, it is discarded.
> We can see similar case in org.apache.axis2.description.OutInAxisOperation.send(MessageContext msgctx). And the fix code is from here.
> -current------------------------------------------------------------------------------------------
> // create the responseMessageContext
> MessageContext responseMessageContext = new MessageContext();
> ------------------------------------------------------------------------------------------------------
> -fix-----------------------------------------------------------------------------------------------------
> // create the responseMessageContext
> MessageContext responseMessageContext = new MessageContext();
> responseMessageContext.setOptions(msgCtx.getOptions()); // set options.
> ------------------------------------------------------------------------------------------------------
--
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
[jira] Commented: (SANDESHA2-55) pass options to
responseMessageContext
Posted by "Matt Lovett (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/SANDESHA2-55?page=comments#action_12454686 ]
Matt Lovett commented on SANDESHA2-55:
--------------------------------------
Unfortunately, copying over the options at this point seems to break the sandesha unit tests. From the look of the tcpmon output, we are failing to create the RM sequence. Perhaps you should try to come up with a better patch, contact me offline, or start a discussion on the mailing list.
Thanks, Matt
> pass options to responseMessageContext
> --------------------------------------
>
> Key: SANDESHA2-55
> URL: http://issues.apache.org/jira/browse/SANDESHA2-55
> Project: Apache Sandesha2
> Issue Type: Bug
> Reporter: Takahide Nogayama
> Assigned To: Matt Lovett
> Priority: Critical
>
> org.apache.sandesha2.workers.SenderWorker.checkForSyncResponses(MessageContext msgCtx) creates responseMessageContext and set some information from input argument messagecontext to responseMessageContext. I think that MessageContext.options should also be set to responseMessageContext. In current implementation, it is discarded.
> We can see similar case in org.apache.axis2.description.OutInAxisOperation.send(MessageContext msgctx). And the fix code is from here.
> -current------------------------------------------------------------------------------------------
> // create the responseMessageContext
> MessageContext responseMessageContext = new MessageContext();
> ------------------------------------------------------------------------------------------------------
> -fix-----------------------------------------------------------------------------------------------------
> // create the responseMessageContext
> MessageContext responseMessageContext = new MessageContext();
> responseMessageContext.setOptions(msgCtx.getOptions()); // set options.
> ------------------------------------------------------------------------------------------------------
--
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