I was including the hidden fields in the base.jsp that all my tiles extend.
The reason the
result name="input" type="tiles">${#parameters.tile}
was not being populated is because the hidden fields were NOT in the
specific form that was being POST'ed. In order for this to work, developers
wo
I'm not sure what that error is, but you can use OGNL expression on results,
using ${expression}, and the request parameters are available in
#parameters, so yes, it should work :)
musachy
On 5/2/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Are you sure about this technique? I have the hi
Are you sure about this technique? I have the hidden field in my page and I
can see that it is set to the correct string, however, when this page is
POSTed, I get the following error. It appears that the hidden field is not
quite making it into the struts.xml result.
15:04:38,762 WARN org.apa
Is there a "soft" way to get the name of the tile definition into this
hidden field without hard coding it someplace? I really dislike coding
names and places beyond the XML file itself. I already have a BaseAction
that extends ActionSupport that is starting to make me ill! I really would
have
Thanks brother! Is this "old school" technique still used in S2? I would
have guessed S2 would hold on to previous request information in the
ActionContext so developers would no longer have to do this riff raff.
On 5/2/07, Musachy Barroso <[EMAIL PROTECTED]> wrote:
Struts never knows what is
Struts never knows what is *the page* that failed. The action gets an http
request, but it doesn't know what was the page, with the submit in it, that
caused the request. You can pass a hidden field with the name of the
page(let's say "inputPage"), and then have a result like this:
${#
6 matches
Mail list logo
