Hi Brian Thanks for spotting that! Whoops, that looks like something that got left in the code after a debugging run. Its gone now.
I've committed the change to CVS and its available in the daily build. James ----- Original Message ----- From: "Brian W. Young" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, October 29, 2001 9:51 PM Subject: [dom4j-dev] stack trace code in saxreader > I'm new to the mailing list and not sure if this has been addressed, but > in v 1.35 of SaxReader, there is a printStackTrace() that is probably > not appropriate... line # 308, the read(InputSource in). > > I had to comment this out to contain uncontrolled stack traces when > plugging in Xerces for validation against a DTD. The stack trace to > system out should be left up to the user of the API, I would think. > > Great API otherwise. Integrated XPath has been a big help. Thanks. > > > > _______________________________________________ > dom4j-dev mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/dom4j-dev > _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ dom4j-dev mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dom4j-dev
