Has this issue been solved, posted into JIRA? Tapestry should be doing, at the presentation level, EXACTLY what Hibernate is doing at the persistence level, taking cues from the @Embedded annotation.
There is simply no guesswork involved in this. In other words, If the registration object is embedded in the car. 1) The CreateCar.tml page should simply be <t:beaneditform object="car"/> 2) Index.Tml should simply be <t:grid source="cars"/> Right now, in both cases the Registration embedded object is ignored by T5 whereas Hibernate creates the table just fine... When you have a lot of embdedded entities that have to re-used across several entities, the customized bean model approach seems to be duplicating the getters and setters. This goes against the T5 philosophy "Code less, deliver more"... -- View this message in context: http://tapestry.1045711.n5.nabble.com/hibernate-Embedded-tp2435807p5635163.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
