Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 363518

Summary: editing a schema does not cause validation to run
Product: [WebTools] Dali JPA Tools Reporter: Karen Butzke <karenfbutzke>
Component: JAXBAssignee: Paul Fullbright <paul.fullbright>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: neil.hauge, paul.fullbright
Version: 3.1   
Target Milestone: 3.3   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Karen Butzke CLA 2011-11-10 13:48:52 EST 
Editing a schema that is in your workspace does not cause validation to run. You have to do a project clean or project validate to get validation errors to appear that are related to the schema changes.
Comment 1 Neil Hauge CLA 2011-12-28 10:48:34 EST 
We need to determine if this should be a user controlled refresh or based on schema change.

If the former, perhaps we need a specific "Refresh" action on the schema, similar to what DTP offers.
Comment 2 Paul Fullbright CLA 2011-12-28 10:56:44 EST 
The problem is that there are several different ways to associate a schema with a JAXB project.

You can choose a workspace schema in the JAXB project. (this is what is described above)
You can choose a workspace schema not in the JAXB project.
You can choose a file system schema which happens to be a schema in the project or  workspace.
You can choose an XML catalog schema which happens to be a schema in the project or workspace.

This problem is exacerbated by the fact that the schema model doesn't actually change when the schema file is changed.  A reload has to occur.

I'm not sure how you'd trigger all JAXB projects (if they exist) to be validated if any schema in the workspace changed.  I think this probably has to remain a manual validation (or something that gets picked up on the next user edit of the JAXB files.)
Comment 3 Neil Hauge CLA 2013-05-09 17:10:29 EDT 
Marking as WONTFIX.  Paul, please reopen if you see fit.