- This topic has 3 replies, 2 voices, and was last updated 19 years ago by
.
-
Posts
-
Schema location given in XML Schema <import> overides XML Cataloge Setting in MyEclipse.
– should be other way round.
– We define custom URL scheme ‘jcp’ which resolves by looking in Java classpath at runtime.
Our xsds use this and give Validation errors in MyEclipse, even if we have added XML Catlaogue entry for the xsd.e.g. sample xsd intro that exhibits this problem (see use of jcp: URI in <import> element) :
<?xml version=”1.0″ encoding=”UTF-8″?>
<schema xmlns=”http://www.w3.org/2001/XMLSchema”
xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”
xmlns:fixexample=”http://xml.foo.com/ns/examples/fixconverter/1.0″
xmlns:tiaf=”http://xml.foo.com/ns/java/bar/2.0″
targetNamespace=”http://xml.foo.com/ns/examples/fixconverter/1.0″
attributeFormDefault=”unqualified”
elementFormDefault=”qualified”
>
<import schemaLocation=”jcp:xsd/java_bar_2.0.xsd” namespace=”http://xml.foo.com/ns/java/bar/2.0″/>Bernard,
To clarify, your complaint is that your <import> statement is overriding any XML Catalog settings, and you feel it should be the other way around?
