NPE in true OneToOne if classes processed out of order

tailwaggers · **Joined:** Sat Mar 04, 2006 10:20 pm **Posts:** 3

I'm getting an NPE if I have a true OneToOne bidirectional and the @PrimaryKeyJoinColumn class gets processed after the side with mappedBy=.

The error occurs on this line:

Code:

if ( otherSideProperty.getValue() instanceof OneToOne ) {

in OneToOneSecondPass.java because otherSideProperty is null.

Changing the order of the classes handed to AnnotationConfiguration works around the problem.

Should I submit a JIRA issue?

Hibernate version: 3.2.0.cr4
Hibernate Annotations version: 3.2.0.cr2
Partial stack trace:

Caused by: java.lang.NullPointerException
at org.hibernate.cfg.OneToOneSecondPass.doSecondPass(OneToOneSecondPass.java:135)
at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1054)
at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:296)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1210)
at com.anystream.acm.tx.impl.SessionCreatorFactory.buildSessionFactory(SessionCreatorFactory.java:117)
at com.anystream.acm.tx.impl.SessionCreatorFactory.buildSessionCreator(SessionCreatorFactory.java:84)
at com.anystream.acm.tx.impl.SessionCreatorFactory.createCoreServiceImplementation(SessionCreatorFactory.java:46)

emmanuel · **Posted:** Thu Sep 28, 2006 11:42 am

yes open a case, the ordering should have been taken care of

emmanuel · **Posted:** Thu Sep 28, 2006 11:42 am

please attach a runnable test case

kockas · **Joined:** Sat Jun 03, 2006 5:36 pm **Posts:** 8

Hi, I've same problem and same exception. (and same workaround)
I'm using Spring & Hibernate. It looks like the property is not within class.
When this will be fixed? Is this in Jira?

I use Hibernate Annotations 3.2.0GA
Thanks.

emmanuel · **Posted:** Mon Dec 04, 2006 4:46 pm

check the jira roadmap it might already be fixed in the user has provided a runnable testcase. Otherwise, open a jira issue with a runnable testcase

heapifyman · **Joined:** Tue Dec 05, 2006 2:06 pm **Posts:** 2

Hello.

I've got the same exception when tryin to deploy EJB3 beans in JBoss 4.0.4GA.
I couldn't find any issue in Jira related to this topic. So, is it already resolved?
I don't know if the JBoss guys plan to integrate a newer version of hibernate into their ejb3 implementation, so can anyone please give me a hint on how to use this workaround you mentioned?

Thanks in advance.

emmanuel · **Posted:** Thu Dec 07, 2006 1:19 pm

Put pressure on the EJB3 team

heapifyman · **Joined:** Tue Dec 05, 2006 2:06 pm **Posts:** 2

Quote:

Put pressure on the EJB3 team

Yeah, right. ;) So, I guess this issue is resolved in newer versions of hibernate?

Anyway, I had an error in my model, so now I don't get the exception anymore and everything seems to work for now.

danielamadei · **Posted:** Fri Dec 08, 2006 3:45 pm

Hi All,

Any updates on this? I did not find any JIRA for this bug and I recompiled using the latest annotations sources and got the same problem.

[]s
Daniel

emmanuel · **Posted:** Sun Dec 17, 2006 4:49 pm

ah, can you open a JIRA issue with a runnable test case. I'll need to have a look at it.