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

Re: SAXException, checked, buy why?


saxexception
* Karl Waclawek <karl@w...> [2005-01-04 14:32]:
> Alan Gutierrez wrote:
> 
> >>>  The class in final because a SAX error is really just a wrapper
> >>>  for a real, application error. No message either. That is found
> >>>  in the real cause. Eh?

> >>If you made your class abstract, then your content handler and
> >>application could agree on some shared way of exchanging
> >>information (through a subclass known to both of them) that is
> >>best suited to the problem at hand, without involving the API
> >>too much.

> >>Did you say "Eh?" to point out my Canadian domain name?
> >>Well, its true, I live there, but if you heard my accent ... ;-)

> >    No. It was just to solicit a response.

> >    Why Canadians are to touchy a boot their accents?
> 
> I am not touchy at all about it, I just find it amusing.

    Din't think you were, really, Wanted to get the "a boot" in there.

> I don't think Canadians have an accent worth mentioning.

> Btw, I am not a Canadian ...

    [OT] My mother's side is French-Canadian. :^) They have an accent of
    sorts in Manatoba. I remember calling directory information in
    Winnipeg, and being unable to understand the operator. It was
    quite a suprise.

> >    I think the API sticks it's nose in. I think API provides a
> >    conduit for XML message events coming in, and it needs to
> >    provide a conduit for error events going, er, where ever.
> 
> Yes, a conduit, but it should not care about what goes through
> that conduit.  This would create unnecessary dependencies.

    No. I think that means a lot of Object.
    
    Attaching a map to the error event?

> >    Did I already state that I see errors as simply more events? I
> >    do for now, at lest. Within handling, an error is an event, to
> >    be handled, and is thrown as a last resort.

> There are always multiple view points.

> In an event based API it is natural to see errors as events. The
> design challenge often is to come up with a solution that looks
> reasonable from different view points.

    You, think, then that this event-like model, with an observer is
    the way to go?

--
Alan Gutierrez - alan@e...

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.