Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-ID: <021201c20211$ca8e05c0$0c91fea9@galina>
From: "Ivelin Ivanov" <ivelin@apache.org>
To: <cocoon-dev@xml.apache.org>
References: <00a501c2006c$9da995c0$0c91fea9@galina>
 <003401c20091$77521080$670004c0@PC103>
Subject: Re: [RT] Cocoon Exception Handling Infrastructure
Date: Wed, 22 May 2002 23:24:54 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="koi8-r"
Content-Transfer-Encoding: 7bit


Ok, let's try to to convert my ranting into a constructive discussion.
I'll scope down the initial request.

Let's talk about fixing the XSLT transformer, so that it produces friendly
and
accurate errors, which point as close as possible to the root cause.

If Cocoon's main transformer works well, then we can use it as usability
reference point for all other transformers.

Does this sound better?


----- Original Message -----
From: "Nicola Ken Barozzi" <nicolaken@apache.org>
To: <cocoon-dev@xml.apache.org>
Sent: Tuesday, May 21, 2002 1:33 AM
Subject: Re: [RT] Cocoon Exception Handling Infrastructure


> From: "Ivelin Ivanov" <ivelin@apache.org>
>
> > XSLT Transformer is obviously one of the most popular Cocoon components.
> > As such it carries the extra burden of serving as example to people
> writing
> > other components.
> >
> > In the sake of fairness, exception reporting is much friendlier in 2.1
> than
> > before. However much remains to be improved.
>
> +1
>
> > I was wondering if someone else shares my observations and thinks it's
> time
> > to lay out a design for better exception reporting infrastructure.
> >
> > I think that one of the biggest psychological barriers for Cocoon users
is
> > that they can't easily start writing simple apps. Cocoon is not very
> > forgiving with bad input, while at the same time its exception reporting
> is
> > often misleading the developer instead of pinpointing the problem.
>
> Well, the problem doesn't lie in the error reporting infrastructure, but
in
> the components themselves.
>
> When a component throws an error, it must not hide it, and must add the
info
> of any exception it wraps.
>
> Garbage in - garbage out
>
> You have labeled this thread RT, but it's more a RR (random rant).
>
> I would like to see some practical suggestions:
> - where in the code does the exception get stuck?
> - Is this problem of a component or general?
> - In which regard is the system inadeguate?
>
> IMNSHO the infrastructure is ok, but it needs debugging, yours too ;-P
>
> Why are there many rants about error reporting but nobody helping?
> (except Peter Royal, with whom I had a really cool trans-oceanic coding
> session on this)
>
> --
> Nicola Ken Barozzi                   nicolaken@apache.org
>             - verba volant, scripta manent -
>    (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>


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