Red Hat Bugzilla – Bug 817040
HibernateRepository's save method does not returns persistent object with generated IDs in sportsclub example
Last modified: 2013-05-14 10:55:03 EDT
Description of problem:
The Hibernate*Repository classes in sportsclub-hibernate-dao subproject don't work properly. When the save method is called with newly created object, it doesn't return the persistent object with generated ID included (the ID remains null). This has only very little impact on the functionality of the example from the user perspective. The only way for the user to hit this problem is when sending WS request for paymentNotification, the response won't contain the generated ID of payment.
Version-Release number of selected component (if applicable):
Sportsclub example, spring 3.1 variant, sportsclub 'hibernate' ear
Steps to Reproduce:
1. build sportsclub example, spring 3.1 variant
2. deploy sportsclub-ear/target/sportsclub.ear (non-jpa ear)
3. use soapUI to send paymentNotification request
The returned response doesn't contain the return element with generated ID of newly created payment.
The response should contain the ID of payment.
I believe this is due to the way in which identity generated ids are handled in
I think this is caused by missing
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.
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.