This behavior is consistent with Struts 1.0. It always prepended the application context, and now it always prepends the application/context.
Since actions are not physical files, and we spend a lot of time forwading from here to there, trying to use relative references is not really recommended. -Ted. 10/18/2002 4:44:01 PM, "Taylor, Jason" <[EMAIL PROTECTED]> wrote: While this discussion is going on regarding 'relativity', I'd like to note that bug #12600 reports a problem with the form tag that seems related: Basically <form action="login.do"> always prepends the module context, making it impossible to specify a true relative link (like "login.do" rather than "/app/login.do" or "/app/module/login.do") which is sometimes desirable. Is it a bug or feature? I'm forced by my architecture to always specify relative links back to the browser, so I can't use the form tag as is. The bug description discusses the type of situation where this may arise... Any thoughts? -JT -----Original Message----- From: Eddie Bush [mailto:ekbush@;swbell.net] Sent: Friday, October 18, 2002 1:12 PM To: Struts Developers List Subject: Re: Going to other context and/or server in 1.1 Or - ... contextRelative is new to 1.1 (obviously). What if we replaced it with relativeTo. relativeTo could take on the values: application/module/absolute Then we're not just growing warts on the side for effect. Craig R. McClanahan wrote: >Failure case: https://www.mysecuresite.com > >Maybe we need an "absolute" attribute on ForwardConfig (and therefore >ActinForward)? > -- Eddie Bush -- To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>
