Let's say I have a hyperlink to the action that is mapped to "/actor/viewsearch".
If I use this construct, where controllerPath is equal to whatever would cause the controller servlet to be invoked, say "/control":
<html:link page="${controllerPath}/actor/viewsearch">I have complete success when path mapping is used. Let's say someone maps the controller to "/", I just set controllerPath to "", and it still works. Also, it still works whether the application itself has a named context or is in the default context.
Now, let's say we switch to extension mapping. Now the controller servlet is invoked by "*.do". I set my controllerPath variable again to be "", and all works great, except for one thing.
When you set the action parameter to html:form to "/actor/viewsearch", the html:form tag properly appends the .do suffix to this, making the action URI "/actor/viewsearch.do" -- the way it should be. However, the above html:link tag does not do this. So I would need to manually go through and change that hyperlink to "${controllerPath}/actor/viewsearch.do". If the extension was changed, my hyperlink would need to change again.
I have a feeling I am missing something here. I tried fiddling with the action attribute to html:link, rather than the page attribute, but that didn't seem to do it. . . . . Or am I thinking about extension mapping the wrong way?
Erik
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
