Good answer :-) Thanks Howard!
Tim. On Sunday 04 March 2007 07:12, Howard Lewis Ship wrote: > Don't mistake the convenience of the annotations for an > annotations-only approach. > > Tapestry can automatically build the necessary BeanModel (used by > BeanEditForm and Grid), or you can provide the BeanModel in code (say, > from a reusable service), or mix and match the two. > > I'm not saying its perfect (yet :-), I'm just saying look a little deeper. > > On 3/3/07, Tim Sawyer <[EMAIL PROTECTED]> wrote: > > Hi Folks, > > > > The new Tapestry 5 stuff relies heavily on annotations of the model, > > rather than XML files, and it looks good. > > > > However, our model is fixed and used for many applications for multiple > > customers - we therefore can't make application specific annotations in > > the model. > > > > Is there some way being considered for T5 to handle this situation? > > > > Cheers, > > > > Tim. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
