anonymous wrote : | anonymous wrote : | | The problem with this is that I can't, of course, attach an element to the threadlocal document because there could be many active SOAPMessage objects within the same thread. | | | | Why is that? Can you show me a valid use case where there are multiple SOAPMessages per Thread?
Sure, what about an SAAJ client application that communicates with 2 webservices and then analyzes the results afterwords. anonymous wrote : The current WS4EE implemenation in Branch_4_0 works with the same ThreadLocal construct. Correct me if I am wrong, but it looks like the current implementation doesn't use a threadlocal implementation, but instead just spawns multiple document instances. It looks like the Axis implementation attempts to solve the problem I mentioned by maintaining a back reference to the SOAPPart. By glancing through the code it does look like 4.0 could suffer from the problem of assigning one document element to another document. The design method I mention could still work by importing nodes if they are from a different document (this is what the RI appears to do). -Jason View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875278#3875278 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875278 ------------------------------------------------------- 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
