Bugzilla – Full Text Bug Listing
| Summary: | Create JPA project and Add New JPA Entity and receive Stack Overflow Error | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [WebTools] Dali JPA Tools | Reporter: | Jolene Moffitt <jolene.moffitt> | ||||||
| Component: | General | Assignee: | Karen Butzke <karenfbutzke> | ||||||
| Status: | VERIFIED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | brian.vosburgh, karenfbutzke, nan.n.li, neil.hauge | ||||||
| Version: | 3.0 | Flags: | neil.hauge:
review+
|
||||||
| Target Milestone: | 3.0.2 | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows Mobile 2003 | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Jolene Moffitt
Update: So far Karen and I have been unable to reproduce this problem. I've actually been unable to have the code go down this execution path following the reproduction steps so this is definitely a bit strange. Will require some more investigation. Jolene, can you reproduce this over and over, or is it just something you saw once? Could you attache a project that produces this? This can be re-created over and over in Build I-3.4.0-20110822071621, however I got a new build this week Build I-3.4.0-20110826171354 and it works fine without error running the automated test suite and running the test manually per the steps listed. I got the latest builds on Monday for Maintenance 3.3.1-20110906011014 and Integration 3.4.0-20110904212209 and when I ran the automated tests Bug 355415 fails on the Integration Build but passes on the Maintenance build. I also ran it manually and can re-create it on the Integration build (If you check the key checkbox for one of the entity fields it happens everytime). FYI. I got the same error with the same steps today with the target platform of M-3.3.1-20110914031739. Created attachment 206596 [details]
proposed patch against 3.0 maintenance
This patch is against 3.0 maintenance, but it will be the same fix for 3.1
(In reply to comment #6) Is there a reason for the added getEntityMappings() method on AbstractOrmTypeMapping? Created attachment 206602 [details]
proposed patch against 3.0 maintenance
No there is not, originally I was calling getEntityMappings().getTextRange(), but decided to go with the Empty text range instead. This is really just working around the bug that the validation could run while the type mapping is in the process of being adding to the orm.xml. It prevents null text range exceptions out of the validation framework. With Brian's batch process code I think we should be able to get rid of this.
fixed in HEAD Yep...looks good. You probably already did this but you can axe the unused EntityMappings import after getting rid of that method. checked in for maintenance, yanked the import. Stupid team synchronize view doesn't remove my unused imports on save :) fixed Verified in Build M-3.3.2-20111117045640 Verified you can create JPA project without error using the steps and also running the Dali Automation Test Suite. See the link to view test steps for verification. http://wiki.eclipse.org/Dali_3.0.2 |