[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Seeking SAXException pattern

• To: "'Mik Lernout'" <mik@f...>,"'Tim Bray'" <tbray@t...>
• Subject: RE: Seeking SAXException pattern
• From: "Michael Kay" <michael.h.kay@n...>
• Date: Sun, 28 Nov 2004 21:17:07 -0000
• Cc: <xml-dev@l...>
• In-reply-to: <41A9B0D3.4030102@f...>
• Thread-index: AcTVUUuPlCYjqzxgT9OQlE5+Y/6Z8gAPbevg

> public class TimBraySAXException extends SAXException { //details.. }

This works for relatively simple cases, but if the application invoked by
the ContentHandler is a real application of any complexity (say a
manufacturing scheduler) then you wouldn't want to distort the class
hierarchy in this way. In fact, if you're invoking existing libraries then
the exception classes will already be defined so you don't have this option.
In this case you have no choice but to wrap these exceptions inside a
SAXException (and then unwrap them when they re-emerge) in the way Tim
originally described. 

I must admit I have become so accustomed to doing this that it has ceased to
seem contorted.

Michael Kay
http://www.saxonica.com/

• References:
  • Re: Seeking SAXException pattern
    • From: Mik Lernout <mik@f...>

• Prev by Date: Re: Relax NG, Thoughts, etc.
• Next by Date: RE: Relax NG, Thoughts, etc.
• Previous by thread: Re: Seeking SAXException pattern
• Next by thread: Re: Seeking SAXException pattern
• Index(es):
  • Date
  • Thread