Aaron,
Unfortunately frameworks are ideally all about good design and best
practices... and yes are dogmatic by their very existence... a little
ironic isn't it... in fact I wouldn't be surprised if Stripes was
implemented this way deliberately to force avoiding bad practices... but
can't be
Nikolaos,
Let me get back on topic by rephrasing my original question: why the value
of the value attribute disappears from the generated HTML? Documentation
states that, if present, the value attribute provides
A default value for the form field. Can be a literal value, or an EL
Hi Aaron,
Am 29.07.2010 12:50, schrieb Aaron Stromas:
Let me get back on topic by rephrasing my original question: why the
value of the value attribute disappears from the generated HTML?
Documentation states that, if present, the value attribute provides
A default value for the
Yes, absolutely. Thank you, Marcus.
-a
On Jul 29, 2010, at 8:56, M.C.S. m...@syn-online.de wrote:
Hi Aaron,
Am 29.07.2010 12:50, schrieb Aaron Stromas:
Let me get back on topic by rephrasing my original question: why the
value of the value attribute disappears from the generated HTML?
Greetings,
My application has a counttry property whose value eventually will be input
in the form but for now is defaulted to US, so I attempted to put it in
the hidden field in the JSP:
stripes:hidden name=country value=US/
The generated HTML is
input type=hidden name=country value=/
The
Aaron,
You shouldn't avoid hard-coding values in a JSP... even if it something
as simple as a default value.
Have you tried putting the value as a constant in your action bean and
referring to it from there?
(the idea is if you have multiple JSPs then the value need only be
maintained in
Hi Nikolaos,
Yes, initializing property in action works fine. I think that in this case my
initial design is better, because I have to change the JSP later anyway, and it
would be only change to the JSP only. Now I have to make change in two places
-a
On Jul 28, 2010, at 12:17, Nikolaos
Nikolaos Giannopoulos wrote:
Aaron,
You shouldn't avoid hard-coding values in a JSP... even if it
something as simple as a default value.
Ha... er... should avoid
Have you tried putting the value as a constant in your action bean and
referring to it from there?
(the idea is if you have
I understood
On Jul 28, 2010, at 13:22, Nikolaos Giannopoulos nikol...@brightminds.org
wrote:
Nikolaos Giannopoulos wrote:
Aaron,
You shouldn't avoid hard-coding values in a JSP... even if it something as
simple as a default value.
Ha... er... should avoid
Have you tried putting
Aaron,
Glad to see it works :-) I corrected my typo before seeing your reply... .
You are free to do what you like in the JSP... but don't say it is
better design... because unfortunately it isn't... . Scriplets and hard
coding in JSPs is bad design period :-)
Yes - if there is one
Hi Nikolaos,
Am 28.07.2010 21:08, schrieb Nikolaos Giannopoulos:
Aaron Strmas wrote:
I think that in this case my initial design is better, because I have
to change the JSP later anyway, and it would be only change to the
JSP only. Now I have to make change in two places
But I'm curious
I don't see why a body would be more important than an attribute; do
you have an example of a tag for which this is the case?
What you could do is use a regular HTML input tag; that way, you can
be certain that Stripes won't change its value.
Levi
Op 17 sep 2009 om 05:09 heeft Brandon
Hi Levi,
using the regular HTML tag results in losing encrypted fields. I would
be glad if there was a way to use the s:hidden field like a regular
tag (value over bean field) - to be able to use the encryption support.
Marcus
Levi Hoogenberg schrieb:
I don't see why a body would be more
13 matches
Mail list logo
