For all intends and purposes, the current design that uses a flat SAAJ tree to model the incoming message is fine.
The way the MessageFactoryImpl fragments the incoming message is highly ineffient and would greatly benefit from the use of SAX or StAX, but that is an optimiztion issue. Currently, the xmlFragments associated with SOAPContentElements are lazily deserialized, requiring a second parse for each fragment. This could also be optimized through StAX if the jboss binding framework could eagerly create the corresponding java objects during the first parse. As far as StAX is concerned, we also need to check whether the license of the available implementations allow us to include it in the jboss stack. Which implemenation did you have in mind? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3859440#3859440 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3859440 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
