[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2834?page=c...
]
Vincent Sevel commented on HHH-2834:
------------------------------------
a '1' slipped through the hole. the bug I am referring to is HHH-2521.
specifically the change made in TypeFactory, line 535. this is eventually leading to a
null pointer (check file test_code_and_exception.txt).
Object[] targetComponentValues = componentType.getPropertyValues( target[i], session );
java.lang.NullPointerException regression between 3.2.2 and 3.2.3
(related to HHH-252)
---------------------------------------------------------------------------------------
Key: HHH-2834
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2834
Project: Hibernate3
Issue Type: Bug
Components: core
Affects Versions: 3.2.2, 3.2.3
Environment: Hibernate version:3.2.3
Hibernate annotations version:3.3.0
Hibernate entity manager version:3.3.1
Hsqldb 1.8.0
Reporter: Vincent Sevel
Attachments: sources.txt, test_code_and_exception.txt
Code that was working in 3.2.2, now throws a null pointer in 3.2.3 after bug HHH-252 was
fixed.
In the stack trace belowe, a FixedLoanDepositInstrumentEty instance is created and
merged. The embedded contractRef is null.
When the new code in TypeFactory.replaceAssociations() gets executed, there is an attempt
to get field values from the null component, which leads eventually to the exception.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira