| Summary: | Validation and content assist don't handle changes to in-workspace schema | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] Dali JPA Tools | Reporter: | Paul Fullbright <paul.fullbright> | ||||
| Component: | JAXB | Assignee: | Paul Fullbright <paul.fullbright> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | neil.hauge | ||||
| Version: | 3.0 | Flags: | neil.hauge:
review+
|
||||
| Target Milestone: | 3.0.1 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows Vista | ||||||
| Whiteboard: | fix_ready | ||||||
| Attachments: |
|
||||||
|
Description
Paul Fullbright
Created attachment 197641 [details]
proposed patch
Adds two API methods to SchemaLibrary (a noextend interface):
refreshSchema(String namespace);
refreshAllSchemas();
The project refreshes all schemas before validation.
The type or package refreshes the schema with the appropriate namespace before content assist.
I assume the refresh would never be a long running operation? Define "long running"? Certainly no longer than adding the schema in the first place. And most likely significantly less than a validation run time. The times I've tested, the content assist had no (additional) lag time. fixed post 3.0 |