Hi,
How about readonly="true" ???
http://struts.apache.org/2.1.8/docs/textfield.html
HTH,
Damo
On 11 November 2011 22:16, Marco Schwarz wrote:
> Hi,
>
> hidden tags and plain text solve my problem ...
>
> I find, when I disable components via jquery, client side I'm sure to
> find the same pr
struts.xml is like
http://struts.apache.org/dtds/struts-2.1.7.dtd";>
...
web.xml is like
http://java.sun.com/xml/ns/javaee";
xmlns:xsi="http://www.
struts.xml is like
http://struts.apache.org/dtds/struts-2.1.7.dtd";>
...
web.xml is like
http://java.sun.com/xml/ns/javaee";
xmlns:xsi="http://www.w3.or
The use of hidden fields to avoid the user changing those fields is a security
risk. You are still getting all the fields from the client's side, so the user
or somebody else (through a man-in-the-middle atytack) are still able to change
the value of those fields.
Sent via BlackBerry from T-Mobi
You are right, but the user must see the fields and I need the object
with all properties for call (JPA) persist method. what's the best
practice for this use case
I have one object and many roles any role can change a different
field ... Do I create a class for any roles?
Idea?
Thanks
Mar
I don't know how JPA works exactly, but I suppouse at some point in your
app you need to get the object from the database through JPA and upda
2011/11/12 Marco Schwarz
> You are right, but the user must see the fields and I need the object
> with all properties for call (JPA) persist method. wha
6 matches
Mail list logo