Bug 817040
| Summary: | HibernateRepository's save method does not returns persistent object with generated IDs in sportsclub example | ||
|---|---|---|---|
| Product: | [Retired] JBoss Enterprise WFK Platform 2 | Reporter: | Tomas Repel <trepel> |
| Component: | Spring | Assignee: | Rodney Russ <rruss> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Tomas Repel <trepel> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 2.0.0.ER4 | CC: | kpiwko, mnovotny |
| Target Milestone: | --- | ||
| Target Release: | 2.2.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | sportsclub | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-05-14 14:55:03 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Tomas Repel
2012-04-27 13:48:11 UTC
I believe this is due to the way in which identity generated ids are handled in Hibernate. I think this is caused by missing org.springframework.orm.hibernate3.support.IdTransferringMergeEventListener registered in sessionFactory chain. If this is a spring 3.1 only issue, I guess it happens due to missing support for Merge in Hibernate4 support in Spring and application needs to be rewritten to handle merge in DAOs. Fixed fixed Still not fixed in WFK2 ER8. The link in previous comment has nothing to do with Sportsclub, it points to some fix in Petclinic example. my mistake, the fix is at http://git.app.eng.bos.redhat.com/?p=snowdrop/snowdrop-examples.git;a=commitdiff;h=eaaa3b0bae3704e997516f76f567240342f8f680;hp=2565c63c3a23c5faf806862fb899579b65881063, but I didn't rebuild sportsclub due my mistake and imagination it was in petclinic, Bumped target version to 2.1.0. Per triage with mbg, kpiwko, mnovotny, move to WFK 2.2. This issue is not reproducible anymore. It was fixed, see comment 7 Tomas, if the commit at http://git.app.eng.bos.redhat.com/?p=snowdrop/snowdrop-examples.git;a=commitdiff;h=eaaa3b0bae3704e997516f76f567240342f8f680;hp=2565c63c3a23c5faf806862fb899579b65881063 is what should have fixed that, it is in WFK 2.2.0.DR1. So I will change the status and you can verify it (I know you already did) - set correct status field value. Verified in WFK 2.2.0.DR1. Closed as CURRENTRELEASE, part of WFK 2.2.0 distributables. |