You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Massimo Lusetti (JIRA)" <ji...@apache.org> on 2011/03/30 09:45:05 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13012872#comment-13012872 ]
Massimo Lusetti commented on TAP5-1487:
---------------------------------------
I've had a patched version since day one due to this one... How will you handle it? I did an advice which intercept the call and merge the session back when it's time...
> 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.0, 5.2.5
> Reporter: 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