You're right. I should have read the documentation more closely. It clearly states that no stack is created and you have to access the parameters through the regular servlet objects. If you believe this is a shortcoming, you could register a JIRA issue for it, unless there is one already.
Nils-H On Fri, Feb 27, 2009 at 5:23 PM, hernan gonzalez <hgonza...@gmail.com> wrote: >> I was not able to do it, despite trying a million different forms as well as >> suggestions by some folks in strust mailing list. >> I do not think you will be able to access the param value passed to >> s:include within struts tag [clearly an obvious shortcoming]. Your best bet >> is using jsp expression language as the parameter is put in request scope. >> > > Indeed a shortcoming, and a frustrating one. > Wouldn this be partially fixed if, when the s:include/s:param are > evaluated, the params are also put into the "parameters" object in the > ActionContext? Are there good reasons to not doing so ? > > > BTW, although I much prefer Struts2 over Struts1, the fact that many > developers -not gurus, but with some months of s2 experience- > frequently need to try "million different forms" ( # % $ .... params > parameters etc etc) till (in the best scenario) it happens to work, > should tell something... > > > Hernán J. González > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@struts.apache.org > For additional commands, e-mail: user-h...@struts.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
