You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Jeff Barrett (JIRA)" <ji...@apache.org> on 2007/06/26 17:03:26 UTC
[jira] Resolved: (AXIS2-2851) Move RESPONSE_WRITTEN flag from
OperationContext to RequestResponseTransport instance
[ https://issues.apache.org/jira/browse/AXIS2-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Barrett resolved AXIS2-2851.
---------------------------------
Resolution: Fixed
Patch was commited to SVN as noted above.
> Move RESPONSE_WRITTEN flag from OperationContext to RequestResponseTransport instance
> -------------------------------------------------------------------------------------
>
> Key: AXIS2-2851
> URL: https://issues.apache.org/jira/browse/AXIS2-2851
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: nightly
> Reporter: Dustin Amrhein
> Assignee: Jeff Barrett
> Fix For: nightly
>
> Attachments: patch.txt
>
>
> In order to properly integrate with Sandesha, we need to move the RESPONSE_WRITTEN from the OperationContext to the RequestResponseTransport instance. Specifically these changes were made in order to allow Axis2 and Sandesha to handle the oneway request case in which data is sent back in the ack. This will allow transport code to determine if data was sent back as the RESPONSE_WRITTEN will now be on the RequestResponseTransport instance instead of the OperationContext, which in the case of an ack is not available.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org