I have used a similar construct quite a bit, but normally, I refer to
parameters like this -
view
not view
In cases like this, I just want to affect the way a view is rendered.
So, leaving the getter/setter off of the action is the way to go.
-Wes
On Tue, Dec 22, 2009 at 6:05 AM, foo bar w
I think that the correct test is:
yes
2009/12/22 foo bar
> Hi all,
>
> I'm testing for the existence of a request parameter in a jsp page in
> Struts 2
>
> <%@ taglib prefix="s" uri="/struts-tags"%>
> "http://www.w3.org/TR/html4/strict.dtd";>
>
>
> yes
>
>
> no
>
>
> But, whatever I do,
Yes, parameters are String arrays. As a side note, see the following
post because sometimes OGNL evaluates things differently:
http://www.mail-archive.com/user@struts.apache.org/msg80015.html
2009/12/22 foo bar :
> Hi,
>
> I would prefer not to use getter/setter.
> What I really want to know is,
Hi,
I would prefer not to use getter/setter.
What I really want to know is, why is this not working as expected ?
Anyway, I solved it
#parameters.messageKey is of type String[], which make sense now
On Tue, Dec 22, 2009 at 9:46 PM, Saeed Iqbal wrote:
> If it is a request parameter, then mak
If it is a request parameter, then make a setter for it to get set and
getter to retrieve it and use % instead of #
If you want to have the parameter in the page context use the s:set with id
On Tue, Dec 22, 2009 at 3:36 PM, foo bar wrote:
> Hi all,
>
> I'm testing for the existence of a requ
Hi all,
I'm testing for the existence of a request parameter in a jsp page in Struts 2
<%@ taglib prefix="s" uri="/struts-tags"%>
http://www.w3.org/TR/html4/strict.dtd";>
yes
no
But, whatever I do, result is always "no"
Tested with these cases:
test.jsp
test.jsp?messageKey=
test.jsp?messa
6 matches
Mail list logo
