So, to summarize this approach more clearly: | * Continue using thread local document behind the scenes to ensure that all nodes are allocated from the same document instance. | * Make SOAPPartImpl.getDocumentElement() return its nested SOAPEvelopeImpl. | * Maintain a reference to the associated SOAPPartImpl in every child NodeImpl. | * Make NodeImpl.getOwnerDocument() return the SOAPPartImpl reference | * Create an implementation of org.w3c.Document with create methods that return SAAJ elements and nodes instead of DOM elements/nodes. | * Delegate to the above implementation from SOAPPartImpl. | * Change the ThreadLocal reference to reference this new Document implementation | This should allow for efficient DOM access (read and write) on the SAAJ tree.
-Jason View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875355#3875355 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875355 ------------------------------------------------------- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
