On Thu, Jun 25, 2009 at 9:05 AM, Jan T. Kim<j....@uea.ac.uk> wrote: > > I agree that from an EJB provider's angle its quite possible to argue > that session bean's constructors shouldn't throw exceptions. From an > application assembler's perspective, though, I'd expect that a global > exception mapping would handle all exceptions of the specified class, > regardless of whether they are thrown by constructors or other methods > (and regardless of whether the exception is considered legitimate or > reasonable). > > Best regards, Jan >
I'm with you here, I plan on making this work in 2.1.8 (or at least trying really hard). You will be hard-pressed to find people to agree that throwing exceptions in your constructor as a way of enforcing security is the right thing to do, *but* "global-exception-mappings" is an ambiguous feature name, unless we are catching exceptions during access and creation. So, although I don't quite agree with your design, I still agree that it is something we should change... (Is that a political explanation or what?) -Wes -- Wes Wannemacher Author - Struts 2 In Practice Includes coverage of Struts 2.1, Spring, JPA, JQuery, Sitemesh and more http://www.manning.com/wannemacher --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
