This is a diff of the latest commit in the trunk:

*** 
jakarta/tapestry/trunk/framework/src/documentation/content/xdocs/tapestry/ComponentReference/TextField.xml
  2006/01/26
19:28:43        372591
--- 
jakarta/tapestry/trunk/framework/src/documentation/content/xdocs/tapestry/ComponentReference/TextField.xml
  2006/03/11
20:54:27        385164
***************
*** 99,107 ****
    Reserved parameters: name, type, value
  </p>

! <p>
! The TextField component supports all of the validation logic covered
in the <link href="../../UsersGuide/validation.html">Users
Guide</link>.
! </p>

  </section>

--- 99,106 ----
    Reserved parameters: name, type, value
  </p>

! <p>A TextField may be decorated by the Form's validation delegate,
but does not have a validator, so is limited in editting properties
types
!   beyond string.  In most cases, the &ValidField; component is preferred. </p>

  </section>


I've already posted in the user list without receiving any response
but I think is clearly erroneous.

Isn't it true that TextField supports all the validation logic covered
by the new Validation framework?
I'm using a lot of validators and translator binding prefix with a lot
of TextField with both 4.0 and 4.0.1 and they work pretty well... am i
missing something pretty obvious?

Thanks
--
Massimo
http://meridio.blogspot.com

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

Reply via email to