From jdo-dev-return-5763-apmail-db-jdo-dev-archive=www.apache.org@db.apache.org Wed May 30 13:10:06 2007 Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 67188 invoked from network); 30 May 2007 13:09:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 May 2007 13:09:43 -0000 Received: (qmail 52479 invoked by uid 500); 30 May 2007 13:09:42 -0000 Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jdo-dev@db.apache.org Delivered-To: mailing list jdo-dev@db.apache.org Received: (qmail 52369 invoked by uid 99); 30 May 2007 13:09:42 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 May 2007 06:09:42 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 May 2007 06:09:37 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 74287714186 for ; Wed, 30 May 2007 06:09:16 -0700 (PDT) Message-ID: <22790989.1180530556473.JavaMail.jira@brutus> Date: Wed, 30 May 2007 06:09:16 -0700 (PDT) From: "Craig Russell (JIRA)" To: jdo-dev@db.apache.org Subject: [jira] Commented: (JDO-472) Cannot use JDO 2 xsd for XML validation In-Reply-To: <30972672.1173905949754.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/JDO-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500126 ] Craig Russell commented on JDO-472: ----------------------------------- I've reviewed the patch and it looks very good. The patch doesn't remove or rename the existing 2.0 xsd files, and I agree that we should leave the 2.0 xsd files as they are, just adding the 2.1 xsd files. I agree that there is no reason to add a 2.1 version of the dtd files unless (and until) we make some changes to the contents. > 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 > Assignee: Michael Bouschen > Fix For: JDO 2 maintenance release 1 > > Attachments: JDO472-mbo-070527.patch, xsd-test.zip > > > I am trying to use the last JDO 2.0 xsd with: > SchemaFactory factory = SchemaFactory.newInstance(XMLConstants.W3C_XML_SCHEMA_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 against this 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:attlist.jdo'. It was detected that 'xs:attlist.jdo' is in namespace 'http://www.w3.org/2001/XMLSchema', but components from this namespace are not referenceable from schema document 'file:/D:/odb/dv/rt/class/jdo.xsd'. If this is the incorrect namespace, perhaps the prefix of 'xs:attlist.jdo' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/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 successfully already? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.