tionState
> >> private Registration registration;
> >>
> >> public Registration getRegistration(){
> >> return registration;
> >> }
> >>
> >> public void setRegistration(Registration registration) {
> >
this.registration = registration;
>> }
>>
>> }
>>
>> CODE Home.page
>>
>> > "-//Apache Software Foundation//Tapestry Specification 3.0//EN"
>> "http://jakarta.apache.org/tapestry/dtd/Tapestry_3_0.dtd";>
>>
gt;
>
>
> So suggest me...
> And also suggest about some useful tutorial with example
> As all the books are paid (No Free ebooks are available for tapestry
> though its opensource)
>
--
View this message in context:
http://www.nabble.com/BeanEditForm-Screencast-tp2115
}
}
CODE Home.page
http://jakarta.apache.org/tapestry/dtd/Tapestry_3_0.dtd";>
So suggest me...
And also suggest about some useful tutorial with example
As all the books are paid (No Free ebooks are available for tapestry though
its opensource)
--
View this message in context:
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
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
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
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