tapestry-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From raulmt <rau...@gmail.com>
Subject Re: Centralize error handling
Date Fri, 04 Mar 2011 18:12:29 GMT
But, for example, access control errors are very common across the
application, so having a common place to handle them appears to be
reasonable. Is there another way to centralize aspects like commons error
handlings (access control, objects not found, requests without the expected
context parameters, etc…) without throwing exceptions in page or component
methods?

--
View this message in context: http://tapestry-users.832.n2.nabble.com/Centralize-error-handling-tp6089256p6089466.html
Sent from the Tapestry Users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Mime
View raw message