Even though Axis is using SAX internally, it still creates a DOM like structure from MessageElement object. Also all of the events are recorded. This leads to cpu/memory utilization similar to that of DOM model. When an object is deserialized from the Envelope, it is getting all of the events from SAXPlayer and not the original parser. As your messages grow larger, it becomes a problem.
Would it not make sense to allow direct serialization of registered object types, and skipping MessageElement? Since it is not always desired, it of cause should be optional. -Taras
