| Summary: | java.lang.NullPointerException in WeavingHookTransformer | ||
|---|---|---|---|
| Product: | [RT] Gemini.JPA | Reporter: | Christoph Laeubrich <laeubi> |
| Component: | Core | Assignee: | Michael Keith <michael.keith> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | 1.1.0 M1 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Christoph Laeubrich
Need more info. 1) What are the characteristics of the domain class(es) being woven? 2) Attach a sample reproducible test case if possible. With no other information we have no way of reproducing this problem. 3) The runtime environment (in PDE or standalone OSGi) 4) Please run with the GEMINI_DEBUG_WEAVING system property set (e.g. -DGEMINI_DEBUG_WEAVING=true) and post the output Thanks. Any update on this bug? 1) What are the characteristics of the domain class(es) being woven? I used simple DAO clases with one one to many relationship 2) Attach a sample reproducible test case if possible. I'll try to create one if i encounter the problem next time 3) The runtime environment (in PDE or standalone OSGi) Standalone OSGi with EclipseLink and Eclipse Gemini running in an equinox container 4) Please run with the GEMINI_DEBUG_WEAVING system property set (e.g. -DGEMINI_DEBUG_WEAVING=true) and post the output I'll try to do this nex time. Sadly I refactored the code where the problem occured due to changes in the system architecture, I hope the stacktrace still would give any usefull hints. I have looked over the WeavingHookTransformer.weave() method a number of times and I can't see anything that could produce an NPE except in a condition where one of the get methods of the WovenClass returned null. None of those methods should ever return null, though, so it's possible that Equinox has/had a timing issue that caused the woven class state to not be fully formed. Unless it happens again, though, I'm not sure how we would be able to pin down the offending conditions. Closing because I'm having a hard time believing it is a Gemini JPA bug. If it ever re-occurs then please reopen and we can take a look at what the root cause might be. |