You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Taha Hafeez (JIRA)" <ji...@apache.org> on 2012/06/17 05:05:42 UTC
[jira] [Closed] (TAP5-1938) The ValueEncoder for JPA entity types
should encode transient instances as null rather than throw an exception
[ https://issues.apache.org/jira/browse/TAP5-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Taha Hafeez closed TAP5-1938.
-----------------------------
> The ValueEncoder for JPA entity types should encode transient instances as null rather than throw an exception
> --------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1938
> URL: https://issues.apache.org/jira/browse/TAP5-1938
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-jpa
> Affects Versions: 5.3.3, 5.3.4
> Reporter: Dimitris Zenios
> Assignee: Taha Hafeez
> Fix For: 5.3, 5.4
>
>
> 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.
> Same bug for Tapestry-Hibernate was resolved from Howard
> https://issues.apache.org/jira/browse/TAP5-1641
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira