Community
Participate
Working Groups
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.
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.
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.)
Marking as WONTFIX. Paul, please reopen if you see fit.
