[
https://issues.apache.org/jira/browse/AXIS2-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503990
]
Srinath Perera commented on AXIS2-1134:
---------------------------------------
I purposed not to support this. It is not clear how Output stream is to be
stored (serialized), and even we though able to do it, OS resources will not be
avalible for ever. Supporting this will be big hassle and it will lead to many
future problems.
> Want to Store the MessageContext together with the OutputStream for later use
> -----------------------------------------------------------------------------
>
> Key: AXIS2-1134
> URL: https://issues.apache.org/jira/browse/AXIS2-1134
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: kernel
> Reporter: Thilina Gunarathne
> Assignee: Deepal Jayasinghe
> Priority: Blocker
>
> Use Case is to be able to send a delayed reply to an InOut invocation. One
> example is BPEL receive and reply activities. In this example we need to send
> a reply after some time to the received invocation. Holding of the invoking
> thread till we can write the response is unacceptable.
> In a scenario like above, we can store the incoming messagecontext to send
> the response later. But this causes the invoking thread to be returned.
> Returning of that thread causes the writing of an HTTP 200 OK to the
> outstream.
> We can introduce a new switch, which can be set when we want to do the above
> scenario. Axsi2 transport module can send an HTTP 100 Continue to the client
> in the presence of that switch to let him know that we'll be sending the
> response later.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
