Just to emphasize this point - during normal request processing, JDOM is not used, so there is no performance issue. JDOM is only used to load the configuration file at startup (or during the reload command).
Jeff > -----Original Message----- > From: Scott Hernandez [mailto:[EMAIL PROTECTED]] > Sent: Friday, February 14, 2003 8:07 AM > To: [EMAIL PROTECTED] > Subject: Re: [Mav-user] JDom > > > Yep. JDom is just used to the load the config file. Not as > the default processor for any other transformations or xml operations. > > > > > I'd like not to use JDom > > > > JDom is tightly integrated with Maverick. I didn't write > the original > code, > > but the code that I've read looks like it uses JDom very > effectively. > > As > far > > as Maverick is concerned, I don't think you'd see any significant > > performance gain by going to SAX or some other parsing technology. > > > ------------------------------------------------------- > This SF.NET email is sponsored by: FREE SSL Guide from > Thawte are you planning your Web Server Security? Click here > to get a FREE Thawte SSL guide and find the answers to all > your SSL security issues. > http://ads.sourceforge.net/cgi-> bin/redirect.pl?thaw0026en > > [INVALID FOOTER] > > ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en [INVALID FOOTER]
