cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Smirnoff" <>
Subject Error handling design question
Date Wed, 13 Feb 2002 22:27:24 GMT
After playing with cocoon for few month I found that it quite
strong and bold to be used in production environment. But
there are some weak points which I've noticed.

One of those is abnormal situation handling in XSP files. So
far I've tried few approaches.

The requirement is :

In the case of error present XML message containing the 
error number and the reason of error occurred.

First straight-forward approach was to use
request.sendRedirect(messagepage) method. But this in
some cases will result in IllegalStateException.

Second (which we are using in our application) is embedded
message approach. In the case of error message is 
embedded in XSP and later in the pipeline is filtered from
excessive tags. The only drawback of this approach is that
in some cases the execution of XSP must be terminated
with "return" statement or throwing an exception, which 
means all open SAX events must be consistently 
closed. Using <autocomplete-documents> will cause 
additional CPU load.

Maybe there are better solutions?

I'll appreciate to get some new opinion about this issue.


Please check that your question has not already been answered in the
FAQ before posting. <>

To unsubscribe, e-mail: <>
For additional commands, e-mail: <>

View raw message