DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12871>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12871 ExceptionHandler does not obey controller inputForward rule ------- Additional Comments From [EMAIL PROTECTED] 2002-12-24 11:21 ------- No offense intended, but how are you testing that you've *fixed* this issue? Again, the issue is _not_ about context relative paths or not, its about how the 'input' attribute is interpretted. Look at the patch I supplied in my second post on this issue and notice how I use getInputForward, not getInput - that is the key. I supplied the code - why are you ignoring it? I will try Struts b3 when its released and see if it is corrected at that point. I have a workaround by using my FixedExceptionHandler anyway. Opening this issue was my contribution to the Struts community, and not critical to my project. Also, I would suggest that try out your fix if you are going to change the code and claim its fixed. Do you have a test scenario where you are using inputForward="true"? Also, please consider applying my patch to the ActionError too, allowing the exception message to propogate and be displayable if desired (using {0}) - otherwise I'll have to continue to used my FixedExceptionHandler to propogate these messages even if you do fix the path handling in the builtin ExceptionHandler. :)) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
