Re: T5 BeanEditForm screencast

2007-02-22 Thread Howard Lewis Ship
I think good design is sometimes about knowing what you DO know, and knowing what you DON'T know, and negotiating between the two. On 2/21/07, Jiri Mares <[EMAIL PROTECTED]> wrote: Very good design ... Howard Lewis Ship napsal(a): > The code that builds up the field validation is pluggable; or

Re: T5 BeanEditForm screencast

2007-02-21 Thread Jiri Mares
Very good design ... Howard Lewis Ship napsal(a): > 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 alph

Re: T5 BeanEditForm screencast

2007-02-21 Thread Howard Lewis Ship
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]> wr

T5 BeanEditForm screencast

2007-02-21 Thread Jiri Mares
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