cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <cziege...@s-und-n.de>
Subject RE: [RT]: InputModules interfaces
Date Tue, 08 Oct 2002 09:08:51 GMT

Sylvain Wallez wrote:
> 
> >But if you have a method indicating that it throws a ProcessingException
> >and it calls a method which simply throws Exception than you have to
> >do something like this:
> >try {
> >    inputmodule.method();
> >} catch (ProcessingException pe) {
> >    // rethrow
> >    throw pe;
> >} catch (Exception e) {
> >    throw new ProcessingException(e);
> >}
> >
> 
> You should also add (damn, I'm picky today) :
>   catch (RuntimeException re) {
>       throw re;
>   }
> 
Nice try :)

But seriously, being picky is imho important to get more qualitity in 
open source. I wasn't picky (and don't cared :( ) when InputModules
were introduced and I didn't follow the discussions very close...

> >And there are some important (= high level) classes which indicate
> >to throw ProcessingException - that's all.
> >
> 
> Granted. But is InputModule to be considered "high level" ?
> 
No, not InputModule but a calling component.

Carsten

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message