Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 312808 - edit and close orm.xml file without saving, JPA details view empty and removed from navigator tree
Summary: edit and close orm.xml file without saving, JPA details view empty and remove...
Status: CLOSED INVALID
Alias: None
Product: Dali JPA Tools
Classification: WebTools
Component: General (show other bugs)
Version: 2.3   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: 2.3 RC2   Edit
Assignee: Neil Hauge CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-13 11:49 EDT by Karen Butzke CLA
Modified: 2010-05-13 14:59 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Karen Butzke CLA 2010-05-13 11:49:03 EDT 
I am opening a bug against us because I'm not sure if this is a regression of a Dali bug or an xml bug.

Edit an orm.xml file and close it without saving.  Reopen the orm.xml file and the Jpa Details and structure view are empty.  Looking in the Project Explorer under JPA Content and you will see that the orm.xml file is not listed.  Do a project clean and the jpa details view work again , but the project explorer does not display the orm.xml file until you close the view and reopen it.
Comment 1 Neil Hauge CLA 2010-05-13 12:32:03 EDT 
This certainly seems like a regression.  Investigate for RC2.
Comment 2 Neil Hauge CLA 2010-05-13 14:00:19 EDT 
Update: So far I have been unable to reproduce any of this behavior in the RC1 candidate.
Comment 3 Paul Fullbright CLA 2010-05-13 14:09:09 EDT 
I can't reproduce in either head or the m7 build
Comment 4 Karen Butzke CLA 2010-05-13 14:59:34 EDT 
Well, fortunately there was a change sitting in my workspace that I thought was a good idea for preventing unnecessary updates when xml resources are modified.  Obviously not a good idea since it's causing this bug.  Good thing I was waiting until we branch to check it in :) Now to continue testing in a build instead of from within eclipse.