DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=36037>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=36037 ------- Additional Comments From [EMAIL PROTECTED] 2005-11-14 21:32 ------- Here's an alternative idea. The ActionForward would still hold an anchor value, but instead of: return mapping.findForward("someMapping?myParam=myVal#myAnchor"); ...the call would be: return new ActionForward(mapping.findForward("default"), "myAnchor"); The advantage is that the change would be limited to one class - ActionForward. The disadvantage would be that the Action class now loses the ability to modify the parameters at runtime. Of course, it doesn't have support for that now, so we're not really *losing* anything, just not providing anything extra. I haven't fully thought this through, so I'm not yet sure if ActionRedirect will be able to just inherit anchor support as well. If it does, then great! Currently, ActionRedirect overrides getPath() to return the computed path based on its properties. Either ActionForward does its computation on getPath () as well, or we just introduce a getComputedPath() which will then return the final path, so we won't need to introduce another getOriginalPath() like we did in ActionRedirect. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
