struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Wu <...@globalmedic.com>
Subject RE: Automatic Form filing, Volatile property
Date Thu, 01 Feb 2001 15:01:05 GMT
My 2 cents worth:

This seems like a good general solution.  This way, the contract in the
documentation could read:
"UNLESS OTHERWISE SPECIFIED, all Struts form tags redisplay the previous
values from the corresponding form bean property"

One question that arises is should this be an attribute/property that is
applicable to all form elements or just a few (ie: password, textfield, text
area)?  Does anybody forsee the need for something like a volatile checkbox
or radio button?  


Eric Wu
Java Architect               
www.GlobalMedic.com
Tel.: 514.738.6770 / 1.888.986.3342
Fax.: 514.738.4827

Silver WWW Health Awards Winner
Globe & Mail  Top 25 e-Businesses in Canada - #5
http://www.globetechnology.com/site/specials/e-25/

Visit www.medalliance.ca, GlobalMedic's new healthcare network for
physicians, pharmacists, patients and consumers, developed in collaboration
with Les Éditions Santé Rogers Media. 

-----Original Message-----
From: Frederic BAGES [mailto:fredba@in-fusio.com]
Sent: February 1, 2001 4:22 AM
To: struts-dev@jakarta.apache.org
Subject: RE: Automatic Form filing, Volatile property



	Could we add a property that say : "Do not fill back this field". I
meen
that the password field is the more obvious field that do not need to
recover the previous value but in an electronic commerce web site the credit
card number will not have to be retreived as well.

	I suggest that any password field is left blank and that fields
marked as
"volatile" is also left blank.

	The biggest problem with filing back these fields is the history
option of
IE or netscape that could retreive all these field's values that are stored
in the html source.

	Frederic.



Mime
View raw message