In my experience hand coding XML in Java can be much faster than depending on external libraries. The downside is maintainence. Libraries have the benefit of many people working on bug fixes and enhancements. This is a classic problem.
I've been working on a scalability study for Elsevier Science that compares performance under increasing load and payload size for several SOAP implementations. What I've seen is the larger the payload the better off you would be to build your own XML message to attain better performance. If you really want to see the best possible performance then I recommend you use the XML-RPC library to make a call to a SOAP-based Web Service. This is an HTTP call that moves a test/xml payload. It will break when the server changes but until then you'll be running at top possible speed. -Frank Cohen www.PushToTest.com Quoting "Pfeiffer, Richard" <[EMAIL PROTECTED]>: > Just as Axis uses SAX instead of DOM to parse incoming messages, I > was > wondering whether it would be significantly faster to build an > outgoing XML > message by appending tags and text to a StringBuffer, sort of like > SAX in > reverse, rather than using the DOM API and doing appendChild, etc. > > I would like to hear people's opinions on whether this is worth > doing, and > if it is, I'd like help in the one thing I haven't figured out yet. > Since we > need to return a DOM Element to the client, is there a way to convert > a > String of XML elements into a valid DOM Element? > > Any ideas or feedback on this would be greatly appreciated! > > > Richard > -- http://www.PushToTest.com for free testing tools for testing Web Services
