cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From CHRISTOPH.OEH...@SBB.CH
Subject Re: Error Handling
Date Thu, 01 Jan 1970 00:00:00 GMT
--- Erhalten von  I0.U150033 0512 20 5221              06.12.99 11.59

What about implementing an Error-handler-interface?

It would have only one method: handle (Document doc, Dictionary
params, Writer write, Exception e).

In the implementation of the errorhandler one would be able to
generate an output on the response stream.

So the user would be able to select the desired handler with an PI.

What do you think?

----------------------------------------------------------------------

From: stefano@apache.org
To: cocoon-dev@xml.apache.org
Date: Mon, 6 Dec 1999 01:07:20 +0100
Subject: Re: Error Handling

brian moseley wrote:
>
> this is where i use the apache custom_response/internal
> redirect mechanism to great advantage in my mod_perl
> applications - when im processing an exception i select an
> error uri and set up an internal redirect to it. i get to
> stuff the exception message in the request notes table so
> that it's available to the 2nd request.
>
> im not terribly knowledgable about the servlet api, but it
> looks we could do something similar in cocoon by modifying
> the request and having the request dispatcher forward it?

Yes, that could be a solution. I'll try different ways out in the next
few days.

Also, what about having an HTTP error code set when something bad
happens? what should we use?

--
Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<stefano@apache.org>                             Friedrich Nietzsche

---- 06.12.99 11.59 ---- Gesendet an   -------------------------------
  -> cocoon-dev@xml.apache.org

Mime
View raw message