Brian Thompson-5 wrote:
>
> I can only speculate, but it seems logical that the ClassNotFoundException
> is being thrown from outside the purview of Struts, in Tomcat's
> ClassLoaders
> - thus the Struts exception mapping never enters into it.
>
Theres definitely something odd going on. With global mappings disabled and
devmode set to true, entering an invalid action into the browser gives the
Struts formatted "No Action Mapped" exception (it's not
ClassNotFoundException"). With global mappings and devmode set to false,
entering an invalid action give the Tomcat 404 page with the no Action
Mapped message. With global mappings set to catch java.lang.exception and
devmode set to false, Struts seems to catch every exception thrown except
when an invalid action is keyed into the browser.
The fact that both the error message texts talk about "No Action Mapped"
must surely mean that the error is being caught by Struts as Action Mapping
is a Struts concept, not a Tomcat concept. I would have thought that
catching in Invalid Action was one of the messages you would most want to
catch to stop unfriendly users "experimenting" with your application!
Regards
--
View this message in context:
http://old.nabble.com/Re%3A-Catching%3A-Unable-to-instantiate-Action-tp26303352p26334735.html
Sent from the Struts - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org
