1) You can have a Controller (org.apache.struts.tiles.Controller) and in the "perform" you can get the "original" request url and save it as a "request" attribute; and the tile can pull that request attribute. You can specify the controller class for your tiles definition. Just Before the jsp is rendered the controller is called and so the tile has the original url available in the request.
2) You can do the same thing in the BaseAction as well. (You can also have a custom ActionMapping and set the url in the request for only a set of actions for which a property in the custom ActionMapping is enabled). Regarding the request parameters not having the original values; I don't see any reason why unless you are redirecting. On Mon, 10 Jan 2005 17:20:21 -0800, Rick Mann <[EMAIL PROTECTED]> wrote: > Hi. We have a tiles-based webapp. Buried down deep in a tile that gets > reused in a few different pages is the need to render a link back to > the current request, with a parameter added. This acts as a switch to > re-render the page a bit differently. > > Unfortunately, request.getRequestURL() reflects the included file (in > this case, the layout JSP used) and NOT the request in the address bar > of the browser. > > Also available to the tile are SOME of the request parameters (all of > the names are there, but they have null values, and not the values > specified in the original request). > > What's the best way to get at this "original" information? > > TIA, > > -- > Rick > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
