Feedback
Did this article resolve your question/issue?

   

Article

Error 9082 when specify XML schema location with SCHEMA-PATH

Information

 
TitleError 9082 when specify XML schema location with SCHEMA-PATH
URL NameError-9082-when-specify-XML-schema-location-with-SCHEMA-PATH
Article Number000112619
EnvironmentProduct: OpenEdge
Version: 11.6, 11.7
OS: Windows
Question/Problem Description
Error 9082 when specify XML schema location with SCHEMA-PATH

Using the X-DOCUMENT SCHEMA-PATH attribute to locate an external DTD file defined within an XML file.  Even though the SCHEMA-PATH attribute is correct and the path in the XML document to the .xsd file is correct, the LOAD method raises error 9082.  For example the code is:
 
DEFINE VARIABLE hDocument AS HANDLE NO-UNDO.

CREATE X-DOCUMENT hDocument.
hDocument:SCHEMA-PATH = "c:\Temp":U.

MESSAGE hDocument:LOAD("FILE":U, "C:\Temp\hotfix.xml":U, TRUE)
    VIEW-AS ALERT-BOX.

The XML file contains:

<?xml version="1.0" encoding="UTF-8"?>
<plugin fileModTime="2018-09-20T17:00:44" fileName="Test-Application-Import.pl" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="c:\temp\plugin.xsd">

The plugin.xsd file resides in the 'c:\temp' folder and is a valid .xsd file.  So why is the error 9082 displayed?
Steps to Reproduce
Clarifying Information
Error MessageX-NODEREF or X-DOCUMENT LOAD got an error: 'no declaration found for element 'plugin''. (9082)
Defect/Enhancement Number
Cause
This is expected behavior.  The SCHEMA-PATH attribute is only searched for if the XML reference to the external DTD is a relative reference (i.e not absolute as in this case 'c:\temp\plugin.xsd').

The documentation entry for the SCHEMA-PATH attribute states:

"A delimiter-separated list of directory paths used to locate the XML Document Type Definition (DTD) associated with a particular XML document. It is searched if the XML document contains a relative path to the DTD."

The searching rules are:
  • if the XML file references an external DTD in the form of an absolute path reference, then it is never searched for. 
  • if the XML file references an external DTD in the form of a relative path reference, then it is searched for only if the SCHEMA-PATH attribute is set. 
Resolution
Set the SCHEMA-PATH attribute and change the XML file .xsd file reference from an absolute path reference, to a relative path reference.  For example:

xsi:noNamespaceSchemaLocation="c:\temp\plugin.xsd"
to:
xsi:noNamespaceSchemaLocation="plugin.xsd"

Alternatively, run in an unsecure configuration by switching off strict entity resolution.  See article X-DOCUMENT susceptible to XML external entity processing vulnerability
Workaround
Notes
Progress Article(s):
 XML validation against external XSD fails starting with OpenEdge 11.6
 X-DOCUMENT susceptible to XML external entity processing vulnerability

References to Other Documentation:
OpenEdge Development: ABL Reference, "SCHEMA-PATH attribute"
Last Modified Date11/20/2020 7:04 AM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.