[ http://issues.apache.org/jira/browse/AXIS2-42?page=comments#action_12323053 ]
Chamikara Jayalath commented on AXIS2-42: ----------------------------------------- Sandesha currently badly needs message context serialization support. But serialization should be minimum to get a resonable performance. To support in-order invocation Sandesha will have to serialize all the messages (since most of the time they won't come in order). if the complete context hierarchy get serialized with every MC serialization , that is going to be a big overhead. So I believe the amount of data that get serialized should be minimum. A serialization of a message should only include the info. necessary to that message. (It is great if this can be limited to SOAP envelops and the properties of the message context). Other Contexts which has data common to several message context can be serialized to a common place (if needed). > Message Context Serialization Support > ------------------------------------- > > Key: AXIS2-42 > URL: http://issues.apache.org/jira/browse/AXIS2-42 > Project: Apache Axis 2.0 (Axis2) > Type: New Feature > Components: core > Reporter: Srinath Perera > Assignee: Deepal Jayasinghe > Priority: Critical > > Support to store and restore the Message context .. this involve the Axis > storage and context serialization -- 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
