Hi, Jim --
Can anyone offer a guess of how much slower it is to use a Digester rather
than writing individual SAX custom document content handlers? Assuming all
of the classes are loaded and retained would using a digester cause
considerable overhead?
The really short answer is YMMV. The slightly less short answer is that Digester is probably fast enough. Unless you're an experienced SAX programmer, the time you'll spend writing and rewriting a hand-implemented solution will outweigh the nominal performance gains. (S in SAX is for "simple", but that's the API as opposed to its usage.)
On premature optimization:
http://c2.com/cgi/wiki?PrematureOptimization
I recently made the decision to hand-implement a SAX-based loader for a configuration object model, but I made that decision based on a desire to minimize library dependencies (JAXB, JIBX, XMLBeans, Digester, etc.). Otherwise, I would have gone with a framework.
I am writing my first SOAP web service and have no experience to make a judgment which direction to go.
That's a more interesting question. Maybe come over to the AXIS user list?
--- Paul Brown http://blogs.fivesight.com/pbblog
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
