[ http://issues.apache.org/jira/browse/SANDESHA2-42?page=comments#action_12449073 ] Chamikara Jayalath commented on SANDESHA2-42: ---------------------------------------------
Yep. Thats better. Lets wait a bit till we have an alternate way to do this. One more thing. The downstream handlers may be dependent on the information present in other contexts as well. So we will have to make sure that we serielize and deserialize the nessary information of all the related contexts (not just the message context). Hope Anns solution addresses this as well. Chamikara > Restructure outbound message path > --------------------------------- > > Key: SANDESHA2-42 > URL: http://issues.apache.org/jira/browse/SANDESHA2-42 > Project: Apache Sandesha2 > Issue Type: Improvement > Reporter: Matt Lovett > Attachments: transport.patch > > > I don't think that the sandesha transport adds any capability to the code, > and it complicates the outbound processing path. I think we should be able to > remove it, and be a little more careful about how we pause and resume the > message context on its way out. > I plan to attach a patch later on today > Matt -- 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]
