From jenny79@example.org Tue Nov 02 12:32:25 2010 Return-Path: <jenny79@example.org> Delivered-To: jenny79@example.org Received: (qmail 71533 invoked from network); 2 Nov 2010 12:32:25 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 2 Nov 2010 12:32:25 -0000 Received: (qmail 63993 invoked by uid 500); 2 Nov 2010 12:32:56 -0000 Delivered-To: jenny79@example.org Received: (qmail 63860 invoked by uid 500); 2 Nov 2010 12:32:53 -0000 Mailing-List: contact jenny79@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenny79@example.org> List-Unsubscribe: <mailto:jenny79@example.org> List-Post: <mailto:jenny79@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: jenny79@example.org Delivered-To: mailing list jenny79@example.org Received: (qmail 63840 invoked by uid 99); 2 Nov 2010 12:32:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Nov 2010 12:32:51 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO thor.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Nov 2010 12:32:49 +0000 Received: from thor (localhost [83.161.120.155]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oA2CWRqj007325 for <jenny79@example.org>; Tue, 2 Nov 2010 12:32:28 GMT Message-ID: <25312082.193311288701147830.JavaMail.jira@thor> Date: Tue, 2 Nov 2010 08:32:27 -0400 (EDT) From: "Mukul Gandhi (JIRA)" <jenny79@example.org> To: jenny79@example.org Subject: [jira] Created: (XERCESJ-1470) enhancements to XML Schema 1.1 assertions run-time error messages MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org enhancements to XML Schema 1.1 assertions run-time error messages ----------------------------------------------------------------- Key: XERCESJ-1470 URL: https://issues.apache.org/jira/browse/XERCESJ-1470 Project: Xerces2-J Issue Type: Improvement Components: XML Schema 1.1 Datatypes, XML Schema 1.1 Structures Affects Versions: 2.10.0 Reporter: Mukul Gandhi Assignee: Mukul Gandhi Priority: Trivial Fix For: 2.11.0 I committed sometime ago little enhancement to Xerces specific error messages during XML Schema 1.1 assertions evaluation failure (thought it would be ok to create a JIRA issue for this). Here are the summary of these changes (explained with a small example). instance document [1]: <x>101</x> XML Schema 1.1 simpleType definition [2]: <xs:simpleType> <xs:restriction base="xs:integer" xmlns:xerces="http://xerces.apache.org"> <xs:assertion test="$value mod 2 = 0" xerces:message="The value must be divisible by 2. {$value} is not divisible by 2." /> </xs:restriction> </xs:simpleType> When the instance document [1] is validated by the simpleType [2] Xerces would now display an error message like following: "The value must be divisible by 2. 101 is not divisible by 2." At run-time the placeholder (a kind of little macro) {$value} will be replaced by corresponding value from instance document. The placeholder for this purpose must have a name {$value}. There can be multiple instances of these placeholders in single assertions message, and all-of them will be replaced by the value from instance document. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: jenny79@example.org For additional commands, e-mail: jenny79@example.org From jenny79@example.org Tue Nov 02 12:34:42 2010 Return-Path: <jenny79@example.org> Delivered-To: jenny79@example.org Received: (qmail 72528 invoked from network); 2 Nov 2010 12:34:41 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 2 Nov 2010 12:34:41 -0000 Received: (qmail 66843 invoked by uid 500); 2 Nov 2010 12:35:12 -0000 Delivered-To: jenny79@example.org Received: (qmail 65069 invoked by uid 500); 2 Nov 2010 12:35:10 -0000 Mailing-List: contact jenny79@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenny79@example.org> List-Unsubscribe: <mailto:jenny79@example.org> List-Post: <mailto:jenny79@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: jenny79@example.org Delivered-To: mailing list jenny79@example.org Received: (qmail 65062 invoked by uid 99); 2 Nov 2010 12:35:10 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Nov 2010 12:35:10 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO thor.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Nov 2010 12:35:09 +0000 Received: from thor (localhost [83.161.120.155]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oA2CYns0007356 for <jenny79@example.org>; Tue, 2 Nov 2010 12:34:49 GMT Message-ID: <2520589.193321288701289465.JavaMail.jira@thor> Date: Tue, 2 Nov 2010 08:34:49 -0400 (EDT) From: "Mukul Gandhi (JIRA)" <jenny79@example.org> To: jenny79@example.org Subject: [jira] Resolved: (XERCESJ-1470) enhancements to XML Schema 1.1 assertions run-time error messages In-Reply-To: <25312082.193311288701147830.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/XERCESJ-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Gandhi resolved XERCESJ-1470. ----------------------------------- Resolution: Fixed marking this issue as fixed. > enhancements to XML Schema 1.1 assertions run-time error messages > ----------------------------------------------------------------- > > Key: XERCESJ-1470 > URL: https://issues.apache.org/jira/browse/XERCESJ-1470 > Project: Xerces2-J > Issue Type: Improvement > Components: XML Schema 1.1 Datatypes, XML Schema 1.1 Structures > Affects Versions: 2.10.0 > Reporter: Mukul Gandhi > Assignee: Mukul Gandhi > Priority: Trivial > Fix For: 2.11.0 > > > I committed sometime ago little enhancement to Xerces specific error messages during XML Schema 1.1 assertions evaluation failure (thought it would be ok to create a JIRA issue for this). Here are the summary of these changes (explained with a small example). > instance document [1]: > <x>101</x> > XML Schema 1.1 simpleType definition [2]: > <xs:simpleType> > <xs:restriction base="xs:integer" xmlns:xerces="http://xerces.apache.org"> > <xs:assertion test="$value mod 2 = 0" xerces:message="The value must be divisible by 2. {$value} is not divisible by 2." /> > </xs:restriction> > </xs:simpleType> > When the instance document [1] is validated by the simpleType [2] Xerces would now display an error message like following: > "The value must be divisible by 2. 101 is not divisible by 2." > At run-time the placeholder (a kind of little macro) {$value} will be replaced by corresponding value from instance document. The placeholder for this purpose must have a name {$value}. There can be multiple instances of these placeholders in single assertions message, and all-of them will be replaced by the value from instance document. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: jenny79@example.org For additional commands, e-mail: jenny79@example.org From jenny79@example.org Fri Nov 05 19:04:42 2010 Return-Path: <jenny79@example.org> Delivered-To: jenny79@example.org Received: (qmail 28035 invoked from network); 5 Nov 2010 19:04:42 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 5 Nov 2010 19:04:42 -0000 Received: (qmail 90260 invoked by uid 500); 5 Nov 2010 19:05:13 -0000 Delivered-To: jenny79@example.org Received: (qmail 90208 invoked by uid 500); 5 Nov 2010 19:05:12 -0000 Mailing-List: contact jenny79@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenny79@example.org> List-Unsubscribe: <mailto:jenny79@example.org> List-Post: <mailto:jenny79@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: jenny79@example.org Delivered-To: mailing list jenny79@example.org Received: (qmail 90201 invoked by uid 99); 5 Nov 2010 19:05:12 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Nov 2010 19:05:12 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO thor.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Nov 2010 19:05:09 +0000 Received: from thor (localhost [83.161.120.155]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oA5J4lqs011037 for <jenny79@example.org>; Fri, 5 Nov 2010 19:04:48 GMT Message-ID: <7862993.41061288983887796.JavaMail.jira@thor> Date: Fri, 5 Nov 2010 15:04:47 -0400 (EDT) From: "Sandy Gao (JIRA)" <jenny79@example.org> To: jenny79@example.org Subject: [jira] Updated: (XERCESJ-1427) Check subsumption relationship of complex type particles In-Reply-To: <jenny79@example.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/XERCESJ-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Gao updated XERCESJ-1427: ------------------------------- Affects Version/s: (was: 2.9.1) 2.10.0 Summary: Check subsumption relationship of complex type particles (was: [GSoC]: Check subsumption relationship of complex type particles ) > Check subsumption relationship of complex type particles > --------------------------------------------------------- > > Key: XERCESJ-1427 > URL: https://issues.apache.org/jira/browse/XERCESJ-1427 > Project: Xerces2-J > Issue Type: New Feature > Components: XML Schema 1.1 Structures > Affects Versions: 2.10.0 > Reporter: Michael Glavassevich > > In XML Schema 1.1 [1], the sequences of sub-elements allowed by a complex type is determined by its content model, a particle [2]. When one complex type restricts a base type, its particle is required to accept less [3] than that of the base type. When <all> model groups [4] are used in the restriction type (while the base type may also have an <all> group or have a combination of <sequence>s and <choice>s), the "accept less" requirement becomes an interesting task. The student is expected to study this problem, research existing solutions to similar issues (e.g. those listed here [5]), and propose and implement a solution. This work also helps to address the Priority Feedback [6] in the specification regarding the usefulness and implementation difficulty of this feature. > Possible Mentors: Sandy Gao > [1] http://www.w3.org/TR/xmlschema11-1/ > [2] http://www.w3.org/TR/xmlschema11-1/#cParticles > [3] http://www.w3.org/TR/xmlschema11-1/#cos-content-act-restrict > [4] http://www.w3.org/TR/xmlschema11-1/#Model_Groups > [5] http://www.w3.org/TR/xmlschema11-1/#subsumptionCheckP > [6] http://www.w3.org/TR/xmlschema11-1/#derivation-ok-restriction -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: jenny79@example.org For additional commands, e-mail: jenny79@example.org From jenny79@example.org Fri Nov 05 19:04:42 2010 Return-Path: <jenny79@example.org> Delivered-To: jenny79@example.org Received: (qmail 28045 invoked from network); 5 Nov 2010 19:04:42 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 5 Nov 2010 19:04:42 -0000 Received: (qmail 90286 invoked by uid 500); 5 Nov 2010 19:05:13 -0000 Delivered-To: jenny79@example.org Received: (qmail 90218 invoked by uid 500); 5 Nov 2010 19:05:13 -0000 Mailing-List: contact jenny79@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenny79@example.org> List-Unsubscribe: <mailto:jenny79@example.org> List-Post: <mailto:jenny79@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: jenny79@example.org Delivered-To: mailing list jenny79@example.org Received: (qmail 90209 invoked by uid 99); 5 Nov 2010 19:05:12 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Nov 2010 19:05:12 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO thor.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Nov 2010 19:05:10 +0000 Received: from thor (localhost [83.161.120.155]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oA5J4nvN011043 for <jenny79@example.org>; Fri, 5 Nov 2010 19:04:49 GMT Message-ID: <29658018.41081288983888993.JavaMail.jira@thor> Date: Fri, 5 Nov 2010 15:04:48 -0400 (EDT) From: "Sandy Gao (JIRA)" <jenny79@example.org> To: jenny79@example.org Subject: [jira] Assigned: (XERCESJ-1427) Check subsumption relationship of complex type particles In-Reply-To: <jenny79@example.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/XERCESJ-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Gao reassigned XERCESJ-1427: ---------------------------------- Assignee: Sandy Gao > Check subsumption relationship of complex type particles > --------------------------------------------------------- > > Key: XERCESJ-1427 > URL: https://issues.apache.org/jira/browse/XERCESJ-1427 > Project: Xerces2-J > Issue Type: New Feature > Components: XML Schema 1.1 Structures > Affects Versions: 2.10.0 > Reporter: Michael Glavassevich > Assignee: Sandy Gao > > In XML Schema 1.1 [1], the sequences of sub-elements allowed by a complex type is determined by its content model, a particle [2]. When one complex type restricts a base type, its particle is required to accept less [3] than that of the base type. When <all> model groups [4] are used in the restriction type (while the base type may also have an <all> group or have a combination of <sequence>s and <choice>s), the "accept less" requirement becomes an interesting task. The student is expected to study this problem, research existing solutions to similar issues (e.g. those listed here [5]), and propose and implement a solution. This work also helps to address the Priority Feedback [6] in the specification regarding the usefulness and implementation difficulty of this feature. > Possible Mentors: Sandy Gao > [1] http://www.w3.org/TR/xmlschema11-1/ > [2] http://www.w3.org/TR/xmlschema11-1/#cParticles > [3] http://www.w3.org/TR/xmlschema11-1/#cos-content-act-restrict > [4] http://www.w3.org/TR/xmlschema11-1/#Model_Groups > [5] http://www.w3.org/TR/xmlschema11-1/#subsumptionCheckP > [6] http://www.w3.org/TR/xmlschema11-1/#derivation-ok-restriction -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: jenny79@example.org For additional commands, e-mail: jenny79@example.org From jenny79@example.org Fri Nov 05 19:08:34 2010 Return-Path: <jenny79@example.org> Delivered-To: jenny79@example.org Received: (qmail 37392 invoked from network); 5 Nov 2010 19:08:34 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 5 Nov 2010 19:08:34 -0000 Received: (qmail 97419 invoked by uid 500); 5 Nov 2010 19:09:05 -0000 Delivered-To: jenny79@example.org Received: (qmail 97390 invoked by uid 500); 5 Nov 2010 19:09:05 -0000 Mailing-List: contact jenny79@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenny79@example.org> List-Unsubscribe: <mailto:jenny79@example.org> List-Post: <mailto:jenny79@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: jenny79@example.org Delivered-To: mailing list jenny79@example.org Received: (qmail 97383 invoked by uid 99); 5 Nov 2010 19:09:05 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Nov 2010 19:09:05 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO thor.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Nov 2010 19:09:05 +0000 Received: from thor (localhost [83.161.120.155]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oA5J8iP8011082 for <jenny79@example.org>; Fri, 5 Nov 2010 19:08:45 GMT Message-ID: <3122003.41161288984124679.JavaMail.jira@thor> Date: Fri, 5 Nov 2010 15:08:44 -0400 (EDT) From: "Sandy Gao (JIRA)" <jenny79@example.org> To: jenny79@example.org Subject: [jira] Resolved: (XERCESJ-1427) Check subsumption relationship of complex type particles In-Reply-To: <jenny79@example.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/XERCESJ-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Gao resolved XERCESJ-1427. -------------------------------- Resolution: Fixed Just committed support of the new content type restriction rules. The implementation treat both the base content model and the derived as DFAs and match corresponding states in the 2 content models. This is not very efficient if the derived content model is an "all" model group. Some optimization is included for all-all derivation, by attempting to simplify the content models before falling back to the DFA approach. > Check subsumption relationship of complex type particles > --------------------------------------------------------- > > Key: XERCESJ-1427 > URL: https://issues.apache.org/jira/browse/XERCESJ-1427 > Project: Xerces2-J > Issue Type: New Feature > Components: XML Schema 1.1 Structures > Affects Versions: 2.10.0 > Reporter: Michael Glavassevich > Assignee: Sandy Gao > > In XML Schema 1.1 [1], the sequences of sub-elements allowed by a complex type is determined by its content model, a particle [2]. When one complex type restricts a base type, its particle is required to accept less [3] than that of the base type. When <all> model groups [4] are used in the restriction type (while the base type may also have an <all> group or have a combination of <sequence>s and <choice>s), the "accept less" requirement becomes an interesting task. The student is expected to study this problem, research existing solutions to similar issues (e.g. those listed here [5]), and propose and implement a solution. This work also helps to address the Priority Feedback [6] in the specification regarding the usefulness and implementation difficulty of this feature. > Possible Mentors: Sandy Gao > [1] http://www.w3.org/TR/xmlschema11-1/ > [2] http://www.w3.org/TR/xmlschema11-1/#cParticles > [3] http://www.w3.org/TR/xmlschema11-1/#cos-content-act-restrict > [4] http://www.w3.org/TR/xmlschema11-1/#Model_Groups > [5] http://www.w3.org/TR/xmlschema11-1/#subsumptionCheckP > [6] http://www.w3.org/TR/xmlschema11-1/#derivation-ok-restriction -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: jenny79@example.org For additional commands, e-mail: jenny79@example.org From jenny79@example.org Sat Nov 06 00:26:33 2010 Return-Path: <jenny79@example.org> Delivered-To: jenny79@example.org Received: (qmail 8492 invoked from network); 6 Nov 2010 00:26:33 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 6 Nov 2010 00:26:33 -0000 Received: (qmail 48914 invoked by uid 500); 6 Nov 2010 00:27:04 -0000 Delivered-To: jenny79@example.org Received: (qmail 48863 invoked by uid 500); 6 Nov 2010 00:27:04 -0000 Mailing-List: contact jenny79@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenny79@example.org> List-Unsubscribe: <mailto:jenny79@example.org> List-Post: <mailto:jenny79@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: jenny79@example.org Delivered-To: mailing list jenny79@example.org Received: (qmail 48856 invoked by uid 99); 6 Nov 2010 00:27:04 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 Nov 2010 00:27:04 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO thor.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 Nov 2010 00:27:03 +0000 Received: from thor (localhost [83.161.120.155]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oA60Qgnp014633 for <jenny79@example.org>; Sat, 6 Nov 2010 00:26:42 GMT Message-ID: <32643534.48001289003202561.JavaMail.jira@thor> Date: Fri, 5 Nov 2010 20:26:42 -0400 (EDT) From: "Chris DeForeest (JIRA)" <jenny79@example.org> To: jenny79@example.org Subject: [jira] Created: (XERCESJ-1471) ArrayIndexOutOfBoundsException in XSLTC when using TransformHandler and a URIResolver MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 ArrayIndexOutOfBoundsException in XSLTC when using TransformHandler and a URIResolver ------------------------------------------------------------------------------------- Key: XERCESJ-1471 URL: https://issues.apache.org/jira/browse/XERCESJ-1471 Project: Xerces2-J Issue Type: Bug Affects Versions: 2.7.1 Environment: Windows XP; Java 1.6_u19; Xalan 2.7.1. Reporter: Chris DeForeest I receive the following ArrayIndexOutOfBoundsException when using the XSLTC transformer: Exception in thread "main" javax.xml.transform.TransformerException: java.lang.ArrayIndexOutOfBoundsException: -jenny79@example.org(TransformerHandlerImpl.java:243) at org.apache.xerces.parsers.AbstractSAXParser.endDocument(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl.endEntity(Unknown Source) at org.apache.xerces.impl.XMLEntityManager.endEntity(Unknown Source) at org.apache.xerces.impl.XMLEntityScanner.load(Unknown Source) at org.apache.xerces.impl.XMLEntityScanner.skipSpaces(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl$TrailingMiscDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at XalanBug.main(XalanBug.java:36) Caused by: javax.xml.transform.TransformerException: java.lang.ArrayIndexOutOfBoundsException: -jenny79@example.org(TransformerImpl.java:639) at org.apache.xalan.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:303) at org.apache.xalan.xsltc.trax.TransformerHandlerImpl.endDocument(TransformerHandlerImpl.java:240) ... 13 more Caused by: java.lang.ArrayIndexOutOfBoundsException: -jenny79@example.org(DOMAdapter.java:233) at org.apache.xalan.xsltc.dom.MultiDOM.getExpandedTypeID(MultiDOM.java:434) at GregorSamsa.applyTemplates() at GregorSamsa.template$dot$1() at GregorSamsa.applyTemplates() at GregorSamsa.applyTemplates() at GregorSamsa.transform() at org.apache.xalan.xsltc.runtime.AbstractTranslet.transform(AbstractTranslet.java:605) at org.apache.xalan.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:632) ... 15 more The problem is somehow related to the combination of TransformHandler, URIResolver and the document() function. It works with XSLTC if I don't supply my own URIResolver. It also works with XSLTC if I use the Transformer.transform() method instead of a TransformHandler. It always works when using the Xalan interpreter (instead of XSLTC). I will attach a condensed example that reproduces the problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: jenny79@example.org For additional commands, e-mail: jenny79@example.org From jenny79@example.org Sat Nov 06 00:28:31 2010 Return-Path: <jenny79@example.org> Delivered-To: jenny79@example.org Received: (qmail 8663 invoked from network); 6 Nov 2010 00:28:30 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 6 Nov 2010 00:28:30 -0000 Received: (qmail 49913 invoked by uid 500); 6 Nov 2010 00:29:02 -0000 Delivered-To: jenny79@example.org Received: (qmail 49777 invoked by uid 500); 6 Nov 2010 00:29:02 -0000 Mailing-List: contact jenny79@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenny79@example.org> List-Unsubscribe: <mailto:jenny79@example.org> List-Post: <mailto:jenny79@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: jenny79@example.org Delivered-To: mailing list jenny79@example.org Received: (qmail 49770 invoked by uid 99); 6 Nov 2010 00:29:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 Nov 2010 00:29:02 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO thor.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 Nov 2010 00:29:01 +0000 Received: from thor (localhost [83.161.120.155]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oA60Sfo9014638 for <jenny79@example.org>; Sat, 6 Nov 2010 00:28:41 GMT Message-ID: <22601813.48011289003321344.JavaMail.jira@thor> Date: Fri, 5 Nov 2010 20:28:41 -0400 (EDT) From: "Chris DeForeest (JIRA)" <jenny79@example.org> To: jenny79@example.org Subject: [jira] Updated: (XERCESJ-1471) ArrayIndexOutOfBoundsException in XSLTC when using TransformHandler and a URIResolver In-Reply-To: <32643534.48001289003202561.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/XERCESJ-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris DeForeest updated XERCESJ-1471: ------------------------------------- Attachment: xalan-bug.zip Simple Java program that reproduces the problem > ArrayIndexOutOfBoundsException in XSLTC when using TransformHandler and a URIResolver > ------------------------------------------------------------------------------------- > > Key: XERCESJ-1471 > URL: https://issues.apache.org/jira/browse/XERCESJ-1471 > Project: Xerces2-J > Issue Type: Bug > Affects Versions: 2.7.1 > Environment: Windows XP; Java 1.6_u19; Xalan 2.7.1. > Reporter: Chris DeForeest > Attachments: xalan-bug.zip > > > I receive the following ArrayIndexOutOfBoundsException when using the XSLTC transformer: > Exception in thread "main" javax.xml.transform.TransformerException: java.lang.ArrayIndexOutOfBoundsException: -1 > at org.apache.xalan.xsltc.trax.TransformerHandlerImpl.endDocument(TransformerHandlerImpl.java:243) > at org.apache.xerces.parsers.AbstractSAXParser.endDocument(Unknown Source) > at org.apache.xerces.impl.XMLDocumentScannerImpl.endEntity(Unknown Source) > at org.apache.xerces.impl.XMLEntityManager.endEntity(Unknown Source) > at org.apache.xerces.impl.XMLEntityScanner.load(Unknown Source) > at org.apache.xerces.impl.XMLEntityScanner.skipSpaces(Unknown Source) > at org.apache.xerces.impl.XMLDocumentScannerImpl$TrailingMiscDispatcher.dispatch(Unknown Source) > at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) > at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) > at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) > at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) > at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) > at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) > at XalanBug.main(XalanBug.java:36) > Caused by: javax.xml.transform.TransformerException: java.lang.ArrayIndexOutOfBoundsException: -1 > at org.apache.xalan.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:639) > at org.apache.xalan.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:303) > at org.apache.xalan.xsltc.trax.TransformerHandlerImpl.endDocument(TransformerHandlerImpl.java:240) > ... 13 more > Caused by: java.lang.ArrayIndexOutOfBoundsException: -1 > at org.apache.xalan.xsltc.dom.DOMAdapter.getExpandedTypeID(DOMAdapter.java:233) > at org.apache.xalan.xsltc.dom.MultiDOM.getExpandedTypeID(MultiDOM.java:434) > at GregorSamsa.applyTemplates() > at GregorSamsa.template$dot$1() > at GregorSamsa.applyTemplates() > at GregorSamsa.applyTemplates() > at GregorSamsa.transform() > at org.apache.xalan.xsltc.runtime.AbstractTranslet.transform(AbstractTranslet.java:605) > at org.apache.xalan.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:632) > ... 15 more > The problem is somehow related to the combination of TransformHandler, URIResolver and the document() function. It works with XSLTC if I don't supply my own URIResolver. It also works with XSLTC if I use the Transformer.transform() method instead of a TransformHandler. It always works when using the Xalan interpreter (instead of XSLTC). I will attach a condensed example that reproduces the problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: jenny79@example.org For additional commands, e-mail: jenny79@example.org From jenny79@example.org Sat Nov 06 07:36:34 2010 Return-Path: <jenny79@example.org> Delivered-To: jenny79@example.org Received: (qmail 47475 invoked from network); 6 Nov 2010 07:36:34 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 6 Nov 2010 07:36:34 -0000 Received: (qmail 37076 invoked by uid 500); 6 Nov 2010 07:37:06 -0000 Delivered-To: jenny79@example.org Received: (qmail 36934 invoked by uid 500); 6 Nov 2010 07:37:03 -0000 Mailing-List: contact jenny79@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenny79@example.org> List-Unsubscribe: <mailto:jenny79@example.org> List-Post: <mailto:jenny79@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: jenny79@example.org Delivered-To: mailing list jenny79@example.org Received: (qmail 36927 invoked by uid 99); 6 Nov 2010 07:37:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 Nov 2010 07:37:02 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO thor.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 Nov 2010 07:37:02 +0000 Received: from thor (localhost [83.161.120.155]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oA67afcU018798 for <jenny79@example.org>; Sat, 6 Nov 2010 07:36:41 GMT Message-ID: <10822138.50421289029001709.JavaMail.jira@thor> Date: Sat, 6 Nov 2010 03:36:41 -0400 (EDT) From: "Mukul Gandhi (JIRA)" <jenny79@example.org> To: jenny79@example.org Subject: [jira] Created: (XERCESJ-1472) allowing xs:group as child of xs:all MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 allowing xs:group as child of xs:all ------------------------------------ Key: XERCESJ-1472 URL: https://issues.apache.org/jira/browse/XERCESJ-1472 Project: Xerces2-J Issue Type: New Feature Components: XML Schema 1.1 Structures Affects Versions: 2.10.0 Reporter: Mukul Gandhi Assignee: Mukul Gandhi Fix For: 2.11.0 The latest WD of XML Schema 1.1 spec has changed the definition of xs:all compositor as following: <all id = ID maxOccurs = 1 : 1 minOccurs = (0 | 1) : 1 {any attributes with non-schema namespace . . .}> Content: (annotation?, (element | any | group)*) </all> We now have xs:group also as child of xs:all. This was not there in the previous schema WD. I've written a patch to support this change to xs:all compositor, and would be committing it asap. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: jenny79@example.org For additional commands, e-mail: jenny79@example.org From jenny79@example.org Sat Nov 06 07:46:34 2010 Return-Path: <jenny79@example.org> Delivered-To: jenny79@example.org Received: (qmail 48547 invoked from network); 6 Nov 2010 07:46:33 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 6 Nov 2010 07:46:33 -0000 Received: (qmail 45670 invoked by uid 500); 6 Nov 2010 07:47:05 -0000 Delivered-To: jenny79@example.org Received: (qmail 45533 invoked by uid 500); 6 Nov 2010 07:47:02 -0000 Mailing-List: contact jenny79@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenny79@example.org> List-Unsubscribe: <mailto:jenny79@example.org> List-Post: <mailto:jenny79@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: jenny79@example.org Delivered-To: mailing list jenny79@example.org Received: (qmail 45521 invoked by uid 99); 6 Nov 2010 07:47:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 Nov 2010 07:47:01 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO thor.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 Nov 2010 07:47:01 +0000 Received: from thor (localhost [83.161.120.155]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oA67keXl018839 for <jenny79@example.org>; Sat, 6 Nov 2010 07:46:41 GMT Message-ID: <5974174.50431289029600796.JavaMail.jira@thor> Date: Sat, 6 Nov 2010 03:46:40 -0400 (EDT) From: "Mukul Gandhi (JIRA)" <jenny79@example.org> To: jenny79@example.org Subject: [jira] Resolved: (XERCESJ-1472) allowing xs:group as child of xs:all In-Reply-To: <10822138.50421289029001709.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/XERCESJ-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Gandhi resolved XERCESJ-1472. ----------------------------------- Resolution: Fixed I've committed the patch for this issue. I'm therefore marking this issue as fixed. > allowing xs:group as child of xs:all > ------------------------------------ > > Key: XERCESJ-1472 > URL: https://issues.apache.org/jira/browse/XERCESJ-1472 > Project: Xerces2-J > Issue Type: New Feature > Components: XML Schema 1.1 Structures > Affects Versions: 2.10.0 > Reporter: Mukul Gandhi > Assignee: Mukul Gandhi > Fix For: 2.11.0 > > > The latest WD of XML Schema 1.1 spec has changed the definition of xs:all compositor as following: > <all > id = ID > maxOccurs = 1 : 1 > minOccurs = (0 | 1) : 1 > {any attributes with non-schema namespace . . .}> > Content: (annotation?, (element | any | group)*) > </all> > We now have xs:group also as child of xs:all. This was not there in the previous schema WD. > I've written a patch to support this change to xs:all compositor, and would be committing it asap. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: jenny79@example.org For additional commands, e-mail: jenny79@example.org From jenny79@example.org Sun Nov 07 03:37:32 2010 Return-Path: <jenny79@example.org> Delivered-To: jenny79@example.org Received: (qmail 59911 invoked from network); 7 Nov 2010 03:37:27 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 7 Nov 2010 03:37:27 -0000 Received: (qmail 45699 invoked by uid 500); 7 Nov 2010 03:37:59 -0000 Delivered-To: jenny79@example.org Received: (qmail 45659 invoked by uid 500); 7 Nov 2010 03:37:56 -0000 Mailing-List: contact jenny79@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenny79@example.org> List-Unsubscribe: <mailto:jenny79@example.org> List-Post: <mailto:jenny79@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: jenny79@example.org Delivered-To: mailing list jenny79@example.org Received: (qmail 45652 invoked by uid 99); 7 Nov 2010 03:37:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 Nov 2010 03:37:55 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO minotaur.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with SMTP; Sun, 07 Nov 2010 03:37:54 +0000 Received: (qmail 58868 invoked by uid 99); 7 Nov 2010 03:37:02 -0000 Received: from localhost.apache.org (HELO mail-ww0-f45.google.com) (83.161.120.155) (smtp-auth username mukulg, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 Nov 2010 03:37:02 +0000 Received: by wwj40 with SMTP id 40so4593929wwj.14 for <jenny79@example.org>; Sat, 06 Nov 2010 20:37:32 -0700 (PDT) Received: by 83.161.120.155 with SMTP id z58mr1144776wek.33.1289101052329; Sat, 06 Nov 2010 20:37:32 -0700 (PDT) MIME-Version: 1.0 Reply-To: jenny79@example.org Received: by 83.161.120.155 with HTTP; Sat, 6 Nov 2010 20:37:12 -0700 (PDT) In-Reply-To: <3122003.41161288984124679.JavaMail.jira@thor> References: <jenny79@example.org> <3122003.41161288984124679.JavaMail.jira@thor> From: Mukul Gandhi <jenny79@example.org> Date: Sun, 7 Nov 2010 09:07:12 +0530 Message-ID: <jenny79@example.org> Subject: Re: [jira] Resolved: (XERCESJ-1427) Check subsumption relationship of complex type particles To: jenny79@example.org Content-Type: text/plain; charset=UTF-8 Hi Sandy & all, I have few questions about the fixes provided in this jira issue (i.e support of schema 1.1 rules of subsumption checks of complex type particles). Before this fix, I had following example working fine (i.e validation succeeded) in both normal schema validation mode and with Xerces full schema checking mode (i.e with -f option of sample jaxp.SourceValidator, which sets a boolean flag for this on JAXP SchemaFactory). (in this example I use the new schema 1.1 attribute "targetNamespace" on xs:element) XML document: <x xmlns="http://test1"> <y xmlns="http://test2" /> </x> XML Schema 1.1 document: <xs:schema xmlns:test1="http://test1" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://test1"> <xs:element name="x"> <xs:complexType> <xs:complexContent> <xs:restriction base="test1:TEST_TYPE"> <xs:sequence> <xs:element name="y" targetNamespace="http://test2"> <xs:complexType/> </xs:element> </xs:sequence> </xs:restriction> </xs:complexContent> </xs:complexType> </xs:element> <xs:complexType name="TEST_TYPE"> <xs:sequence> <xs:element name="y"> <xs:complexType/> </xs:element> </xs:sequence> </xs:complexType> </xs:schema> But after these fixes, the above validation succeeds without full schema checking, but not with Xerces full schema checking mode. With Xerces full schema checking mode, I get following validation errors now (i.e after these fixes): [Error] derivation-ok-restriction.5.4.2: Error for type '#AnonType_x'. The particle of the type is not a valid restriction of the particle of the base. Here are few questions please related to these new observations: 1. Is the above error message correct for the above example, wrt the schema 1.1 spec? 2. If the error message specified above conforms to XML Schema 1.1 spec, what is the right way to write a 1.1 schema for the above requirement, with Xerces full schema checking validation mode? -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: jenny79@example.org For additional commands, e-mail: jenny79@example.org From jenny79@example.org Mon Nov 08 00:53:28 2010 Return-Path: <jenny79@example.org> Delivered-To: jenny79@example.org Received: (qmail 83508 invoked from network); 8 Nov 2010 00:53:28 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 8 Nov 2010 00:53:28 -0000 Received: (qmail 55957 invoked by uid 500); 8 Nov 2010 00:53:59 -0000 Delivered-To: jenny79@example.org Received: (qmail 55903 invoked by uid 500); 8 Nov 2010 00:53:58 -0000 Mailing-List: contact jenny79@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenny79@example.org> List-Unsubscribe: <mailto:jenny79@example.org> List-Post: <mailto:jenny79@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: jenny79@example.org Delivered-To: mailing list jenny79@example.org Received: (qmail 55896 invoked by uid 99); 8 Nov 2010 00:53:58 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Nov 2010 00:53:58 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jenny79@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO e4.ny.us.ibm.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Nov 2010 00:53:49 +0000 Received: from d01relay05.pok.ibm.com (d01relay05.pok.ibm.com [83.161.120.155]) by e4.ny.us.ibm.com (8.14.4/8.13.1) with ESMTP id oA80axrY012149 for <jenny79@example.org>; Sun, 7 Nov 2010 19:36:59 -0500 Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [83.161.120.155]) by d01relay05.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id oA80rSD5162548 for <jenny79@example.org>; Sun, 7 Nov 2010 19:53:28 -0500 Received: from d01av04.pok.ibm.com (loopback [83.161.120.155]) by d01av04.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id oA80rRfO025683 for <jenny79@example.org>; Sun, 7 Nov 2010 19:53:27 -0500 Received: from d25ml03.torolab.ibm.com (d25ml03.torolab.ibm.com [83.161.120.155]) by d01av04.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id oA80rRFb025680 for <jenny79@example.org>; Sun, 7 Nov 2010 19:53:27 -0500 In-Reply-To: <jenny79@example.org> References: <jenny79@example.org> <3122003.41161288984124679.JavaMail.jira@thor> <jenny79@example.org> Subject: Re: [jira] Resolved: (XERCESJ-1427) Check subsumption relationship of complex type particles X-KeepSent: 8E0E500F:6BEBC039-852577D5:0004053F; type=4; name=$KeepSent To: jenny79@example.org X-Mailer: Lotus Notes Release 8.0.2FP1 SHF149 July 17, 2009 Message-ID: <jenny79@example.org> From: Michael Glavassevich <jenny79@example.org> Date: Sun, 7 Nov 2010 19:53:25 -0500 X-MIMETrack: Serialize by Router on D25ML03/25/M/IBM(Release 8.0.1|February 07, 2008) at 11/07/2010 19:53:27 MIME-Version: 1.0 Content-type: multipart/alternative; Boundary="0__=0ABBFD46DF9783AF8f9e8a93df938690918c0ABBFD46DF9783AF" Content-Disposition: inline --0__=0ABBFD46DF9783AF8f9e8a93df938690918c0ABBFD46DF9783AF Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: quoted-printable Hi Mukul, The content allowed by your restricted type must also be allowed by the= base type. In your example it seems like you're trying to change the namespace of element "y" to "http://test2", but that element isn't allo= wed by "TEST_TYPE" (only an element "y" with no namespace is) and so this i= sn't a valid restriction. Thanks. Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: jenny79@example.org E-mail: jenny79@example.org Mukul Gandhi <jenny79@example.org> wrote on 11/06/2010 11:37:12 PM: > Hi Sandy & all, > I have few questions about the fixes provided in this jira issue > (i.e support of schema 1.1 rules of subsumption checks of complex typ= e > particles). > > Before this fix, I had following example working fine (i.e validation= > succeeded) in both normal schema validation mode and with Xerces full= > schema checking mode (i.e with -f option of sample > jaxp.SourceValidator, which sets a boolean flag for this on JAXP > SchemaFactory). > > (in this example I use the new schema 1.1 attribute "targetNamespace"= > on xs:element) > > XML document: > <x xmlns=3D"http://test1"> > <y xmlns=3D"http://test2" /> > </x> > > XML Schema 1.1 document: > <xs:schema xmlns:test1=3D"http://test1" > xmlns:xs=3D"http://www.w3.org/2001/XMLSchema" > targetNamespace=3D"http://test1"> > > <xs:element name=3D"x"> > <xs:complexType> > <xs:complexContent> > <xs:restriction base=3D"test1:TEST_TYPE"> > <xs:sequence> > <xs:element name=3D"y" targetNamespace=3D"http://= test2"> > <xs:complexType/> > </xs:element> > </xs:sequence> > </xs:restriction> > </xs:complexContent> > </xs:complexType> > </xs:element> > > <xs:complexType name=3D"TEST_TYPE"> > <xs:sequence> > <xs:element name=3D"y"> > <xs:complexType/> > </xs:element> > </xs:sequence> > </xs:complexType> > > </xs:schema> > > But after these fixes, the above validation succeeds without full > schema checking, but not with Xerces full schema checking mode. With > Xerces full schema checking mode, I get following validation errors > now (i.e after these fixes): > > [Error] derivation-ok-restriction.5.4.2: Error for type '#AnonType_x'= . > The particle of the type is not a valid restriction of the particle > of the base. > > Here are few questions please related to these new observations: > 1. Is the above error message correct for the above example, wrt the > schema 1.1 spec? > 2. If the error message specified above conforms to XML Schema 1.1 > spec, what is the right way to write a 1.1 schema for the above > requirement, with Xerces full schema checking validation mode? > > > > > -- > Regards, > Mukul Gandhi > > ---------------------------------------------------------------------= > To unsubscribe, e-mail: jenny79@example.org > For additional commands, e-mail: jenny79@example.org= --0__=0ABBFD46DF9783AF8f9e8a93df938690918c0ABBFD46DF9783AF Content-type: text/html; charset=US-ASCII Content-Disposition: inline Content-transfer-encoding: quoted-printable <html><body> <p><tt>Hi </tt><tt>Mukul,</tt><br> <br> <tt>The content allowed by your restricted type must also be allowed by= the base type. In your example it seems like you're trying to change t= he namespace of element &quot;y&quot; to &quot;<a href=3D"http://test2"= >http://test2</a>&quot;, but that element isn't allowed by &quot;TEST_T= YPE&quot; (only an element &quot;y&quot; with no namespace is) and so t= his isn't a valid restriction.</tt><br> <br> <tt>Thanks.</tt><br> <br> <tt>Michael Glavassevich<br> XML Parser Development<br> IBM Toronto Lab<br> E-mail: jenny79@example.org</tt><br> <tt>E-mail: jenny79@example.org</tt><br> <br> <tt>Mukul Gandhi &lt;jenny79@example.org&gt; wrote on 11/06/2010 11:37:12= PM:<br> <br> &gt; Hi Sandy &amp; all,<br> &gt; &nbsp; &nbsp; I have few questions about the fixes provided in thi= s jira issue<br> &gt; (i.e support of schema 1.1 rules of subsumption checks of complex = type<br> &gt; particles).<br> &gt; <br> &gt; Before this fix, I had following example working fine (i.e validat= ion<br> &gt; succeeded) in both normal schema validation mode and with Xerces f= ull<br> &gt; schema checking mode (i.e with -f option of sample<br> &gt; jaxp.SourceValidator, which sets a boolean flag for this on JAXP<b= r> &gt; SchemaFactory).<br> &gt; <br> &gt; (in this example I use the new schema 1.1 attribute &quot;targetNa= mespace&quot;<br> &gt; on xs:element)<br> &gt; <br> &gt; XML document:<br> &gt; &lt;x xmlns=3D&quot;http://test1&quot;&gt;<br> &gt; &nbsp; &nbsp;&lt;y xmlns=3D&quot;http://test2&quot; /&gt;<br> &gt; &lt;/x&gt;<br> &gt; <br> &gt; XML Schema 1.1 document:<br> &gt; &lt;xs:schema xmlns:test1=3D&quot;http://test1&quot;<br> &gt; xmlns:xs=3D&quot;http://www.w3.org/2001/XMLSchema&quot;<br> &gt; targetNamespace=3D&quot;http://test1&quot;&gt;<br> &gt; <br> &gt; &nbsp; &nbsp; &nbsp; &lt;xs:element name=3D&quot;x&quot;&gt;<br> &gt; &nbsp; &nbsp; &nbsp; &lt;xs:complexType&gt;<br> &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&lt;xs:complexContent&gt;= <br> &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&lt;xs:restriction base=3D= &quot;test1:TEST_TYPE&quot;&gt;<br> &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb= sp; &lt;xs:sequence&gt;<br> &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb= sp; &lt;xs:element name=3D&quot;y&quot; targetNamespace=3D&quot;http://= test2&quot;&gt;<br> &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb= sp;&lt;xs:complexType/&gt;<br> &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&lt;/xs:ele= ment&gt;<br> &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&lt;/xs:seq= uence&gt;<br> &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&lt;/xs:restriction&gt;<b= r> &gt; &nbsp; &nbsp; &nbsp; &lt;/xs:complexContent&gt;<br> &gt; &nbsp; &nbsp; &nbsp; &lt;/xs:complexType&gt;<br> &gt; &nbsp; &nbsp; &nbsp; &nbsp;&lt;/xs:element&gt;<br> &gt; &nbsp; &nbsp;<br> &gt; &nbsp; &nbsp;&lt;xs:complexType name=3D&quot;TEST_TYPE&quot;&gt;<b= r> &gt; &nbsp; &nbsp; &nbsp; &nbsp;&lt;xs:sequence&gt;<br> &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&lt;xs:element name=3D&qu= ot;y&quot;&gt;<br> &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;xs:complexType/&gt;<br> &gt; &nbsp; &nbsp; &nbsp; &nbsp;&lt;/xs:element&gt;<br> &gt; &nbsp; &nbsp; &nbsp; &nbsp;&lt;/xs:sequence&gt;<br> &gt; &nbsp; &nbsp;&lt;/xs:complexType&gt;<br> &gt; <br> &gt; &lt;/xs:schema&gt;<br> &gt; <br> &gt; But after these fixes, the above validation succeeds without full<= br> &gt; schema checking, but not with Xerces full schema checking mode. Wi= th<br> &gt; Xerces full schema checking mode, I get following validation error= s<br> &gt; now (i.e after these fixes):<br> &gt; <br> &gt; [Error] derivation-ok-restriction.5.4.2: Error for type '#AnonType= _x'.<br> &gt; &nbsp;The particle of the type is not a valid restriction of the p= article<br> &gt; of the base.<br> &gt; <br> &gt; Here are few questions please related to these new observations:<b= r> &gt; 1. Is the above error message correct for the above example, wrt t= he<br> &gt; schema 1.1 spec?<br> &gt; 2. If the error message specified above conforms to XML Schema 1.1= <br> &gt; spec, what is the right way to write a 1.1 schema for the above<br= > &gt; requirement, with Xerces full schema checking validation mode?<br>= &gt; <br> &gt; <br> &gt; <br> &gt; <br> &gt; -- <br> &gt; Regards,<br> &gt; Mukul Gandhi<br> &gt; <br> &gt; ------------------------------------------------------------------= ---<br> &gt; To unsubscribe, e-mail: jenny79@example.org<br> &gt; For additional commands, e-mail: jenny79@example.org</tt>= </body></html>= --0__=0ABBFD46DF9783AF8f9e8a93df938690918c0ABBFD46DF9783AF-- From jenny79@example.org Mon Nov 08 04:47:10 2010 Return-Path: <jenny79@example.org> Delivered-To: jenny79@example.org Received: (qmail 78691 invoked from network); 8 Nov 2010 04:47:09 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 8 Nov 2010 04:47:09 -0000 Received: (qmail 91327 invoked by uid 500); 8 Nov 2010 04:47:41 -0000 Delivered-To: jenny79@example.org Received: (qmail 91195 invoked by uid 500); 8 Nov 2010 04:47:38 -0000 Mailing-List: contact jenny79@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenny79@example.org> List-Unsubscribe: <mailto:jenny79@example.org> List-Post: <mailto:jenny79@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: jenny79@example.org Delivered-To: mailing list jenny79@example.org Received: (qmail 91188 invoked by uid 99); 8 Nov 2010 04:47:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Nov 2010 04:47:37 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO minotaur.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 08 Nov 2010 04:47:35 +0000 Received: (qmail 78644 invoked by uid 99); 8 Nov 2010 04:46:42 -0000 Received: from localhost.apache.org (HELO mail-ww0-f45.google.com) (83.161.120.155) (smtp-auth username mukulg, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Nov 2010 04:46:42 +0000 Received: by wwj40 with SMTP id 40so5319777wwj.14 for <jenny79@example.org>; Sun, 07 Nov 2010 20:47:11 -0800 (PST) Received: by 83.161.120.155 with SMTP id j2mr6354527wea.33.1289191631665; Sun, 07 Nov 2010 20:47:11 -0800 (PST) MIME-Version: 1.0 Reply-To: jenny79@example.org Received: by 83.161.120.155 with HTTP; Sun, 7 Nov 2010 20:46:51 -0800 (PST) In-Reply-To: <jenny79@example.org> References: <jenny79@example.org> <3122003.41161288984124679.JavaMail.jira@thor> <jenny79@example.org> <jenny79@example.org> From: Mukul Gandhi <jenny79@example.org> Date: Mon, 8 Nov 2010 10:16:51 +0530 Message-ID: <jenny79@example.org> Subject: Re: [jira] Resolved: (XERCESJ-1427) Check subsumption relationship of complex type particles To: jenny79@example.org Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org Hi Michael, Thanks for the answers. I therefore modified definition of schema type "TEST_TYPE" in my example as follows: <xs:complexType name="TEST_TYPE"> <xs:complexContent> <xs:extension base="xs:anyType" /> </xs:complexContent> </xs:complexType> OR <xs:complexType name="TEST_TYPE"> <xs:complexContent> <xs:restriction base="xs:anyType"> <xs:sequence> <xs:any processContents="lax" /> </xs:sequence> </xs:restriction> </xs:complexContent> </xs:complexType> And both of these approaches solved the problem I mentioned earlier. Many thanks. On Mon, Nov 8, 2010 at 6:23 AM, Michael Glavassevich <jenny79@example.org> wrote: > Hi Mukul, > > The content allowed by your restricted type must also be allowed by the base > type. In your example it seems like you're trying to change the namespace of > element "y" to "http://test2", but that element isn't allowed by "TEST_TYPE" > (only an element "y" with no namespace is) and so this isn't a valid > restriction. > > Thanks. > > Michael Glavassevich > XML Parser Development > IBM Toronto Lab > E-mail: jenny79@example.org > E-mail: jenny79@example.org -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: jenny79@example.org For additional commands, e-mail: jenny79@example.org From jenny79@example.org Mon Nov 08 23:08:04 2010 Return-Path: <jenny79@example.org> Delivered-To: jenny79@example.org Received: (qmail 40450 invoked from network); 8 Nov 2010 23:08:04 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 8 Nov 2010 23:08:04 -0000 Received: (qmail 82927 invoked by uid 500); 8 Nov 2010 23:08:35 -0000 Delivered-To: jenny79@example.org Received: (qmail 82793 invoked by uid 500); 8 Nov 2010 23:08:34 -0000 Mailing-List: contact jenny79@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenny79@example.org> List-Unsubscribe: <mailto:jenny79@example.org> List-Post: <mailto:jenny79@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: jenny79@example.org Delivered-To: mailing list jenny79@example.org Received: (qmail 82786 invoked by uid 99); 8 Nov 2010 23:08:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Nov 2010 23:08:34 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO thor.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Nov 2010 23:08:33 +0000 Received: from thor (localhost [83.161.120.155]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oA8N8DjS029471 for <jenny79@example.org>; Mon, 8 Nov 2010 23:08:13 GMT Message-ID: <1924216.87581289257693313.JavaMail.jira@thor> Date: Mon, 8 Nov 2010 18:08:13 -0500 (EST) From: "Josh Spiegel (JIRA)" <jenny79@example.org> To: jenny79@example.org Subject: [jira] Created: (XERCESJ-1473) RegexParser backreference problem MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 RegexParser backreference problem --------------------------------- Key: XERCESJ-1473 URL: https://issues.apache.org/jira/browse/XERCESJ-1473 Project: Xerces2-J Issue Type: Bug Reporter: Josh Spiegel In org.apache.xerces.impl.xpath.regex.RegexParser I think the processBackreference() method has a bug. I think this line: if ('1' <= ch && ch <= '9') { Should be: if ('0' <= ch && ch <= '9') { In order to correctly process backreferences where a subsequent digit is 0. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: jenny79@example.org For additional commands, e-mail: jenny79@example.org From jenny79@example.org Tue Nov 09 00:08:02 2010 Return-Path: <jenny79@example.org> Delivered-To: jenny79@example.org Received: (qmail 69176 invoked from network); 9 Nov 2010 00:08:02 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 9 Nov 2010 00:08:02 -0000 Received: (qmail 61272 invoked by uid 500); 9 Nov 2010 00:08:34 -0000 Delivered-To: jenny79@example.org Received: (qmail 61180 invoked by uid 500); 9 Nov 2010 00:08:33 -0000 Mailing-List: contact jenny79@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenny79@example.org> List-Unsubscribe: <mailto:jenny79@example.org> List-Post: <mailto:jenny79@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: jenny79@example.org Delivered-To: mailing list jenny79@example.org Received: (qmail 61172 invoked by uid 99); 9 Nov 2010 00:08:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Nov 2010 00:08:33 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO thor.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Nov 2010 00:08:33 +0000 Received: from thor (localhost [83.161.120.155]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oA908DNw000495 for <jenny79@example.org>; Tue, 9 Nov 2010 00:08:13 GMT Message-ID: <26842867.89681289261293165.JavaMail.jira@thor> Date: Mon, 8 Nov 2010 19:08:13 -0500 (EST) From: "Michael Glavassevich (JIRA)" <jenny79@example.org> To: jenny79@example.org Subject: [jira] Assigned: (XERCESJ-1473) RegexParser backreference problem In-Reply-To: <1924216.87581289257693313.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/XERCESJ-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich reassigned XERCESJ-1473: --------------------------------------------- Assignee: Khaled Noaman > RegexParser backreference problem > --------------------------------- > > Key: XERCESJ-1473 > URL: https://issues.apache.org/jira/browse/XERCESJ-1473 > Project: Xerces2-J > Issue Type: Bug > Components: XML Schema 1.0 Datatypes > Affects Versions: 2.10.0 > Reporter: Josh Spiegel > Assignee: Khaled Noaman > Priority: Minor > > In org.apache.xerces.impl.xpath.regex.RegexParser > I think the processBackreference() method has a bug. > I think this line: > if ('1' <= ch && ch <= '9') { > Should be: > if ('0' <= ch && ch <= '9') { > In order to correctly process backreferences where a subsequent digit is 0. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: jenny79@example.org For additional commands, e-mail: jenny79@example.org From jenny79@example.org Tue Nov 09 00:08:03 2010 Return-Path: <jenny79@example.org> Delivered-To: jenny79@example.org Received: (qmail 69181 invoked from network); 9 Nov 2010 00:08:02 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 9 Nov 2010 00:08:02 -0000 Received: (qmail 61245 invoked by uid 500); 9 Nov 2010 00:08:34 -0000 Delivered-To: jenny79@example.org Received: (qmail 61171 invoked by uid 500); 9 Nov 2010 00:08:33 -0000 Mailing-List: contact jenny79@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenny79@example.org> List-Unsubscribe: <mailto:jenny79@example.org> List-Post: <mailto:jenny79@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: jenny79@example.org Delivered-To: mailing list jenny79@example.org Received: (qmail 61164 invoked by uid 99); 9 Nov 2010 00:08:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Nov 2010 00:08:33 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO thor.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Nov 2010 00:08:32 +0000 Received: from thor (localhost [83.161.120.155]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oA908BZj000483 for <jenny79@example.org>; Tue, 9 Nov 2010 00:08:12 GMT Message-ID: <20230892.89641289261291542.JavaMail.jira@thor> Date: Mon, 8 Nov 2010 19:08:11 -0500 (EST) From: "Michael Glavassevich (JIRA)" <jenny79@example.org> To: jenny79@example.org Subject: [jira] Updated: (XERCESJ-1473) RegexParser backreference problem In-Reply-To: <1924216.87581289257693313.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/XERCESJ-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-1473: ------------------------------------------ Component/s: XML Schema 1.0 Datatypes Affects Version/s: 2.10.0 > RegexParser backreference problem > --------------------------------- > > Key: XERCESJ-1473 > URL: https://issues.apache.org/jira/browse/XERCESJ-1473 > Project: Xerces2-J > Issue Type: Bug > Components: XML Schema 1.0 Datatypes > Affects Versions: 2.10.0 > Reporter: Josh Spiegel > > In org.apache.xerces.impl.xpath.regex.RegexParser > I think the processBackreference() method has a bug. > I think this line: > if ('1' <= ch && ch <= '9') { > Should be: > if ('0' <= ch && ch <= '9') { > In order to correctly process backreferences where a subsequent digit is 0. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: jenny79@example.org For additional commands, e-mail: jenny79@example.org From jenny79@example.org Tue Nov 09 00:08:05 2010 Return-Path: <jenny79@example.org> Delivered-To: jenny79@example.org Received: (qmail 69251 invoked from network); 9 Nov 2010 00:08:05 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 9 Nov 2010 00:08:05 -0000 Received: (qmail 61603 invoked by uid 500); 9 Nov 2010 00:08:36 -0000 Delivered-To: jenny79@example.org Received: (qmail 61572 invoked by uid 500); 9 Nov 2010 00:08:36 -0000 Mailing-List: contact jenny79@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenny79@example.org> List-Unsubscribe: <mailto:jenny79@example.org> List-Post: <mailto:jenny79@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: jenny79@example.org Delivered-To: mailing list jenny79@example.org Received: (qmail 61565 invoked by uid 99); 9 Nov 2010 00:08:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Nov 2010 00:08:36 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO thor.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Nov 2010 00:08:34 +0000 Received: from thor (localhost [83.161.120.155]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oA908Cx7000489 for <jenny79@example.org>; Tue, 9 Nov 2010 00:08:12 GMT Message-ID: <766214.89661289261292721.JavaMail.jira@thor> Date: Mon, 8 Nov 2010 19:08:12 -0500 (EST) From: "Michael Glavassevich (JIRA)" <jenny79@example.org> To: jenny79@example.org Subject: [jira] Updated: (XERCESJ-1473) RegexParser backreference problem In-Reply-To: <1924216.87581289257693313.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/XERCESJ-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-1473: ------------------------------------------ Priority: Minor (was: Major) > RegexParser backreference problem > --------------------------------- > > Key: XERCESJ-1473 > URL: https://issues.apache.org/jira/browse/XERCESJ-1473 > Project: Xerces2-J > Issue Type: Bug > Components: XML Schema 1.0 Datatypes > Affects Versions: 2.10.0 > Reporter: Josh Spiegel > Priority: Minor > > In org.apache.xerces.impl.xpath.regex.RegexParser > I think the processBackreference() method has a bug. > I think this line: > if ('1' <= ch && ch <= '9') { > Should be: > if ('0' <= ch && ch <= '9') { > In order to correctly process backreferences where a subsequent digit is 0. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: jenny79@example.org For additional commands, e-mail: jenny79@example.org From jenny79@example.org Wed Nov 10 19:30:09 2010 Return-Path: <jenny79@example.org> Delivered-To: jenny79@example.org Received: (qmail 26638 invoked from network); 10 Nov 2010 19:30:08 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 10 Nov 2010 19:30:08 -0000 Received: (qmail 36299 invoked by uid 500); 10 Nov 2010 19:30:40 -0000 Delivered-To: jenny79@example.org Received: (qmail 36251 invoked by uid 500); 10 Nov 2010 19:30:39 -0000 Mailing-List: contact jenny79@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenny79@example.org> List-Unsubscribe: <mailto:jenny79@example.org> List-Post: <mailto:jenny79@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: jenny79@example.org Delivered-To: mailing list jenny79@example.org Received: (qmail 36244 invoked by uid 99); 10 Nov 2010 19:30:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Nov 2010 19:30:39 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO thor.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Nov 2010 19:30:38 +0000 Received: from thor (localhost [83.161.120.155]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oAAJUHnI001005 for <jenny79@example.org>; Wed, 10 Nov 2010 19:30:18 GMT Message-ID: <32067870.11771289417417955.JavaMail.jira@thor> Date: Wed, 10 Nov 2010 14:30:17 -0500 (EST) From: "Khaled Noaman (JIRA)" <jenny79@example.org> To: jenny79@example.org Subject: =?utf-8?Q?[jira]_Resolved:_(XERCESJ-1433)_[GSoC]:_Implementing_XML_S?= =?utf-8?Q?chema_1.1=C2=A0overriding_component_definitions_(<xs:override>)?= MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/XERCESJ-1433?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:all-tabpanel ] Khaled Noaman resolved XERCESJ-1433. ------------------------------------ Resolution: Fixed Fix Version/s: 2.11.0 Patch applied with some minor modifications > [GSoC]: Implementing XML Schema 1.1=C2=A0overriding component definitions= (<xs:override>) > -------------------------------------------------------------------------= ----------- > > Key: XERCESJ-1433 > URL: https://issues.apache.org/jira/browse/XERCESJ-1433 > Project: Xerces2-J > Issue Type: New Feature > Components: XML Schema 1.1 Structures > Affects Versions: 2.9.1 > Reporter: Michael Glavassevich > Assignee: Khaled Noaman > Fix For: 2.11.0 > > Attachments: schema1_1_override_patch.tar.gz > > > XML schema specification version 1.1 [1] specifies syntax and semantics o= f "Overriding component definitions<override>"[2] or xs:override , under "S= chemas and Namespaces: Access and Composition" . The new component definiti= on is a powerful addition to the XML schema composition framework=C2=A0 ,wh= ich tries to mitigate some of the constraints present in similar constructs= such as xs:redefine or <redefine> schema component.=20 > The <redefine> construct defined in "Including modified component definit= ions (<redefine>) "[3] on XMLSchema specification is useful in schema evolu= tion and versioning. It can be used only when there exists some restriction= or extension relation between the old component and the new redefined comp= onent. But there are occasions when the schema author simply wants to repla= ce old components with new ones without any constraint. Also, existing XSD = processors have implemented conflicting and non-interoperable interpretatio= ns of <redefine>. The implementation of=C2=A0 new construct <override> on X= erces XML Schema processor ,would avoid these bottlenecks and allow unconst= rained replacement as and when needed by the schema author. > Possible Mentors: Khaled Noaman > =C2=A0=20 > [1] http://www.w3.org/TR/2006/REC-xml11-20060816/ > [2] http://www.w3.org/TR/xmlschema11-1/#override-schema > [3] http://www.w3.org/TR/xmlschema11-1/#modify-schema --=20 This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: jenny79@example.org For additional commands, e-mail: jenny79@example.org From jenny79@example.org Wed Nov 10 19:38:04 2010 Return-Path: <jenny79@example.org> Delivered-To: jenny79@example.org Received: (qmail 29025 invoked from network); 10 Nov 2010 19:38:04 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 10 Nov 2010 19:38:04 -0000 Received: (qmail 48113 invoked by uid 500); 10 Nov 2010 19:38:35 -0000 Delivered-To: jenny79@example.org Received: (qmail 48096 invoked by uid 500); 10 Nov 2010 19:38:35 -0000 Mailing-List: contact jenny79@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:jenny79@example.org> List-Unsubscribe: <mailto:jenny79@example.org> List-Post: <mailto:jenny79@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: jenny79@example.org Delivered-To: mailing list jenny79@example.org Received: (qmail 48089 invoked by uid 99); 10 Nov 2010 19:38:35 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Nov 2010 19:38:35 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO thor.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Nov 2010 19:38:35 +0000 Received: from thor (localhost [83.161.120.155]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oAAJcEJN001120 for <jenny79@example.org>; Wed, 10 Nov 2010 19:38:14 GMT Message-ID: <23936155.12001289417894340.JavaMail.jira@thor> Date: Wed, 10 Nov 2010 14:38:14 -0500 (EST) From: "Khaled Noaman (JIRA)" <jenny79@example.org> To: jenny79@example.org Subject: [jira] Resolved: (XERCESJ-1473) RegexParser backreference problem In-Reply-To: <1924216.87581289257693313.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/XERCESJ-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Khaled Noaman resolved XERCESJ-1473. ------------------------------------ Resolution: Fixed Fix Version/s: 2.11.0 Fix checked in. > RegexParser backreference problem > --------------------------------- > >
{'source': 'Apache Software Foundation Public Mail Archives'}