axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Sosnoski (JIRA)" <>
Subject [jira] Created: (AXIS2-516) MTOM forces document model generation
Date Sun, 26 Mar 2006 01:59:37 GMT
MTOM forces document model generation

         Key: AXIS2-516
     Project: Apache Axis 2.0 (Axis2)
        Type: Bug
  Components: databinding  
    Versions: 0.95    
 Environment: n/a
    Reporter: Dennis Sosnoski

The MTOM code currently forces the full expansion of the document model for outbound messages,
in order to check for optimizable components. This contradicts the whole intent of a build-on-demand
document model. Since AXIOM is actually considerably heavier in memory usage than standard
DOM implementations, it also means that Axis2 performance (at least for transports supporting
MTOM) is likely to be worse than the original Axis.

The performance drawbacks are especially severe when using data binding frameworks other than
XMLBeans and ADB - most data binding frameworks only allow marshalling data to a stream or
XMLStreamWriter equivalent, meaning that they would need to marshal the data to a memory buffer
and then parse it again in order to construct the document model. This would more than eliminate
any potential advantages from the use of MTOM.

One possible solution is to provide a way for data binding frameworks to check whether a value
is to be "optimized" (i.e., sent out of band) at the time it is being marshalled. The data
binding framework can then generate the appropriate output for an element, while the transport
can handle the details of sending separate components.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message