Slow validation & search for declaration in GML application

[mhppn]

Hi,

I'm creating a GML application schema using Oxygen. Although it does not have that many types & elements, validation and search for declarations is very slow.

An example for the searching of declarations: When selecting the TreeSpeciesType in the TreeSpecies-element below the search should just yield the declaration in the next line. However, a dialog pops up "searching for component dependencies" and I have to wait for "calculating ressource dependencies".

Code: Select all

<xs:element name="TreeSpecies" type="TreeSpeciesType" substitutionGroup="gml:Definition"/>

<xs:complexType name="TreeSpeciesType">

...

I do not encounter this problem in other schemata. I suspect the imports/includes from online ressources could be the problem? However, even if I use a local copy of the GML base schema it uses such imports/includes itself, e.g., to XLink or GMD... Shouldn't there be some kind of caching of such remote imports?

Any suggestions?

Regards
Martin

[adrian]

Hi,

If you have remote imports or includes in the schema hierarchy, Oxygen will go online to retrieve them when searching for declarations. There is no caching in this case.
The imported/included schemas are cached for automatic validation or when explicitly invoking the cached validation: Document > Validate > Validate (cached) (there's a corresponding action in the toolbar, in the validation drop down list).

Either way, whenever possible, for best performance we recommend using an XML catalog and a local copy of the remote schemas.
Working with XML Catalogs

Regards,
Adrian

[mhppn]

Thank you very much. After downloading copies of all (recursively) imported XSDs and creating a catalog file validation and search for declaration is way faster!

However, the task was quite tedious. Wouldn't it be a nice feature for Oxygen to derive such a catalog including all the XSD copies? Seems like a highly automatable task...

[adrian]

Hi,

We already have a request logged on our issue tracking tool for providing the possibility of downloading a local copy of an entire schema hierarchy in one step. The creation of an XML catalog will probably be an option.
I've added your vote for this feature request. We will notify this thread when it is implemented.

Regards,
Adrian