03-15-07 12:11 AM
[ https://issues.apache.org/jira/brow...action_12480964 ]
Ilan Kirsh commented on JDO-472:
--------------------------------
Unfortunately I am getting the same problems now with DocumentBuilder. I tri
ed also the 3 previous versions of the xsd - and the result is the same. I a
m using JDK 1.5.0_09.
e.g.
org.xml.sax.SAXParseException: cos-nonambig: "http://java.sun.com/xml/ns/jdo
/jdo":extension and "http://java.sun.com/xml/ns/jdo/jdo":extension (or eleme
nts from their substitution group) violate "Unique Particle Attribution". Du
ring validation against thi
s schema, ambiguity would be created for those two particles.
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXPars
eException(ErrorHandlerWrapper.java:236)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHa
ndlerWrapper.java:172)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLE
rrorReporter.java:382)
at com.sun.org.apache.xerces.internal.impl.xs.XSConstraints.reportSchemaErro
r(XSConstraints.java:315)
at com.sun.org.apache.xerces.internal.impl.xs.XSConstraints.fullSchemaChecki
ng(XSConstraints.java:463)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleEndEl
ement(XMLSchemaValidator.java:2246)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.endElement(
XMLSchemaValidator.java:814)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndE
lement(XMLNSDocumentScannerImpl.java:719)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$Fr
agmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1685)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.sc
anDocument(XMLDocumentFragmentScannerImp
l.java:368)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11
Configuration.java:834)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11
Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java
:148)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java
:250)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Documen
tBuilderImpl.java:292)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:98)
> Cannot use JDO 2 xsd for XML validation
> ---------------------------------------
>
> Key: JDO-472
> URL: https://issues.apache.org/jira/browse/JDO-472
> Project: JDO
> Issue Type: Bug
> Affects Versions: JDO 2 final
> Reporter: Ilan Kirsh
> Fix For: JDO 2 final
>
>
> I am trying to use the last JDO 2.0 xsd with:
> SchemaFactory factory = SchemaFactory.newInstance(XMLConstants.W3C_XML_SCH
EMA_NS_URI);
> URL xsdURL = getClass().getResource("/jdo_2.0.xsd");
> Schema schema = factory.newSchema(xsdURL);
> First I got the following exception (from newSchema):
> org.xml.sax.SAXParseException: cos-nonambig: "http://java.sun.com/xml/ns/jdo/jdo":
extension and "http://java.sun.com/xml/ns/jdo/jdo":extension (or elements from their
substitution group) violate "Unique Particle Attribution". During validation agains
t t
his schema, ambiguity would be created for those two particles.
> And after trying to fix it, I got the following exception (from newSchema)
:
> org.xml.sax.SAXParseException: src-resolve.4.2: Error resolving component 'xs:attl
ist.jdo'. It was detected that 'xs:attlist.jdo' is in namespace 'http://www.w3.org/2
001/XMLSchema', but components from this namespace are not referenceable from schema
do
cument 'file:/D:/odb/dv/rt/class/jdo.xsd'. If this is the incorrect namespac
e, perhaps the prefix of 'xs:attlist.jdo' needs to be changed. If this is th
e correct namespace, then an appropriate 'import' tag should be added to 'fi
le:/D:/odb/dv/rt/class/jdo.
xsd'.
> The same 3 lines work well with JPA 1.0 xsd. Has anyone used JDO 2.0 xsd successfu
lly already?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ Post a follow-up to this message ]
|