Bug 414688 - "null argument" exception in JPA project properties page after renaming a project back to its original name
Summary: "null argument" exception in JPA project properties page after renaming a pro...
Status: RESOLVED FIXED
Alias: None
Product: Dali JPA Tools
Classification: WebTools
Component: JPA (show other bugs)
Version: 3.3   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Brian Vosburgh CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 414723 414795
Blocks:
  Show dependency tree
 
Reported: 2013-08-08 13:11 EDT by Brian Vosburgh CLA
Modified: 2016-01-15 15:38 EST (History)
0 users

See Also:


Attachments
stack trace (7.61 KB, text/plain)
2013-08-08 13:11 EDT, Brian Vosburgh CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Brian Vosburgh CLA 2013-08-08 13:11:26 EDT
Created attachment 234206 [details]
stack trace

Renaming a JPA project twice, the second time back to the original name, will temporarily corrupt the project's preferences, resulting in an invalid JPA platform.

Steps to recreate:
- create a simple JPA project "Foo"
- rename the project to "Bar"
- rename the project back to "Foo"
- [attempt to] open the JPA project properties page (i.e. select the project in the Project Explorer and open the context menu and select "Properties", then select the "JPA" node in the Properties dialog)
- the JPA properties page will not display - instead an error dialog opens: "The currently displayed page contains invalid values."
- an exception stack traced is logged (see the attachment)

The JPA project properties page will not display because the JPA platform, as stored in the preferences, has a value of 'null', even though the underlying preferences file (with the appropriate JPA platform) was correctly moved to the new project.

Workaround: Restart the Eclipse workspace.
Comment 1 Brian Vosburgh CLA 2013-08-09 16:02:40 EDT
Fixing either of the "depends on" bugs will most likely fix this bug; but bug 414795 is really the root cause.
Comment 2 Brian Vosburgh CLA 2016-01-15 15:38:05 EST
Fix of bug 414795 fixed this bug.