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-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
