Hi all, I support this proposal. It gives us a way to simplify the outbound Sandesha processing (no more need to force a dummy transport into the outbound processing chain), helps integrate cleanly with security (no more need to special-case security as a 'retransmittable phase'), and helps ensure that the same message context object is not pushed out through 2 axis engines at the same time.
Note that http://issues.apache.org/jira/browse/SANDESHA2-42 contains the patch needed to address the first of these, and I'm happy to work on the code to achieve the other 2. Thanks Matt Ann Robinson <[EMAIL PROTECTED]> wrote on 27/11/2006 16:47:45: > I have a proposal for saving the AXIS2 message context based on some > of the discussion that occurred earlier this year. I have put a > description of the proposal on the Apache wiki at > > http://wiki.apache.org/ws/FrontPage/Axis2/MessageContextSaveRestore > > and I have submitted a patch for review in the JIRA issue AXIS2-1567. > > I would appreciate any comments on this proposal since it is > particularly useful for a WS-RM implementation. > > Ann > > WebSphere Development, Web Services Engine > > IBM > 11501 Burnet Rd IZip 9035G021 > Austin, TX 78758 > (512)838-9438 TL 678-9438 > > Lotus Notes: Ann Robinson/Austin/[EMAIL PROTECTED] > Internet: robinsona @ us.ibm.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
