[
https://issues.apache.org/jira/browse/TAP5-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17893101#comment-17893101
]
Hudson commented on TAP5-2783:
------------------------------
SUCCESS: Integrated in Jenkins build Tapestry ยป tapestry-trunk-freestyle #269
(See
[https://ci-builds.apache.org/job/Tapestry/job/tapestry-trunk-freestyle/269/])
added an entity with compound ids to TestApp0 to reproduce the problem
described in TAP5-2783 (thiago: rev 6ca885159011279986589b5b184c794d164e76db)
* (add)
tapestry-hibernate/src/test/java/org/example/app0/entities/CompoundIdEntityPK.java
* (add)
tapestry-hibernate/src/test/java/org/example/app0/entities/CompoundIdEntity.java
Fix for TAP5-2783 (NPE on init of the HibernateModule when entities with
compound ids are used) (thiago: rev 2c48bb7a90e2f725e0ec62f5896046c0e19a311d)
* (edit)
tapestry-hibernate/src/main/java/org/apache/tapestry5/hibernate/web/modules/HibernateModule.java
> 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
> Assignee: Ben Weidig
> Priority: Major
> Fix For: 5.9.0
>
> Time Spent: 0.5h
> 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)
