Why value is not a reserved parameter is as following :- One of the most imp point is that tapestry html pages can be directly opened in the browser and can give the same look and feel as they are seen when deployed.
But if you declare value as reserved parameter html developers cannot use value parameter when writing html . So thet cannot customise the text on the submit button. In your case if there are 2 value parameters in html it should not be a problem. Html takes what ever the first occurrence is. And all tapestry components make sure that their parameters occur first than what had written in html by html developers. Muralidhar Y Software Engineer, Adastrum technologies-Nikai groups, EmiratesGroup-I.T Division, Dubai, UAE. Mobile : 00971-50-2256149. http://www.adastrumtech.com http://www.mercator.aero (Keep Smiling. Be happy All The Time.) -----Original Message----- From: Jan Normann Nielsen [mailto:[EMAIL PROTECTED] Sent: 03 October 2005 17:57 To: [email protected] Subject: Submit component and "value" property Hi Is there any reason behind the choice that "value" is not a reserved parameter for the Submit component? If I use: <input type="submit" jwcid="add" value="Add" /> in a HTML page and want to localize the "value" attribute value in the page specification, I use <component id="add" type="Submit"> <binding name="listener" value="listener:add" /> <binding name="label" value="message:add" /> </component> But when the page renders, it gives me two "value" attributes, which I don't want. Until now, I have declared my own component ValueSubmit which makes "value" a reserved parameter and use that instead. But shouldn't "value" just be a reserved parameter in the Submit component so that this is not an issue? Best wishes, Jan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
