The code that builds up the field validation is pluggable; originally I was thinking in terms of Hibernate/EJB3 annotations, but it should be reasonble to handle all kinds of approaches. This part of the code and design is still very alpha (in flux).
On 2/21/07, Jiri Mares <[EMAIL PROTECTED]> wrote:
Hi Howard, T5 looks very good. I would like to ask about the screencast #4 where you presented BeanEditForm component. For validation there is the annotation, which causes me problems. I don't want to annotade my business objects with tapestry annotation (they start to depend on tapestry). At the moment we are using OVal (oval.sf.net) for the Design by Contract and the oval annotations carry the same information as the tapestry validate annotation. So will it be easy to use for validation these annotations (instead of the tapestry one)? Meaning if you are thinking about some kind of pluggable validation framework ... or at least pluggable validation definition framework. Thanks -- Jiří Mareš (mailto:[EMAIL PROTECTED]) ČSAD SVT Praha, s.r.o. (http://www.svt.cz) Czech Republic --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com
