You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a XSD file is saved, it loop for all opened document and for each XML document, it checks if the saved XSD file bind the the current XML file. To do that DOMDocument#useSchemas is called. This method must be improved
Windows OS problem
When XSD file is saved on Windows OS, it should revalidate all bound XML files, but it didn't do that.
After debugging, I have this error:
java.nio.file.InvalidPathException: Illegal char <:> at index 2: /C:/Users/azerr/Downloads/data_gxl_minimal++_minimal++_OHNE_DOC.gxl/book.xsd
Manage only xs:schemaLocation, xs:noNamespaceSchemaLocation binding
If opened XML file is bound with a XML catalog, XML file assocotaions, DOMDocumnt#useSchemas doesn't takes care of this binding kind.
To fix both 1) and 2), the DOMDocumnt#useSchemas must be rewritten by using resolverExtensionManager#resolve.
The text was updated successfully, but these errors were encountered:
angelozerr
changed the title
Revalidate XML files when XSD files is saved doesn't work on Windows OS
Improve revalidate XML files when XSD files is saved
Jul 10, 2019
When a XSD file is saved, it loop for all opened document and for each XML document, it checks if the saved XSD file bind the the current XML file. To do that DOMDocument#useSchemas is called. This method must be improved
When XSD file is saved on Windows OS, it should revalidate all bound XML files, but it didn't do that.
After debugging, I have this error:
java.nio.file.InvalidPathException: Illegal char <:> at index 2: /C:/Users/azerr/Downloads/data_gxl_minimal++_minimal++_OHNE_DOC.gxl/book.xsd
If opened XML file is bound with a XML catalog, XML file assocotaions, DOMDocumnt#useSchemas doesn't takes care of this binding kind.
To fix both 1) and 2), the DOMDocumnt#useSchemas must be rewritten by using resolverExtensionManager#resolve.
The text was updated successfully, but these errors were encountered: