Just out of interest, does any one know what the rational was for not making hidden fields part of the core codebase? Is it simply because Activation Contexts should be used in preference to hidden fields for keeping state between requests?

Bill Holloway wrote:
The tapestry5-components project on Google code features a Hidden
field component.  See:  http://code.google.com/p/tapestry5-components/

Bill @ peoplepad

On Sun, Oct 12, 2008 at 1:51 PM, Argo Vilberg <[EMAIL PROTECTED]> wrote:
hello

How to make hidden field in Tapestry5.

<input type="hidden" name="action" value="CANCEL">


<t:textfield type="hidden" t:id="signatureHex" t:value="signatureHex"/>

this textfield does not work.

Wich tapestry component i must use to use hidden form field?


Argo





--
SU3 Analytics Ltd
61b Oxford Gardens
W10 5UJ
London

Tel: +44 20 8960 2634
Mob: +44 75 2501 0825
www.su3analytics.com

SU3 Analytics Ltd is a company registered in England and Wales under company 
number 06639473 at registered address 61b Oxford Gardens, London W10 5UJ, 
United Kingdom.



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to