Hi, Peter I have used SAX for one project last year, and JDOM for another project this year. JDOM cut development time by four. To be honest, I could have reused many parts of the first project for the second, and development time would also have been shorter, but not that much. I found JDOM is exactly what I should have developped for myself (and much more, of course;-). With JDOM, you are just one step from your business logic and you don't have to deal whith technical details. It's one of the most productive package I have ever used. The only problem is it is still a work in progress. I really hope it will become a real standard. Pierre-Yves -----Message d'origine----- De : A mailing list for discussion about Sun Microsystem's Java Servlet API Technology. [mailto:[EMAIL PROTECTED]]De la part de Peter Barraud Envoy� : mercredi 20 juin 2001 07:57 � : [EMAIL PROTECTED] Objet : JDOM Hi Has anybody started using the JDOM it seems incredibly easier than DOM & SAX since I haven't done anything so far, I would appreciate any suggestions about weather it would be ok to go ahead and work completely with the JDOM or should I first start with DOM & SAX peter ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
