Rober, <bean:write> tag allows to retrieve the value of the specified bean property and render it to the page as a String.
<html:hidden> tag and the resulting hidden field do more than what <bean:write> does. The value of the hidden field can be read/manipulated, and posted back to server. With the disabled attribute (to be added in the taglib implementation), the <html:hidden> tag provides consistent handling for dynamic situations. Thanks. -----Original Message----- From: Robert Lamping [mailto:[EMAIL PROTECTED] Sent: Thursday, October 16, 2003 2:30 AM To: Struts Users Mailing List Subject: RE: html:hidden, disabled attribute Dear Haiwei, >but sometime we want the hidden tag to be disabled so its value will not be posted to the server. What is then the purpose of have the hidden tag in it? You could also leave it out. You can always access a property using the <bean:write> tag. Kind regards, Robert -----Original Message----- From: Chen, Haiwei (H.) [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 14, 2003 1:42 PM To: 'Struts Users Mailing List' Subject: RE: html:hidden, disabled attribute Thanks for your response. We have a need to include a hidden tag in the form; but sometime we want the hidden tag to be disabled so its value will not be posted to the server. I have filed a bug report. The problem will be fixed in the future Struts releases. -----Original Message----- From: Robert Lamping [mailto:[EMAIL PROTECTED] Sent: Monday, October 13, 2003 6:38 PM To: Struts Users Mailing List Subject: RE: html:hidden, disabled attribute Haiwei, The purpose of the hidden tag is to keep the property and its value in the dataset of the form. And you will use it, when you don't want to expose the value to the user. Whereas the disabled attribute will exclude the property from the dataset in the request. For your information. When you would have a unique value for the item presented on the screen and you use <html:text disabled="true" .... >, then you will find out that the property for this unique value is not in your request. With the normal getters and setters, your unique value now gets blanked. "". And gone is your unique code. Hence, the hidden tag and the disabled attribute are more or less mutually exclusive. Kind regards, Robert Lamping -----Original Message----- From: Chen, Haiwei (H.) [mailto:[EMAIL PROTECTED] Sent: Monday, October 13, 2003 5:36 PM To: Struts Users Mailing List (E-mail) Subject: html:hidden, disabled attribute Does anyone know whether future Struts release will support the "disabled" attribute for the <html:hidden> tag? For some reason, it is not supported in the Struts 1.1. Does anyone know the reason behind that? Thanks. Haiwei --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
