[
https://issues.apache.org/jira/browse/TAPESTRY-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAPESTRY-2339.
------------------------------------------
Resolution: Fixed
Fix Version/s: 5.0.12
Yep, switching to Tapestry's PropertyAccess code (which will invoke the getter,
rather than reading the field) did the trick. Still not sure if this
represents a bug in Hibernate or just user error on our part, but it works and
that's what counts.
> The automatic ValueEncoder for Hibernate entities will sometimes encode an
> entity as null (rather than its primary key)
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-2339
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2339
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-hibernate
> Affects Versions: 5.0.11
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Priority: Critical
> Fix For: 5.0.12
>
>
> Still trying to figure out under which circumstances this can occur. It may
> be a Hibernate problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
