Yeah, that seemed a little too easy :)
I would think it should throw an exception... Any Struts devs out there
have an opinion? I know someone (I forget who, sorry!) just mentioned
they added a warning that didn't make it into 1.2.7... A warning is
good, but I would personally think an exception would be better because
it's a pretty severe situation that deserves immediate attention (also a
situation that theoretically would never happen outside development...
at least, QA procedures better make that true! :) ).
Frank
Dan Tenenbaum wrote:
On 6/13/05, Frank W. Zammetti <[EMAIL PROTECTED]> wrote:
But again, I'm not certain this type of problem will be caught because I'm
not even sure an exception is thrown in such a case. If it isn't that
strikes me as a bug. Anyone else know for sure?
I don't think it does throw an exception. I tried putting just the
findForward() line in a try/catch block and nothing was thrown. Also,
no stack traces appear in my tomcat log except a broken pipe error
when trying to render the error page (there is nothing weird in the
error page itself that would cause this).
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
