Re-Validate: Button?

[mariomueller]

Hi all,

I am new to the editor and I wonder how to re-validate a XML after a modification in the XML?

I had an error in a XML that refers to a XSD. After fixing the error in the XML and saving the XML, the error statement is still in the "oXygen task bar".
What do I have to do, that a re-validation gets processed after saving? (Altovas XMLSPY has this feature)

Thanks
Regards
Mario

[adrian]

Hello,

By default Oxygen already automatically validates the document as you type, so as soon as you make a change and pause the document gets validated again. However, such an automatic validation does not update or clear the list of errors from the results panel. Only a manual validation (Document > Validate > Validate / Ctrl+Shift+V) does this.
So, if you validated the document manually and got a list of errors in the results panel, after fixing the errors in the document you have to trigger a manual validation again so that the list gets cleared. This can also be done automatically on Save, if you enable the option Check errors on save in Options > Preferences, Editor > Open/Save.

Regards,
Adrian

[mariomueller]

Hi adrian,

thanks for your reply. Seems to work. But now I got another problem. The validation takes 3 Minutes!
The XSD and the XML are both local files (no network traffic)
The XSD has 12925 lines! In XMLSPY it takes just a second. Do I something wrong?

Thanks
Regards
Mario

[adrian]

Hi,

It's unlikely for the validation to take 3 minutes, if all resources are local.
Check for imports/includes within the XML and XSD that refer remote schemas (or other resources).

To debug remote references that are unresolved, go to Options > Preferences, XML > XML Catalog and set Verbosity to Unresolved entities. When you validate, you will get in the Catalogs view the list of URIs and SystemIDs that are not resolved.

Regards,
Adrian

[mariomueller]

Hi Adrian,

I did what you told without any improvement. Is it possible to upload the XSD and the XML so you could do a check?

Regards
Mario

[adrian]

Hi,

Sure, you can send them to support@oxygenxml.com or upload them via our Technical Support form, select Other and fill email, subject and description. File attachment is at the bottom of the form.

Regards,
Adrian

[mariomueller]

Hi Adrian,

I used the "technical contact" form and submitted already.

Regards Mario

[mariomueller]

Hi adrian,

many thanks for the good work. I changed from 99999 to unbounded. But the error check still takes a lot of time (> 2 minutes).
How many minutes/seconds did your error check last?

Thanks
Regards
Mario

[adrian]

Hi,

I'm afraid that still doesn't resolve the long validation time. It's about 2 minutes with Xerces, or 2 minutes and 45 seconds with Saxon-EE.
I'm still looking into possible causes.

Regards,
Adrian

[mariomueller]

Hi Adrian,

thanks for the very good and quick support. If you find reasons to speed up the performance, please let me know.

Regards
Mario

[adrian]

Hi,

We have tested some more and it only worked well after replacing all maxOccurs="99", maxOccurs="99999" and maxOccurs="999999" with maxOccurs="unbounded".
So, it seems even relatively low values like 99 (maxOccurs="99") trigger the performance issue in both Xerces and Saxon-EE.

Regards,
Adrian

[mariomueller]

Hi Adrian,

it worked! Thanks a lot, we bought a permanent key

Regards Mario