You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jesse Kuhnert (JIRA)" <de...@tapestry.apache.org> on 2008/02/08 16:05:19 UTC
[jira] Updated: (TAPESTRY-1349) exception presenter pages strategy
service
[ https://issues.apache.org/jira/browse/TAPESTRY-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse Kuhnert updated TAPESTRY-1349:
------------------------------------
Fix Version/s: (was: 4.1.5)
4.1.6
> exception presenter pages strategy service
> ------------------------------------------
>
> Key: TAPESTRY-1349
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1349
> Project: Tapestry
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 4.1.2
> Environment: internals / exception presenting
> Reporter: Jesse Kuhnert
> Priority: Minor
> Fix For: 4.1.6
>
>
> Mailing list dump from jesse / etc:
> I think most the exception infrastructure is focused around building
> up location / context information more so than exception types, though
> types are handled as well of course.. .
> If you want to know how tapestry handles it right now take a look at:
> http://svn.apache.org/viewvc/tapestry/tapestry4/trunk/tapestry-framework/src/java/org/apache/tapestry/engine/AbstractEngine.java?view=markup
> I can see it being useful having a hivemind strategy / config point
> similar to how data squeezers "vote" for handling something being the
> means by which these exception presenters are chosen. I'll file a jira
> issue for it.
> - Hide quoted text -
> On 3/8/07, Justin Walsh <ju...@sadalbari.com> wrote:
> > Is there a preferred way/pattern of handling application exceptions in a
> > tapestry application.
> > For example, I have a page, AuthorizationFailure.html which I want to
> > display when a javax.ejb.EJBAccessException is thrown from the ejb
> > layer, with a custom message etc.
> >
> > At the moment I'm plugging in my own ExceptionPresenter which sniffs out
> > the root cause and delegates to a handler, defaulting to the exception
> > page when a specific handler can't be found. But I'm wondering if I'm
> > missing anything. Perhaps there are exception handler base classes that
> > I can use? Or perhaps I can configure an exception presenter for a
> > specific type of exception?
> >
> > Cheers
> >
> > --
> > Justin Walsh
> > http://www.ewage.co.za
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org