On Thu, 22 Mar 2012 14:31:09 -0300, IcedDante <ultimate_ham...@yahoo.com>
wrote:
When I use the <t:beaneditform object="game"/> in this scenario I will
only get the fields specific to game. Is it best practice here to create
a custom form that contains game and address fields or is there a better
way?
Yep. Or you can use BeanEditor instead of BeanEditForm:
<t:form>
<t:beaneditor object="game"/>
<t:beaneditor object="game.address"
<input type="submit"/>
<t:form>
If not, is there some way to automatically bind the fields from the form
to the
respective entity properties?
You could pass a customize BeanModel to the model parameter.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
