XML parser I/O error disappears if mentioned file is open in OxygenXML
Posted: Fri Mar 20, 2026 3:58 pm
Hi folks,
I am working with a set of XSLT routines to migrate content from a previous environment. Everything is local, I am using OxygenXML Developer 28.0, build 2026020208.
The routines involve lookups in many (100+) other XML files to pull in content based on IDs, most of them have a DOCTYPE entry and I configured my Oxygen project to use catalog files which resolve the public identifiers to actual DTD files. When I open any of those files, the validation is successful.
I access the files like this:
For exactly this element, the XML parser reports:
I/O error reported by XML parser processing file:/C:/Users/path/input/reuse-rgd/_config/bg/instr.xml: Cannot resolve URI supplied for entity resolution
BUT: If I have this exact file open in OxygenXML, there is no error!
I am baffled and assume that I hit certain limitations regarding calls to files. Can I change certain settings to avoid this effect or shall I change the processing?
I would greatly appreciate any tips.
Best regards,
Michael
I am working with a set of XSLT routines to migrate content from a previous environment. Everything is local, I am using OxygenXML Developer 28.0, build 2026020208.
The routines involve lookups in many (100+) other XML files to pull in content based on IDs, most of them have a DOCTYPE entry and I configured my Oxygen project to use catalog files which resolve the public identifiers to actual DTD files. When I open any of those files, the validation is successful.
I access the files like this:
Code: Select all
<xsl:variable name="instr" select="doc('../../input/reuse-rgd/_config/' || $srcLang || '/instr.xml')/cfg/group/instr-group[@id eq $instrId]" as="element(instr-group)"/>I/O error reported by XML parser processing file:/C:/Users/path/input/reuse-rgd/_config/bg/instr.xml: Cannot resolve URI supplied for entity resolution
BUT: If I have this exact file open in OxygenXML, there is no error!
I am baffled and assume that I hit certain limitations regarding calls to files. Can I change certain settings to avoid this effect or shall I change the processing?
I would greatly appreciate any tips.
Best regards,
Michael