You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2011/09/23 21:43:26 UTC
[jira] [Resolved] (TAP5-1487) The Hibernate "entity" persistent
field strategy should handle transient objects (by value) as well as
persistent object (by entity name and id)
[ https://issues.apache.org/jira/browse/TAP5-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship resolved TAP5-1487.
----------------------------------------
Resolution: Won't Fix
Assignee: Howard M. Lewis Ship
Duplicate of TAP5-1641, which handled the situation by serializing a null
> The Hibernate "entity" persistent field strategy should handle transient objects (by value) as well as persistent object (by entity name and id)
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1487
> URL: https://issues.apache.org/jira/browse/TAP5-1487
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-hibernate
> Affects Versions: 5.3, 5.2.5
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
>
> You have to jump through some amazing hoops otherwise, when you want the same page to store a transient persistent when creating an object, and a true persistent when editing an object.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira