You're not seeing any data in your action because your JSP doesn't
contain anything that would submit data. You have a form in your JSP,
but no input elements: all your data is just written to the page as
static text.
If you want a form to submit data, that form needs to include HTML input
el
Props to Rick as well. You were dead on.
-Original Message-
From: Rick Reumann [mailto:[EMAIL PROTECTED]
Sent: Friday, March 18, 2005 9:42 AM
To: Struts Users Mailing List
Subject: Re: ActionForm problem
Just curious, is your boolean getter autogenerated? It might be set up as
Props to Rick as well. You were dead on.
-Original Message-
From: Rick Reumann [mailto:[EMAIL PROTECTED]
Sent: Friday, March 18, 2005 9:42 AM
To: Struts Users Mailing List
Subject: Re: ActionForm problem
Just curious, is your boolean getter autogenerated? It might be set up as
input, y'all. It is all helpful to a guy who is
still pretty new at this stuff.
Hyrum
-Original Message-
From: Jeff Beal [mailto:[EMAIL PROTECTED]
Sent: Friday, March 18, 2005 8:54 AM
To: Struts Users Mailing List
Subject: Re: ActionForm problem
Did you change the types on both the gett
input, y'all. It is all helpful to a guy who is
still pretty new at this stuff.
Hyrum
-Original Message-
From: Jeff Beal [mailto:[EMAIL PROTECTED]
Sent: Friday, March 18, 2005 8:54 AM
To: Struts Users Mailing List
Subject: Re: ActionForm problem
Did you change the types on both the gett
Just curious, is your boolean getter autogenerated? It might be set up as
isSsnOnFile
which will work fine for booleans, but when you change to String it
needs to find getSsnOnFile. My guess is maybe you changed the type but
didn't change the syntax of the getter?
Hyrum wrote the following on 3/
Did you change the types on both the getter and the setter methods?
Did you keep a setter with the boolean type? I don't remember all of
the details, but I don't think that the following is a valid bean
property:
public String getSsnOnFile() { return ssnOnFile ? "Y" : "N"; }
public void setS
I would still like to know what the root problem is here, the tag thing
aside. Why can't the ValidatorActionForm see my value "ssnOnFile" when I
change the type from boolean to String?? Just for future reference, anyone
have any ideas??
-Original Message-
From: Hyrum [mailto:[EMAIL PROT
I would still like to know what the root problem is here, the tag thing
aside. Why can't the ValidatorActionForm see my value "ssnOnFile" when I
change the type from boolean to String?? Just for future reference, anyone
have any ideas??
-Original Message-
From: Hyrum [mailto:[EMAIL PROT
Leon Rosenberg wrote the following on 3/17/2005 5:37 PM:
Actually I was saying the opposite :-) EL makes your page looking
"uglier"...
I mean, you can write
${bean.boolProp?'Yes, I am an idiot':'No, not an idiot'}
Or
<% bean.boolProp?"Yes, I am an idiot":"No, not an idiot" %>
I think the idea of
You want to validate your input anyway. If user puts in
On Thu, 17 Mar 2005 18:03:16 -0700, Hyrum <[EMAIL PROTECTED]> wrote:
>
> ${bean.isIdiot ? "Yes, I'm an Idiot" : "No, I'm not an Idiot"}
>
This doesn't suffer from the dangerious content problem, because you
don't actually *emit* the contents of the isIdiot property -- you only
use it on the ser
I guess these things depend on sentiments that are not obvious. I
definitely like the wrote:
> So, if not using ugly, and I don't want wicked users inserting script tags, am I stuck with
> the original somewhere. The choose method works, but is there a better way? If you
> wanna talk about ug
So, if not using
Yes, I'm an Idiot
No, I'm not an Idiot
Is WAY uglier than
${bean.isIdiot ? "Yes, I'm an Idiot" : "No, I'm not an Idiot"}
even if the ugly way is safer. But that's just personal preference.
So, if not using
Yes, I'm an Idiot
No, I'm not an Idiot
Is WAY uglier than
${bean.isIdiot ? "Yes, I'm an Idiot" : "No, I'm not an Idiot"}
even if the ugly way is safer. But that's just personal preference.
>
> > I asked for an example where you actually need EL -> can't
> achieve the
> > same with (standard) tags.
>
> Oh, ok. No, you are right, all the EL expressions do is make
> my page look a little cleaner vs using c:out. Not that big of
> a deal I guess, however they are nice for certain th
>
> > I asked for an example where you actually need EL -> can't
> achieve the
> > same with (standard) tags.
>
> Oh, ok. No, you are right, all the EL expressions do is make
> my page look a little cleaner vs using c:out. Not that big of
> a deal I guess, however they are nice for certain th
Leon Rosenberg wrote the following on 3/17/2005 5:10 PM:
I asked for an example where you actually need EL -> can't achieve the same
with (standard) tags.
Oh, ok. No, you are right, all the EL expressions do is make my page
look a little cleaner vs using c:out. Not that big of a deal I guess,
how
> Not sure what you mean by the above the question and No, I'm
> not going to use XSLT:) XSTL is nice, but no way it's as easy
> to use as EL expressions in JSP. When I know I'm only going
> to be using JSP, EL is my friend.
I asked for an example where you actually need EL -> can't achieve the
> Not sure what you mean by the above the question and No, I'm
> not going to use XSLT:) XSTL is nice, but no way it's as easy
> to use as EL expressions in JSP. When I know I'm only going
> to be using JSP, EL is my friend.
I asked for an example where you actually need EL -> can't achieve the
Craig McClanahan wrote the following on 3/17/2005 4:22 PM:
The unsuspecting user who displays this page will be executing
whatever JavaScript code replaces "...". That doesn't happen if you
use (or in Struts) because, by default, the "<"
character gets emitted as "<" instead.
Very interesting. T
Leon Rosenberg wrote the following on 3/17/2005 4:22 PM:
Now really, is there a case where you actually _need_ JSTL / EL
functionality in
an MVC conform jsp?
Not sure what you mean by the above the question and No, I'm not going
to use XSLT:) XSTL is nice, but no way it's as easy to use as EL
e
> Expression evaluation doesn't filter out characters that are
> sensitive in HTML (like '<'). Consider a common case where
> you accept input from a user into a text field, store it in
> your database, and then display it (on a different page) with
> something like this:
>
> ${customer.n
> Expression evaluation doesn't filter out characters that are
> sensitive in HTML (like '<'). Consider a common case where
> you accept input from a user into a text field, store it in
> your database, and then display it (on a different page) with
> something like this:
>
> ${customer.n
Thanks, Craig, and thereyougo, Rick.
On Thu, 17 Mar 2005 13:22:41 -0800, Craig McClanahan <[EMAIL PROTECTED]> wrote:
> On Thu, 17 Mar 2005 16:18:25 -0500, Rick Reumann <[EMAIL PROTECTED]> wrote:
> > Dakota Jack wrote the following on 3/17/2005 4:08 PM:
> > > I think that Craig had mentioned that
On Thu, 17 Mar 2005 16:18:25 -0500, Rick Reumann <[EMAIL PROTECTED]> wrote:
> Dakota Jack wrote the following on 3/17/2005 4:08 PM:
> > I think that Craig had mentioned that there were some security issues
> > or something, however, with not using the > bother checking it out because I still use t
Dakota Jack wrote the following on 3/17/2005 4:08 PM:
I think that Craig had mentioned that there were some security issues
or something, however, with not using the wow, really? I'd like to know what they are. I love how much cleaner my
code is without having to use c:out everywhere.
--
Rick
---
I think that Craig had mentioned that there were some security issues
or something, however, with not using the wrote:
> Hyrum wrote the following on 3/17/2005 3:48 PM:
>
> >
>
> No, with Tomcat5.0 you dont' need the c:out just do:
>
> ${manageFilerForm.ssnOnFile?'Y':'N'}
>
>
> --
> Rick
>
Hyrum wrote the following on 3/17/2005 3:48 PM:
No, with Tomcat5.0 you dont' need the c:out just do:
${manageFilerForm.ssnOnFile?'Y':'N'}
--
Rick
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
t;", "lt", "==", "eq", "<=", "le", ">=", "ge", "!=",
"ne", "[", "+", "-", "*", "/", "div", "%", "mod", "and
t;", "lt", "==", "eq", "<=", "le", ">=", "ge", "!=",
"ne", "[", "+", "-", "*", "/", "div", "%", "mod", "and
Hyrum wrote the following on 3/17/2005 2:56 PM:
I have successfully populated a jsp with items from a ValidatorActionForm.
One of the properties is a boolean, and it is printing the word "true" on my
page, where I want a 'Y' or 'N'. So I changed the ValidatorForm so that the
property is a string.
32 matches
Mail list logo
