I can say it's not simple at all but I'm trying to comprehend it, specially that the code in the link you provided has some deprecated methods. But while I'm trying to master this, what if I need to apply validation too ?
I understand from the link you provided is that I have 2 choices, either to implement BeanModel<T> for editing or go a step back and implement a BeanModelSource (which according to the document "provides support to the model by generating validation information for individual fields.") After looking a bit into tapestry code I found that the BeanModelSource uses the Messages object to provide labels for the propertyes and most probably validation rules too but I still haven't found were is that yet.So the question is, what if I have those validation strings (maxLength=5,minLength=2..etc) in an independant string ? Because I intend to have this information in a database (label, name\id, validation rules). On Sun, May 20, 2012 at 3:44 PM, Thiago H. de Paula Figueiredo < thiag...@gmail.com> wrote: > On Sun, 20 May 2012 10:21:35 -0300, Muhammad Gelbana <m.gelb...@gmail.com> > wrote: > > Has anyone tried to edit a map instance using a bean editor ? >> > > Check http://tapestry.1045711.n5.**nabble.com/T5-Best-way-to-** > alter-core-components-**tp2408801p2408802.html<http://tapestry.1045711.n5.nabble.com/T5-Best-way-to-alter-core-components-tp2408801p2408802.html>. > Basically, you need to implement PropertyConduit instead of relyaing in > PropertyConduitSource, which works based on the class properties (getters > and setters). > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, > and instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br > -- *Regards,* *Muhammad Gelbana Java Developer*
