Peter Royal wrote:
> (Carlos I have cc'd you since this is a good "best pratice" for debugging)
>
> On Thursday 03 January 2002 03:49 pm, you wrote:
> Wrap *all* SAX event handlers that you have written (or think may be buggy)
> ala:
>
> public void endElement(String uri, String loc, String raw) throws SAXException
> {
> try {
> //your code here
> } catch (RuntimeException re) {
> throw new SAXException("RuntimeException in endElement", re);
> }
> }
>
> and you will find the error. Once I figured this trick out I used it in a few
> choice spots and fixed all my errors. (well, not *ALL* just the RE's in the
> SAX stream :)
> -pete
Perhaps the AbstractXMLConsumer should perform the wrapping for us!
That will catch many issues.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
