[ http://issues.apache.org/jira/browse/AXIS2-1134?page=comments#action_12439742 ] Thilina Gunarathne commented on AXIS2-1134: -------------------------------------------
This problem arises in the case of AsyncMessageReceiver too... Without the above mentioned switch to send http 100 continue upon returning of the calling thread, Axis2 will not be able to send a response in the same channel in the case of AsyncMessageReceiver.... > Want to Store the MessageContext together with the OutputStream for later use > ----------------------------------------------------------------------------- > > Key: AXIS2-1134 > URL: http://issues.apache.org/jira/browse/AXIS2-1134 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Improvement > Components: core > Reporter: Thilina Gunarathne > > 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. - 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
