[
https://issues.apache.org/jira/browse/TAP5-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Kemnade updated TAP5-1899:
---------------------------------
Labels: bulk-close-candidate (was: newbie)
This issue affects an old version of Tapestry that is not actively developed
anymore, and is therefore prone to be bulk-closed in the near future.
If the issue still persists with the most recent version of Tapestry (currently
5.4.0, available from Maven Central), please update it as soon as possible and
add '5.4.0') to the issue's affected versions.
> Tapestry BeanEditor should follow Persistence @Embedded
> --------------------------------------------------------
>
> Key: TAP5-1899
> URL: https://issues.apache.org/jira/browse/TAP5-1899
> Project: Tapestry 5
> Issue Type: Improvement
> Components: quickstart, tapestry-hibernate, tapestry-jpa
> Affects Versions: 5.3.2
> Reporter: Uday Kari
> Priority: Minor
> Labels: bulk-close-candidate
>
> Quick Intro:
> http://tapestry.1045711.n5.nabble.com/hibernate-Embedded-td2435807.html
> If an entity has an embedded entity which in turn has an embedded entity and
> so on...hibernate is able to generate a database table for the highest level
> entity using the properties of embedded entities. The corresponding create
> page in T5 should simply be, <t:beaneditform object="highestLevelEntity"/>
> and the list page should simply be <t:grid source="highestLevelEntities"/>.
> Right now the embedded entities do not showing up unless
> 1) bean model is customized for rendering the embedded entities. This means
> T5 gets in the way and adds a parallel interpretation to whatever hibernate
> is doing per JPA
> 2) the highest level entity features getters and setters to wrap the embedded
> entities
> 3) use Struts style dot notation to directly address embedded entities
> All of these approaches violate "Code Less, Deliver More". And this can be
> solved by using the principle "Follow Hibernate". Just read directly from
> the database just Hibernate successfully created and then used the @Embedded
> hierarchy to build the object model.
> There may be a case for arbitrary embdedded properties to be exposed only
> through bean model to the presentation layer...but for something being
> processed just fine by persistence layer, T5 should facilitate it as well.
> Lastly, this would really help quickstart a real world application.
> Otherwise T5 just replaces a whole lot of coding elsewhere.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
