> We want to handle exceptions in a centralized way
My first approach would be to see how Tapestry already does it. In
TapestryModule there is a RequestFilter configured:
configuration.addInstance("ErrorFilter", RequestErrorFilter.class);
One approach would be to add your own filter to c
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 paramet
My approach would be not to throw exceptions all the time. The exception
handler is only used for fatal stuff, I don't throw stuff there by design.
--
View this message in context:
http://tapestry-users.832.n2.nabble.com/Centralize-error-handling-tp6089256p6089399.html
Sent from the Tapestry User
