On May 4, 2009, at 5/45:19 PM , Thiago H. de Paula Figueiredo wrote:
Em Mon, 04 May 2009 18:58:24 -0300, Robert Zeigler
<robe...@scazdl.org> escreveu:
I think it would be useful, however, to be able to define the set
of validators to use in a message catalog.
+1 to that. By the way, I think it would be very nice to have
something like a pipeline to provide validation to fields. Support
for validation based on JPA, Hibernate, Hibernate Validator and Bean
Validation (JSR 303, still in beta) annotations or any other source
of validation rules (including message catalogs).
Well, the ValidationConstraintGenerator basically serves this purpose,
no? You can contribute any sort of constraint generator, neh?
For instance, the tapestry5-cayenne module contributes one that gleans
the validation info from mapping metadata.
That would entail a new ValidationConstraintGenerator, except...
there's no simple way for a ValidationConstraintGenerator
implementation to gain access to the message catalog for the page
or component that holds the component for which the constraints
should be generated. The behavior I described above is handled at
a level outside of the constraint generator. Still... if you add
an issue, I'll grab it and explore options.
At least we could use the global message catalog (app.properties).
Yeah.... but it would be nice to be able to tie things down a bit more
specifically to a particular page or component.
Robert
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
