Author: mukulg
Date: Sat Dec 14 08:04:19 2019
New Revision: 1871418
URL: http://svn.apache.org/viewvc?rev=1871418&view=rev
Log:
adding information to release information meta data, for xerces 2.12.1 release
Modified:
xerces/java/branches/xml-schema-1.1-dev/docs/releases.xml
xerces/java/trunk/docs/releases.xml
Modified: xerces/java/branches/xml-schema-1.1-dev/docs/releases.xml
URL:
http://svn.apache.org/viewvc/xerces/java/branches/xml-schema-1.1-dev/docs/releases.xml?rev=1871418&r1=1871417&r2=1871418&view=diff
==============================================================================
--- xerces/java/branches/xml-schema-1.1-dev/docs/releases.xml (original)
+++ xerces/java/branches/xml-schema-1.1-dev/docs/releases.xml Sat Dec 14
08:04:19 2019
@@ -18,6 +18,64 @@
<!-- $Id$ -->
<!DOCTYPE releases SYSTEM 'dtd/releases.dtd'>
<releases>
+ <release version='&ParserName; 2.12.1'>
+ <desc>
+ <p>
+ This release is a bug fix release. It fixes few bugs which were present
in Xerces-J 2.12.0
+ and also includes a few other minor enhancements.
+ </p>
+ </desc>
+ <changes>
+ <update>
+ <note>
+ For certain cases, while doing XML Schema 1.1 assert validations,
error messages appeared
+ like following 'FOAR0001 - Division by zero'. Modified such error
messages, to now contain
+ the character ':' instead of '-' (since, the character '-' can be
confused with a negation symbol).
+ </note>
+ <submitter name='Mukul Gandhi'/>
+ </update>
+ <fix>
+ <note>
+ As described in XSD 1.1 REC in the section, "3.2.3 Constraints on
XML Representations of
+ Attribute Declarations (Schema Representation Constraint: Attribute
Declaration
+ Representation)", '5 If fixed and use are both present, use must not
have the actual value
+ prohibited'. This is newly introduced in XSD 1.1. Fixed a runtime
validation issue for this
+ XSD clause, when XSD 1.1 implementation is invoked in XSD 1.0 mode.
+ </note>
+ <submitter name='Mukul Gandhi'/>
+ </fix>
+ <fix>
+ <note>
+ Xerces-J was previously not building from sources when Java 9+ was
used. This release fixes this.
+ </note>
+ <submitter name='Thomas Pasch, Mukul Gandhi'/>
+ </fix>
+ <fix>
+ <note>
+ While doing XML Schema 1.1 validation, when the schema document is
specified via xsi:schemaLocation
+ attribute in the XML document, when full XPath 2.0 was used with
CTA, for certain use cases
+ validation was not occurring correctly. This release fixes this.
+ </note>
+ <submitter name='Yitzhak Khabinsky, Mukul Gandhi'/>
+ </fix>
+ <fix>
+ <note>
+ XML Schema 1.1 has introduced a 'ref' attribute on xs:key, xs:unique
and xs:keyref. When certain such
+ schema documents were processed by Xerces-J's XSD 1.1 implementation
in XSD 1.0 mode,
+ java.lang.NullPointerException was produced. This release fixes this.
+ </note>
+ <submitter name='Mukul Gandhi'/>
+ </fix>
+ <fix>
+ <note>
+ When XML Schema 1.1 validations are done, where xs:assert are
contained within xs:override, the XPath
+ expressions within xs:assert can't see XML namespace bindings
specified at certain locations in schema
+ documents. This release fixes this.
+ </note>
+ <submitter name='Patrick Gratz, Mukul Gandhi'/>
+ </fix>
+ </changes>
+ </release>
<release version='&ParserName; 2.12.0'>
<desc>
<p>
Modified: xerces/java/trunk/docs/releases.xml
URL:
http://svn.apache.org/viewvc/xerces/java/trunk/docs/releases.xml?rev=1871418&r1=1871417&r2=1871418&view=diff
==============================================================================
--- xerces/java/trunk/docs/releases.xml (original)
+++ xerces/java/trunk/docs/releases.xml Sat Dec 14 08:04:19 2019
@@ -18,6 +18,64 @@
<!-- $Id$ -->
<!DOCTYPE releases SYSTEM 'dtd/releases.dtd'>
<releases>
+ <release version='&ParserName; 2.12.1'>
+ <desc>
+ <p>
+ This release is a bug fix release. It fixes few bugs which were present
in Xerces-J 2.12.0
+ and also includes a few other minor enhancements.
+ </p>
+ </desc>
+ <changes>
+ <update>
+ <note>
+ For certain cases, while doing XML Schema 1.1 assert validations,
error messages appeared
+ like following 'FOAR0001 - Division by zero'. Modified such error
messages, to now contain
+ the character ':' instead of '-' (since, the character '-' can be
confused with a negation symbol).
+ </note>
+ <submitter name='Mukul Gandhi'/>
+ </update>
+ <fix>
+ <note>
+ As described in XSD 1.1 REC in the section, "3.2.3 Constraints on
XML Representations of
+ Attribute Declarations (Schema Representation Constraint: Attribute
Declaration
+ Representation)", '5 If fixed and use are both present, use must not
have the actual value
+ prohibited'. This is newly introduced in XSD 1.1. Fixed a runtime
validation issue for this
+ XSD clause, when XSD 1.1 implementation is invoked in XSD 1.0 mode.
+ </note>
+ <submitter name='Mukul Gandhi'/>
+ </fix>
+ <fix>
+ <note>
+ Xerces-J was previously not building from sources when Java 9+ was
used. This release fixes this.
+ </note>
+ <submitter name='Thomas Pasch, Mukul Gandhi'/>
+ </fix>
+ <fix>
+ <note>
+ While doing XML Schema 1.1 validation, when the schema document is
specified via xsi:schemaLocation
+ attribute in the XML document, when full XPath 2.0 was used with
CTA, for certain use cases
+ validation was not occurring correctly. This release fixes this.
+ </note>
+ <submitter name='Yitzhak Khabinsky, Mukul Gandhi'/>
+ </fix>
+ <fix>
+ <note>
+ XML Schema 1.1 has introduced a 'ref' attribute on xs:key, xs:unique
and xs:keyref. When certain such
+ schema documents were processed by Xerces-J's XSD 1.1 implementation
in XSD 1.0 mode,
+ java.lang.NullPointerException was produced. This release fixes this.
+ </note>
+ <submitter name='Mukul Gandhi'/>
+ </fix>
+ <fix>
+ <note>
+ When XML Schema 1.1 validations are done, where xs:assert are
contained within xs:override, the XPath
+ expressions within xs:assert can't see XML namespace bindings
specified at certain locations in schema
+ documents. This release fixes this.
+ </note>
+ <submitter name='Patrick Gratz, Mukul Gandhi'/>
+ </fix>
+ </changes>
+ </release>
<release version='&ParserName; 2.12.0'>
<desc>
<p>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
