If you just need to hardcode some parameters, you can do that using a forward. If the parameters are being passed dynamically, the mapping is passed to the page in the request scope, and so you could query it from there, using an expression. You could also have the action expose the action path, or any other path, in request scope before passing it down to the page.
Though, personally, I don't see what's "unwieldy" about having the Action create a map. It's actually a very clean and easy solution.
Anyway, you can always file an enhancement request. But this is a volunteer project, and all the Committers seem to have demanding day jobs these days. So, many times, something won't get done unless someone needs to use it themselves. Right now, the best way to get a feature into the tag library would be to implement it and offer up a patch.
(See also the "[FRIDAY] Job Jar" post).
-Ted.
Rick Mann wrote:
I once requested that html:link et al. be modified to allow nested tags to add parameters. I was told that the JSTL version of html:link allowed this.
I've been reluctant to try to use the JSTL version based on the assumption that the JSTL verison would not know anything about Struts actions. It helps us tremendously to be able to specify the action without knowing exactly where the action is going to be in the path namespace.
Does the JSTL know about actions? Can it determine the appropriate path to an action based strictly on the action name?
If not, then my original request stands: I'd like to be able to add parameters to an html:link tag without going through the very unwieldy map option.
Thanks!
-- Ted Husted, Struts in Action <http://husted.com/struts/book.html>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
