it's more of an HTML thing than Tapestry - if a field is marked disabled - then it doesn't figure in the HTTP request that the Browser sends to the server.
and hence tapestry in turn will not assign these values, as they're not part of the HTTPRequest at all. On 10/15/06, Jabbar <[EMAIL PROTECTED]> wrote:
Hello, Thank you all for your help :)))) I have sorted the problem after a very long time... I have a page which shows all the properties of List<CelloChannel>. On the page I have a disable button which disables the textfield for two of the properties. After rewind I couldn't understand why tapestry wasn't assigning properties from the disabled textfields and why those properties were showing their default type values. The lesson learnt is tapestry won't assign disabled textfield values to bound properties. Which is logical. I feel happy and very tired ...
