:-) It's all a bit much isn't it.
SAX is not a parser, it's more of a method that a parser would use. There are essentially two ways to treat XML. DOM ..where a tree is built based on the XML file given and then traversed back and forth to get stuff out of it. - And SAX ..where an XML file is treated more like an object and can fire its own events without having to be traversed/climbed like the DOM tree. (please someone who actually knows something about this stuff correct me). As such you could use either of DOM or SAX methods to get the effect you're looking for. The difference between the two is basically that DOM is a little easier conceptually (I think) and SAX is faster and more OOP oriented. If you're used to HTML then you're already working in a DOM type environment and the conceptual leaps should not be so big. Xerces can work in either of these modes. http://www.devshed.com/Server_Side/XML/SAXandXerces/SAXandXerces2/print_ html http://www.ecerami.com/xerces/ The latter article is a tad out of date as it mentions the xerces.jar file which no longer comes with the package but the rest of it should still be valid. It may further clear up the quagmire. Sorry I can't provide a clearer bit of example code but this lot should help you down the path. Alternatively.. check out the Jakarta standard taglibraries. There's an xml parsing taglib that may do just what you want http://www.manning.com/bayern/appendixA.pdf PDF manual for the taglibs ------------------------------------------------------ Tref Gare Development Consultant Areeba Level 19/114 William St, Melbourne VIC 3000 email: [EMAIL PROTECTED] phone: +61 3 9642 5553 fax: +61 3 9642 1335 website: http://www.areeba.com.au ------------------------------------------------------ "This email is intended only for the use of the individual or entity named above and contains information that is confidential. No confidentiality is waived or lost by any mis-transmission. If you received this correspondence in error, please notify the sender and immediately delete it from your system. You must not disclose, copy or rely on any part of this correspondence if you are not the intended recipient. Any communication directed to clients via this message is subject to our Agreement and relevant Project Schedule. Any information that is transmitted via email which may offend may have been sent without knowledge or the consent of Areeba." ------------------------------------------------------ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 20 November 2002 6:40 PM To: Tomcat Users List Subject: RE: XML parser I am looking at the article you suggested. While I am trying to digest it all.. am I right in thinking you are proposing and what the article is demonstrating is that I use the SAX approach to parse my XML (although SAX 'is not a parser'!) and not the Xerces parser? Thanks Paul. You're fine so far. The location of the xercesImpl.jar is fine for all jsp's that reside in your ROOT webapp ie: everything that lives in the root of your Tomcat installation. To parse the xml you'd ordinarily be trying to use a Servlet or a Bean to get the processing off the JSP page which should be used only for presentation of the finished results (as much as possible, best of all poss worlds etc). http://www2.theserverside.com/resources/article.jsp?l=JSP-XML2 This article should point you in the right direction. T -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
