Community
Participate
Working Groups
- Generate classes from in-workspace schema file (adds schema to project library). - Make changes to schema that will affect validation and content assist (e.g. change the name of an element) - JAXB model will not validate or provide content assist with respect to new version of schema, only the version as it existed when it was compiled. We'll likely need to reload schemas at certain points, perhaps at validation beginning and when content assist is invoked. There doesn't look to be a way to create an XSD model that stays in synch with its resource.
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
