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

Re: SAXException, checked, buy why?


Re:  SAXException
* Karl Waclawek <karl@w...> [2005-01-04 18:32]:
> 
> 
> Alan Gutierrez wrote:
> >* Karl Waclawek <karl@w...> [2005-01-04 15:22]:
> >
> >>Alan Gutierrez wrote:
> >>
> >>
> >>>>>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?
> >>
> >>The fact that you are adding certain methods with a specific signature
> >>already defines dependencies, even if you use Object everywhere.
> >>Using an abstract class is more open, IMO. It would serve as what
> >>you would call an opaque pointer in other languages.
> >
> >
> >    I don't follow.
> >
> >    public interface StrategyError /* maybe something here */ {
> >        // Stuff here.
> >    }
> >
> >    Suggestions?

> I would use a class, not an interface.
> Sender and receiver agree on a subclass appropriate for their
> problem. The sender passes it as abstract base class, the receiver
> casts it back, the API knows nothing about the subclass.

> You can add some always needed abstract members to the base class,
> like getMessage(), getCause(), etc. But don't add too many,
> as they may create dependencies, and may not always be needed,
> making the design non-minimal.

    If the sender and receiver agree on a class, then they can put
    it in variables map attached to the StrategyError.

    By making StrategyError a /final/ class, I'm enforcing a
    convention, that might be a bad convention, but the idea is that
    Strategy itself does not create an error.
    
    This class is the conduit, or at least the packet in the coduit.
    
    An interface, to me, is only interesting if it specifies a
    behavior, and not simply data members.

--
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.