[ http://issues.apache.org/jira/browse/SANDESHA2-42?page=comments#action_12448664 ] Chamikara Jayalath commented on SANDESHA2-42: ---------------------------------------------
Hi Matt, There was a need for the Sandesha2TransportSender but it'll be reflected only when a PersistentStorageManager is present :-( . Because of this Sandesha2TransportSender Sandesha2 always saves the final SOAP envelope (which has gone through all the outFlow handlers) in its database. In retransmissions Sender can directly feed this to the actual Transport Sender. If we remove this we will be storing envelopes which have only gone through a half of the outFlow handlers. We will have to send them throgh the rest of the handlers in every retransmission and we will have to serialize the whole context hierarchy to make sure that the process work correctly. 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]
