You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by bu...@apache.org on 2003/02/03 17:11:31 UTC

DO NOT REPLY [Bug 16603] - internalModuleRelativeForward() does'nt treat module-relative paths as defined by forwardPattern.

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=16603>.
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=16603

internalModuleRelativeForward() does'nt  treat module-relative paths as defined by forwardPattern.





------- Additional Comments From malik.recoing@wanadoo.fr  2003-02-03 16:11 -------
It seems like this but affect ActionConfig.forward and ActionConfig.input as 
for both of them internalModuleRelativeForward() is used to calculate the 
definitive URI.

My fix was to delegate the work in internetModuleRelativeForward() to a new 
RequestUtils.contextRelativeURL() methode. I also re-aranged the pageURL() and 
forwardURL() so they use this new methode. 

I can now create an true multi-modules app with pages under WEB-INF.

Nobody have yet confirm me it's a bug and not a missunderstanding of the "big 
picture". However I still can't find a witness of a sucessfull configuration 
under WEB-INF (or anywere else other than /module1Prefix/, /module2Prefix/...).

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org