Hi Ann, Thanks for comming up with this proposal. Quite a useful subject indeed. I went through it and felt unclear about several areas. Here they are.
1. Serialization of parent contexts Does the serialization of parents repeat for every message context or do they get shared. If they do not I guess we hv to find out a way to share them. Otherwise it will be a big waste of the storage. 2. ConfigurationContext I'm not sure on how the information in the ConfigurationContext will be serialized. You haven't mentioned in the list of contexts that get saved with the MessageContext. But this may also contain useful runtime data which may be needed by the entity that uses the MessageContext. 3. What actually happens in the 'msgContext2.activate(configurationContext)' method. 4. As a whole your aproach is on making MessageContext implement Externalizable right ? 5. How will this map to a environment where somebody wants to save the MC in a database. For example Sandesha2 has a StorageManager inferace which could be implemented by different storage mechanisms. How will you support such a scenario with this. Chamikara p.s. (forwarding to sandesha-dev as well) On 11/27/06, Ann Robinson <[EMAIL PROTECTED]> wrote:
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 *<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
