[
https://issues.apache.org/jira/browse/TAP5-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17864075#comment-17864075
]
Ben Weidig commented on TAP5-2783:
----------------------------------
Thanks for the detailed issue description and pull request!
So far, I couldn't pin down TAP5-2754 at least not enough to create a
reproducible environment to trigger it in a test :(
Disabling support for composite identifiers with @IdClass makes sense, but I'd
add a warning log message so the feature does not just silently not work.
> Hibernate module initialization fails when entities with compound ids exist
> ---------------------------------------------------------------------------
>
> Key: TAP5-2783
> URL: https://issues.apache.org/jira/browse/TAP5-2783
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-hibernate
> Affects Versions: 5.8.6
> Reporter: Hendrik Noot
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The Tapestry Hibernate module throws a null pointer exception during
> initialization when entities with compound ids exist and it tries to build a
> value encoder for such an entity. This is because the implementation is
> specific to entities with a single id, so it never worked.
> This could be solved by ignoring these entities or implementing support for
> compound ids.
> Since no one filed a bug for this yet I would suggest ignoring them and will
> provide a pull request.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
