[
https://issues.apache.org/jira/browse/TAP5-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103091#comment-13103091
]
Hudson commented on TAP5-1641:
------------------------------
Integrated in tapestry-trunk-freestyle #516 (See
[https://builds.apache.org/job/tapestry-trunk-freestyle/516/])
TAP5-1641: Encode transient instances as null
The ValueEncoder for Hibernate entity types should encode transient instances
as null rather than throw an exception
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1169936
Files :
*
/tapestry/tapestry5/trunk/tapestry-hibernate/src/main/java/org/apache/tapestry5/internal/hibernate/HibernateEntityValueEncoder.java
*
/tapestry/tapestry5/trunk/tapestry-hibernate/src/test/java/org/apache/tapestry5/internal/hibernate/HibernateEntityValueEncoderTest.java
> The ValueEncoder for Hibernate entity types should encode transient instances
> as null rather than throw an exception
> --------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1641
> URL: https://issues.apache.org/jira/browse/TAP5-1641
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-hibernate
> Affects Versions: 5.3
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.3
>
>
> The current behavior gets in the way in many cases, such as creating a single
> page that will either edit an existing entity or editing a newly created
> entity before its first save, where the instance (transient or persistent) is
> stored as page activation context.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
