updating xalanj documentation details, within xalan-site repos
diff --git a/charter.html b/charter.html
index a914773..f099309 100644
--- a/charter.html
+++ b/charter.html
@@ -82,11 +82,9 @@
<a href="xalan-c/index.html">Xalan C++</a>
</li>
<li>
-<a href="xalan-j/index.html">Xalan Java 2.7.2</a>
+<a href="xalan-j/index.html">Xalan Java 2.7.3</a>
</li>
-<li>
-<a href="old/xalan-j/index.html">Xalan Java 2.7.1</a>
-</li></ul><hr /><ul></ul>
+</ul><hr/><ul></ul>
<p class="navGroup">
<em>Mail Lists</em>
</p><ul>
@@ -128,7 +126,7 @@
</p>
<h3>Xalan Project Charter</h3>
<p>The following charter applies to all Xalan projects.</p>
-
+
<p align="right" size="2">
<a href="#content">(top)</a>
@@ -143,14 +141,14 @@
documentation.</p>
<p>1.2 This charter briefly describes the mission, history, organization
and processes of the project.</p>
-
+
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
<h3>2 MISSION</h3>
<p>2.1 Apache Xalan exists to promote the use of XSLT. We view XSLT
- (Extensible Stylesheet Language Transformations) as a compelling
+ (Extensible Stylesheet Language Transformations) as a compelling
paradigm that transforms XML documents, thereby facilitating the
exchange, transformation, and presentation of knowledge. The ability
to transform XML documents into usable information has great potential
@@ -173,12 +171,12 @@
components and other components and applications, standards (formal or
de facto) will be used as much as possible for both protocols and
APIs. Where appropriate, experiences and lessons learned will be fed
- back to standards bodies in an effort to assist in the development of
+ back to standards bodies in an effort to assist in the development of
those standards. We will also encourage the innovation of new
protocols, APIs, and components in order to seed new concepts not
yet defined by standards.</p>
-
-
+
+
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
@@ -187,17 +185,17 @@
Software Foundation in October 2004 to facilitate joint open-source
development. Prior to October 2004 this project was a subproject
of the Apache XML project.</p>
-
-
+
+
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
<h3>4 TERMS</h3>
- <p>4.1 The ASF Board. The management board of the Apache Software
+ <p>4.1 The ASF Board. The management board of the Apache Software
Foundation.</p>
- <p>4.2 The Project. The Apache Xalan project; intended to refer to the
+ <p>4.2 The Project. The Apache Xalan project; intended to refer to the
source code, website, subprojects, and community that are Apache Xalan.</p>
- <p>4.3 Subproject. The Apache Xalan project may have subprojects; a
+ <p>4.3 Subproject. The Apache Xalan project may have subprojects; a
subproject is responsible for a component or application whose scope
is well defined.</p>
<p>4.4 Product. Some deliverable (usually a binary or source package)
@@ -207,30 +205,30 @@
multiple releases of a given product.</p>
<p>4.6 Contributor. Anyone who makes a contribution to the development
of the Apache Xalan project.</p>
- <p>4.7 Committer. The Apache Xalan project has a set of committers.
+ <p>4.7 Committer. The Apache Xalan project has a set of committers.
Committers are contributors who have read/write access to the source
code repository.</p>
<p>4.8 PMC. The PMC (Project Management Committee) is the group of people
- that form the entity that makes decisions and controls the project.
+ that form the entity that makes decisions and controls the project.
Individual people or committers do not control the project.</p>
-
-
+
+
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
<h3>5 THE PROJECT MANAGEMENT COMMITTEE</h3>
- <p>5.1 The Apache Xalan project is managed by a core group of committers
+ <p>5.1 The Apache Xalan project is managed by a core group of committers
known as the Project Management Committee [PMC]. Subprojects, if any,
much each have at least one representative committer on the PMC.</p>
<p>5.2 The activities of the PMC are coordinated by the Chairperson,
who is an officer of the corporation and reports to the Apache
- Board. The Chairperson will, on the request of the Apache Board,
- provide reports to the Board on issues related to the running of
+ Board. The Chairperson will, on the request of the Apache Board,
+ provide reports to the Board on issues related to the running of
the Apache Xalan project.</p>
<p>5.3 The PMC has the following responsibilities:</p>
<p>a) Accepting new subproject proposals, formally submitting these
proposals for Apache Xalan committer vote, and creating the subproject
- (see SUBPROJECTS below). This is done in collaboration with the
+ (see SUBPROJECTS below). This is done in collaboration with the
Incubator (see <a href="http://incubator.apache.org">http://incubator.apache.org</a>).</p>
<p>b) Facilitating code or other donations by individuals or companies,
in collaboration with the Incubator.</p>
@@ -238,24 +236,24 @@
the ASF board.</p>
<p>d) Ensuring that administrative and infrastructure work is completed.</p>
<p>e) Facilitating relationships among projects and subprojects.</p>
- <p>f) Facilitating relationships between the Apache Xalan project and the
+ <p>f) Facilitating relationships between the Apache Xalan project and the
external world.</p>
- <p>g) Overseeing Apache Xalan to ensure that the mission defined in this
+ <p>g) Overseeing Apache Xalan to ensure that the mission defined in this
document is being fulfilled.</p>
<p>h) Resolving conflicts within the project.</p>
<p>i) Reporting to the ASF board (through the Chair) on the progress
of the project.</p>
<p>j) Propose new releases of projects or subprojects. Such proposals pass
- if 75% of the PMC members vote in agreement.</p>
-
+ if 75% of the PMC members vote in agreement.</p>
+
<p>5.4 A contributor can, at any time, nominate a committer to be on the PMC,
- by calling for a vote. If two thirds, or more, of the active committers
+ by calling for a vote. If two thirds, or more, of the active committers
vote in agreement then the nomination is given to the PMC. The person
becomes a new PMC member if 75% or more of the PMC members vote in
agreement, with no dissenting votes among the PMC members. This individual
- should be elected based on merit for the evolution of the project and
+ should be elected based on merit for the evolution of the project and
demonstration of commitment.</p>
- <p>5.5 In cases where the subproject is unable to directly provide a
+ <p>5.5 In cases where the subproject is unable to directly provide a
representative on the PMC, another member of the PMC will be required to
represent that subproject on the PMC. This will be strongly discouraged.
It is preferable that all subprojects have direct representation on the
@@ -269,8 +267,8 @@
if they are not already, be appointed an officer of the corporation. See
<a href="http://www.apache.org/foundation/bylaws.html">
http://www.apache.org/foundation/bylaws.html</a> for more information.</p>
- <p>5.8 The PMC is responsible for maintaining and updating this charter.
- Development must follow the process outlined below, so any change to the
+ <p>5.8 The PMC is responsible for maintaining and updating this charter.
+ Development must follow the process outlined below, so any change to the
development process necessitates a change to the charter. Proposed changes
to this charter by the PMC are passed if 75% or more of the PMC members
approve the proposal, with no dissenting votes. However, an active Apache
@@ -290,15 +288,15 @@
votes among the other PMC members.</p>
<p>5.12 A person remains a PMC member until he or she resigns, is removed by a
vote from among the other PMC members, dies or is incapacitated.</p>
-
+
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
<h3>6 SUBPROJECTS</h3>
- <p>6.1 A subproject of the Apache Xalan project is responsible for a component
- or application whose scope is well defined. Each subproject has its own set
- of developers, and is responsible for approving its own committers. Apache
+ <p>6.1 A subproject of the Apache Xalan project is responsible for a component
+ or application whose scope is well defined. Each subproject has its own set
+ of developers, and is responsible for approving its own committers. Apache
Xalan is composed of subprojects which fit into one of two categories:</p>
<p>(a) An XSLT processor implementation in some particular programming
language. There may be multiple processors for a given language if
@@ -324,8 +322,8 @@
challenge the active committers approve the removal with a two-thirds
majority vote. Any subproject removal is subject to the approval of the
ASF board.</p>
-
-
+
+
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
@@ -334,7 +332,7 @@
meritocracy -- the more work you do, the more you are allowed to do.</p>
<p>7.2 People who make regular and substantial contributions may become
committers as described below. Contributions include: participating in
- mailing lists, reporting issues or bugs in issue-records in the Issue Database,
+ mailing lists, reporting issues or bugs in issue-records in the Issue Database,
providing patches, and proposing changes to a product.</p>
<p>7.3 In order to ensure that all code contained in the Apache Xalan
project's code repository is free of licensing, intellectual property and patent
@@ -343,9 +341,9 @@
<p>a) If contributing as an individual, sign the "Individual
Contributor License Agreement (CLA)"
(<a href="http://www.apache.org/licenses/icla.txt">http://www.apache.org/licenses/icla.txt</a>)
- and file a copy with the Secretary of the Corporation; or </p>
+ and file a copy with the Secretary of the Corporation; or </p>
<p>b) If making the contribution as part of their employment
- responsibilities, sign the "Corporate CLA (CCLA)",
+ responsibilities, sign the "Corporate CLA (CCLA)",
(<a href="http://www.apache.org/licenses/cla-corporate.txt">http://www.apache.org/licenses/cla-corporate.txt</a>)
and file a copy with the Secretary of the Corporation.</p>
<p>7.4 If the contribution in question is a small bugfix, the contributor need
@@ -363,18 +361,18 @@
<p>e) Are you aware of any third-party licenses or other
restrictions (such as related patents or trademarks) that could
apply to your contribution? If so, what are they?</p>
-
-
+
+
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
<h3>8 COMMITTERS</h3>
<p>8.1 The Apache Xalan project has a set of committers. If there
are subprojects, each subproject will also have a set of committers.
- Committers are contributors who have read/write access to the source code
- repository. New committers are added when a contributor is nominated by a
- committer and approved by at least 50 percent of the active committers for
- that subproject with no opposing votes. In most cases, new committers will
+ Committers are contributors who have read/write access to the source code
+ repository. New committers are added when a contributor is nominated by a
+ committer and approved by at least 50 percent of the active committers for
+ that subproject with no opposing votes. In most cases, new committers will
already be participating in the development process by submitting suggestions
and/or fixes via issue-records in the Issue Database or mailing lists.</p>
<p>8.2 For the purposes of voting, committers will be classed as "active" or
@@ -389,8 +387,8 @@
<p>8.4 An inactive status will not prevent a committer committing new code
changes or posting to the mailing lists. Either of these activities will
automatically re-activate the committer for the purposes of voting.</p>
-
-
+
+
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
@@ -405,7 +403,7 @@
documentation and other associated parts that are stored in
the repository. Any subproject will have its set of committers
for its repository.</p>
- <p>c) Website -- The website <a href="http://xalan.apache.org">xalan.apache.org</a>
+ <p>c) Website -- The website <a href="http://xalan.apache.org">xalan.apache.org</a>
will contain information about the Apache Xalan project and its subprojects,
including documentation, downloads of releases, and this charter.</p>
<p>d) Mailing Lists -- appropriate mailing lists will be created
@@ -413,8 +411,8 @@
for example include: a PMC mailing list, a general mailing list,
project or subproject public developer mailing lists,
project or subproject public user mailing lists.</p>
-
-
+
+
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
@@ -428,23 +426,23 @@
it is the responsibility of the committer, in consultation with
the PMC, to conduct due diligence on the pedigree of the
contribution under consideration; see sections 7.3 and 7.4. </p>
-
-
+
+
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
-<h3>11 THE DEVELOPMENT PROCESS</h3>
+<h3>11 THE DEVELOPMENT PROCESS</h3>
<p>11.1 For a committer to commit a change to the MAIN branch of the
repository an issue-record must be opened in the "Issue Database"
to track the change. The status of the issue must be kept up to date.</p>
- <p>11.2 No voting is required to commit changes, but one other active
+ <p>11.2 No voting is required to commit changes, but one other active
committer must review the changes. Before the changes are committed, the reviewer
must add a comment in the corresponding issue-record indicating that
they have reviewed and approve the changes.</p>
<p>11.3 Issue-records and reviews are not required for committing changes to
other experimental branches (not the MAIN branch) in a repository.</p>
-
-
+
+
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
@@ -453,8 +451,8 @@
proposals must be made within two weeks of the proposal. A challenge to
a proposal must also be made within two weeks of the proposal. Likewise,
votes cast on challenges must be cast within two weeks of the challenge.</p>
-
-
+
+
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
@@ -463,12 +461,12 @@
projects, such as Xerces and XML, to avoid redundancy
and achieve a coherent architecture among Apache Xalan and these
projects.</p>
-
+
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
</div>
-<div id="footer">Copyright © 1999-2023 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sat 2023-01-21</div>
+<div id="footer">Copyright © 1999-2023 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Tue 2023-04-04</div>
</div>
</body>
</html>
diff --git a/index.html b/index.html
index 3c7aba8..cc731f0 100644
--- a/index.html
+++ b/index.html
@@ -82,11 +82,9 @@
<a href="xalan-c/index.html">Xalan C++</a>
</li>
<li>
-<a href="xalan-j/index.html">Xalan Java 2.7.2</a>
+<a href="xalan-j/index.html">Xalan Java</a>
</li>
-<li>
-<a href="old/xalan-j/index.html">Xalan Java 2.7.1</a>
-</li></ul><hr /><ul></ul>
+</ul><hr/><ul></ul>
<p class="navGroup">
<em>Mail Lists</em>
</p><ul>
@@ -123,10 +121,7 @@
</div>
<div id="content">
<h2>The Apache Xalan Project</h2>
-<p>We are proud to release version 2.7.2 of our Xalan Java project. This is
-the first product distribution release of Xalan Java since Apache Xalan was
-reformed in 2011. It also fixes a security issue reported against the
-previous version.
+<p>We are proud to release version 2.7.3 of our Xalan Java project.
</p>
<p>The Apache Xalan Project develops and maintains libraries and programs
that transform XML documents using XSLT standard stylesheets. Our
@@ -134,17 +129,17 @@
the XSLT libraries.
</p>
<p>The Apache Xalan Project was reformed in 2011. It started as a
-subproject of Apache XML which has since been officially retired.
+subproject of Apache XML which has since been officially retired.
The Apache Xalan Project continues as a top-level project governed by the
Apache Software Foundation as a collaborative software development community
-dedicated to providing robust, full-featured, commercial-quality, and
+dedicated to providing robust, full-featured, commercial-quality, and
freely available XSLT support on a wide variety of platforms.
</p>
<p>The supported specifications are defined by the
-<a href="http://www.w3.org/TR/xslt">W3C XSL Transformations (XSLT)
-Version 1.0</a> and the <a href="http://www.w3.org/TR/xpath">XML Path Language (XPath) Version 1.0</a>
+<a href="https://www.w3.org/TR/1999/REC-xslt-19991116">W3C XSL Transformations (XSLT)
+Version 1.0</a> and the <a href="https://www.w3.org/TR/1999/REC-xpath-19991116">XML Path Language (XPath) Version 1.0</a>
recommendations.
-</p>
+</p>
<p>
<b>Contents:</b>
</p>
@@ -171,16 +166,16 @@
<a href="#content">(top)</a>
</p>
<h3>Apache Xalan Projects</h3>
-<p>There are currently two subprojects under the Apache Xalan Project:
-<a href="xalan-c/index.html">Xalan C++</a>, and
+<p>There are currently two subprojects under the Apache Xalan Project:
+<a href="xalan-c/index.html">Xalan C++</a>, and
<a href="xalan-j/index.html">Xalan Java</a>, representing
-C++ and Java implementations of the
-<a href="http://www.w3.org/TR/xslt">W3C XSL Transformations (XSLT)
-Version 1.0</a> and the
-<a href="http://www.w3.org/TR/xpath">XML Path Language (XPath) Version 1.0</a>
+C++ and Java implementations of the
+<a href="http://www.w3.org/TR/xslt">W3C XSL Transformations (XSLT)
+Version 1.0</a> and the
+<a href="http://www.w3.org/TR/xpath">XML Path Language (XPath) Version 1.0</a>
recommendations.
-</p>
-<p>Both the Java and C++ development teams provide libraries and
+</p>
+<p>Both the Java and C++ development teams provide libraries and
executable programs to transform XML documents using XSLT stylesheets.
</p>
<p align="right" size="2">
@@ -217,20 +212,19 @@
<a href="#content">(top)</a>
</p>
<h4>Xalan Java Project</h4>
-<p>The <a href="xalan-j/index.html">Xalan-Java 2.7.2</a> was released in April 2014. You can download the current release
-the current <a href="http://www.apache.org/dyn/closer.cgi/xalan/xalan-j/">Xalan-Java 2.7.2</a> release for your development. The
-current work in progress can be found in the
-<a href="http://svn.apache.org/repos/asf/xalan/xalan-j/trunk/">subversion repository</a>.
+<p>The <a href="xalan-j/index.html">Xalan-Java 2.7.3</a> was released in April 2023. You may download the current Xalan-Java
+release <a href="http://www.apache.org/dyn/closer.cgi/xalan/xalan-j/">Xalan-Java 2.7.3</a> for your development. The
+current work in progress can be found in the
+<a href="https://gitbox.apache.org/repos/asf?p=xalan-java.git">git repository</a>.
</p>
-<p>The current release fixes a security issue that was registered against version 2.7.1.
+<p>The current release among other Xalan-J implementation features, fixes a Xalan-J XSLTC security issue that was registered
+against version 2.7.2.
</p>
-<p>The old <a href="old/xalan-j/index.html">Xalan-J 2.7.1</a>
-distributions are still available on the
-<a href="http://archive.apache.org/dist/xml/xalan-j">Apache Archives</a>.
+<p>Many of the earlier Xalan-J distributions are still available on the <a href="http://archive.apache.org/dist/xml/xalan-j">Apache Archives</a>.
</p>
<p>This is a mature project. There has been some discussion about supporting XPath-2.
-We could use your support in this major rework of the library.
-You can follow the efforts and post your own contributions
+We could use your support in this major rework of the library.
+You can follow the efforts and post your own contributions
on the Java users and developers mail lists.
</p>
@@ -240,18 +234,18 @@
<a href="#content">(top)</a>
</p>
<h3>What is XSLT and XPath?</h3>
-<p>XSLT is the first part of the
-<a href="http://www.w3.org/TR/xsl/">Extensible Stylesheet Language (XSL)</a>.
-It includes the XSL Transformation (XSLT) vocabulary and
-XPath, a language for addressing parts of XML documents.
-XSL also includes a vocabulary for specifying formatting semantics, however,
-this is not part of the Apache Xalan Project. For more information on formatting objects, see the
+<p>XSLT is the first part of the
+<a href="http://www.w3.org/TR/xsl/">Extensible Stylesheet Language (XSL)</a>.
+It includes the XSL Transformation (XSLT) vocabulary and
+XPath, a language for addressing parts of XML documents.
+XSL also includes a vocabulary for specifying formatting semantics, however,
+this is not part of the Apache Xalan Project. For more information on formatting objects, see the
<a href="http://xmlgraphics.apache.org/fop/">Apache XML Graphics (Formatting Objects Project)</a>.
</p>
<p>XSLT implementations, sometimes referred to as XSLT processors, use an XSL stylesheet to transform
-XML documents into HTML, text, or other XML document types.
-In structural terms, an XSL stylesheet
-specifies the transformation of one tree of nodes (the XML input)
+XML documents into HTML, text, or other XML document types.
+In structural terms, an XSL stylesheet
+specifies the transformation of one tree of nodes (the XML input)
into another tree of nodes (the output or transformation result).
</p>
@@ -268,7 +262,7 @@
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
-<h3>Getting Involved</h3>
+<h3>Getting Involved</h3>
<p>We always appreciate people and organizations that wish to help
in the development and project support efforts.</p>
@@ -284,16 +278,16 @@
<p>Each subproject has its own mail list for project specific user
issues.</p>
-<p>The user list for Xalan C++
- [<a href="mailto:c-users@xalan.apache.org">xalan-c-users</a>] is
+<p>The user list for Xalan C++
+ [<a href="mailto:c-users@xalan.apache.org">xalan-c-users</a>] is
for general user comments on the Xalan C++ project.</p>
-<p>The user list for Xalan Java
+<p>The user list for Xalan Java
[<a href="mailto:j-users@xalan.apache.org">xalan-j-users</a>] is
for general user comments on the Xalan Java project.</p>
-<p>The Apache Software Foundation has guidance on
- <a href="http://www.apache.org/foundation/getinvolved.html">how to
+<p>The Apache Software Foundation has guidance on
+ <a href="http://www.apache.org/foundation/getinvolved.html">how to
participate</a> in the various development efforts.</p>
<a name="Security"></a>
@@ -312,7 +306,7 @@
<a href="#content">(top)</a>
</p>
</div>
-<div id="footer">Copyright © 1999-2023 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sat 2023-01-21</div>
+<div id="footer">Copyright © 1999-2023 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Tue 2023-04-04</div>
</div>
</body>
</html>
diff --git a/xalan-j/bugreporting.html b/xalan-j/bugreporting.html
index c3f5638..676344f 100644
--- a/xalan-j/bugreporting.html
+++ b/xalan-j/bugreporting.html
@@ -75,7 +75,7 @@
<a href="http://xalan.apache.org/index.html">Home</a>
</li></ul><hr /><ul>
<li>
-<a href="index.html">Xalan-J 2.7.2</a>
+<a href="index.html">Xalan-J 2.7.3</a>
</li>
<li>
<a href="charter.html">Charter</a>
diff --git a/xalan-j/builds.html b/xalan-j/builds.html
index eab0786..d6a0fc1 100644
--- a/xalan-j/builds.html
+++ b/xalan-j/builds.html
@@ -75,7 +75,7 @@
<a href="http://xalan.apache.org/index.html">Home</a>
</li></ul><hr /><ul>
<li>
-<a href="index.html">Xalan-J 2.7.2</a>
+<a href="index.html">Xalan-J 2.7.3</a>
</li>
<li>
<a href="charter.html">Charter</a>
diff --git a/xalan-j/charter.html b/xalan-j/charter.html
index 7fabb5f..7ef897d 100644
--- a/xalan-j/charter.html
+++ b/xalan-j/charter.html
@@ -75,7 +75,7 @@
<a href="http://xalan.apache.org/index.html">Home</a>
</li></ul><hr /><ul>
<li>
-<a href="index.html">Xalan-J 2.7.2</a>
+<a href="index.html">Xalan-J 2.7.3</a>
</li>
<li>Charter<br />
</li></ul><hr /><ul>
@@ -163,7 +163,7 @@
</p>
<h3>Xalan Project Charter</h3>
<p>The following charter applies to all Xalan projects.</p>
-
+
<p align="right" size="2">
<a href="#content">(top)</a>
@@ -178,14 +178,14 @@
documentation.</p>
<p>1.2 This charter briefly describes the mission, history, organization
and processes of the project.</p>
-
+
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
<h3>2 MISSION</h3>
<p>2.1 Apache Xalan exists to promote the use of XSLT. We view XSLT
- (Extensible Stylesheet Language Transformations) as a compelling
+ (Extensible Stylesheet Language Transformations) as a compelling
paradigm that transforms XML documents, thereby facilitating the
exchange, transformation, and presentation of knowledge. The ability
to transform XML documents into usable information has great potential
@@ -208,12 +208,12 @@
components and other components and applications, standards (formal or
de facto) will be used as much as possible for both protocols and
APIs. Where appropriate, experiences and lessons learned will be fed
- back to standards bodies in an effort to assist in the development of
+ back to standards bodies in an effort to assist in the development of
those standards. We will also encourage the innovation of new
protocols, APIs, and components in order to seed new concepts not
yet defined by standards.</p>
-
-
+
+
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
@@ -222,17 +222,17 @@
Software Foundation in October 2004 to facilitate joint open-source
development. Prior to October 2004 this project was a subproject
of the Apache XML project.</p>
-
-
+
+
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
<h3>4 TERMS</h3>
- <p>4.1 The ASF Board. The management board of the Apache Software
+ <p>4.1 The ASF Board. The management board of the Apache Software
Foundation.</p>
- <p>4.2 The Project. The Apache Xalan project; intended to refer to the
+ <p>4.2 The Project. The Apache Xalan project; intended to refer to the
source code, website, subprojects, and community that are Apache Xalan.</p>
- <p>4.3 Subproject. The Apache Xalan project may have subprojects; a
+ <p>4.3 Subproject. The Apache Xalan project may have subprojects; a
subproject is responsible for a component or application whose scope
is well defined.</p>
<p>4.4 Product. Some deliverable (usually a binary or source package)
@@ -242,30 +242,30 @@
multiple releases of a given product.</p>
<p>4.6 Contributor. Anyone who makes a contribution to the development
of the Apache Xalan project.</p>
- <p>4.7 Committer. The Apache Xalan project has a set of committers.
+ <p>4.7 Committer. The Apache Xalan project has a set of committers.
Committers are contributors who have read/write access to the source
code repository.</p>
<p>4.8 PMC. The PMC (Project Management Committee) is the group of people
- that form the entity that makes decisions and controls the project.
+ that form the entity that makes decisions and controls the project.
Individual people or committers do not control the project.</p>
-
-
+
+
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
<h3>5 THE PROJECT MANAGEMENT COMMITTEE</h3>
- <p>5.1 The Apache Xalan project is managed by a core group of committers
+ <p>5.1 The Apache Xalan project is managed by a core group of committers
known as the Project Management Committee [PMC]. Subprojects, if any,
much each have at least one representative committer on the PMC.</p>
<p>5.2 The activities of the PMC are coordinated by the Chairperson,
who is an officer of the corporation and reports to the Apache
- Board. The Chairperson will, on the request of the Apache Board,
- provide reports to the Board on issues related to the running of
+ Board. The Chairperson will, on the request of the Apache Board,
+ provide reports to the Board on issues related to the running of
the Apache Xalan project.</p>
<p>5.3 The PMC has the following responsibilities:</p>
<p>a) Accepting new subproject proposals, formally submitting these
proposals for Apache Xalan committer vote, and creating the subproject
- (see SUBPROJECTS below). This is done in collaboration with the
+ (see SUBPROJECTS below). This is done in collaboration with the
Incubator (see <a href="http://incubator.apache.org">http://incubator.apache.org</a>).</p>
<p>b) Facilitating code or other donations by individuals or companies,
in collaboration with the Incubator.</p>
@@ -273,24 +273,24 @@
the ASF board.</p>
<p>d) Ensuring that administrative and infrastructure work is completed.</p>
<p>e) Facilitating relationships among projects and subprojects.</p>
- <p>f) Facilitating relationships between the Apache Xalan project and the
+ <p>f) Facilitating relationships between the Apache Xalan project and the
external world.</p>
- <p>g) Overseeing Apache Xalan to ensure that the mission defined in this
+ <p>g) Overseeing Apache Xalan to ensure that the mission defined in this
document is being fulfilled.</p>
<p>h) Resolving conflicts within the project.</p>
<p>i) Reporting to the ASF board (through the Chair) on the progress
of the project.</p>
<p>j) Propose new releases of projects or subprojects. Such proposals pass
- if 75% of the PMC members vote in agreement.</p>
-
+ if 75% of the PMC members vote in agreement.</p>
+
<p>5.4 A contributor can, at any time, nominate a committer to be on the PMC,
- by calling for a vote. If two thirds, or more, of the active committers
+ by calling for a vote. If two thirds, or more, of the active committers
vote in agreement then the nomination is given to the PMC. The person
becomes a new PMC member if 75% or more of the PMC members vote in
agreement, with no dissenting votes among the PMC members. This individual
- should be elected based on merit for the evolution of the project and
+ should be elected based on merit for the evolution of the project and
demonstration of commitment.</p>
- <p>5.5 In cases where the subproject is unable to directly provide a
+ <p>5.5 In cases where the subproject is unable to directly provide a
representative on the PMC, another member of the PMC will be required to
represent that subproject on the PMC. This will be strongly discouraged.
It is preferable that all subprojects have direct representation on the
@@ -304,8 +304,8 @@
if they are not already, be appointed an officer of the corporation. See
<a href="http://www.apache.org/foundation/bylaws.html">
http://www.apache.org/foundation/bylaws.html</a> for more information.</p>
- <p>5.8 The PMC is responsible for maintaining and updating this charter.
- Development must follow the process outlined below, so any change to the
+ <p>5.8 The PMC is responsible for maintaining and updating this charter.
+ Development must follow the process outlined below, so any change to the
development process necessitates a change to the charter. Proposed changes
to this charter by the PMC are passed if 75% or more of the PMC members
approve the proposal, with no dissenting votes. However, an active Apache
@@ -325,15 +325,15 @@
votes among the other PMC members.</p>
<p>5.12 A person remains a PMC member until he or she resigns, is removed by a
vote from among the other PMC members, dies or is incapacitated.</p>
-
+
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
<h3>6 SUBPROJECTS</h3>
- <p>6.1 A subproject of the Apache Xalan project is responsible for a component
- or application whose scope is well defined. Each subproject has its own set
- of developers, and is responsible for approving its own committers. Apache
+ <p>6.1 A subproject of the Apache Xalan project is responsible for a component
+ or application whose scope is well defined. Each subproject has its own set
+ of developers, and is responsible for approving its own committers. Apache
Xalan is composed of subprojects which fit into one of two categories:</p>
<p>(a) An XSLT processor implementation in some particular programming
language. There may be multiple processors for a given language if
@@ -359,8 +359,8 @@
challenge the active committers approve the removal with a two-thirds
majority vote. Any subproject removal is subject to the approval of the
ASF board.</p>
-
-
+
+
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
@@ -369,7 +369,7 @@
meritocracy -- the more work you do, the more you are allowed to do.</p>
<p>7.2 People who make regular and substantial contributions may become
committers as described below. Contributions include: participating in
- mailing lists, reporting issues or bugs in issue-records in the Issue Database,
+ mailing lists, reporting issues or bugs in issue-records in the Issue Database,
providing patches, and proposing changes to a product.</p>
<p>7.3 In order to ensure that all code contained in the Apache Xalan
project's code repository is free of licensing, intellectual property and patent
@@ -378,9 +378,9 @@
<p>a) If contributing as an individual, sign the "Individual
Contributor License Agreement (CLA)"
(<a href="http://www.apache.org/licenses/icla.txt">http://www.apache.org/licenses/icla.txt</a>)
- and file a copy with the Secretary of the Corporation; or </p>
+ and file a copy with the Secretary of the Corporation; or </p>
<p>b) If making the contribution as part of their employment
- responsibilities, sign the "Corporate CLA (CCLA)",
+ responsibilities, sign the "Corporate CLA (CCLA)",
(<a href="http://www.apache.org/licenses/cla-corporate.txt">http://www.apache.org/licenses/cla-corporate.txt</a>)
and file a copy with the Secretary of the Corporation.</p>
<p>7.4 If the contribution in question is a small bugfix, the contributor need
@@ -398,18 +398,18 @@
<p>e) Are you aware of any third-party licenses or other
restrictions (such as related patents or trademarks) that could
apply to your contribution? If so, what are they?</p>
-
-
+
+
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
<h3>8 COMMITTERS</h3>
<p>8.1 The Apache Xalan project has a set of committers. If there
are subprojects, each subproject will also have a set of committers.
- Committers are contributors who have read/write access to the source code
- repository. New committers are added when a contributor is nominated by a
- committer and approved by at least 50 percent of the active committers for
- that subproject with no opposing votes. In most cases, new committers will
+ Committers are contributors who have read/write access to the source code
+ repository. New committers are added when a contributor is nominated by a
+ committer and approved by at least 50 percent of the active committers for
+ that subproject with no opposing votes. In most cases, new committers will
already be participating in the development process by submitting suggestions
and/or fixes via issue-records in the Issue Database or mailing lists.</p>
<p>8.2 For the purposes of voting, committers will be classed as "active" or
@@ -424,8 +424,8 @@
<p>8.4 An inactive status will not prevent a committer committing new code
changes or posting to the mailing lists. Either of these activities will
automatically re-activate the committer for the purposes of voting.</p>
-
-
+
+
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
@@ -440,7 +440,7 @@
documentation and other associated parts that are stored in
the repository. Any subproject will have its set of committers
for its repository.</p>
- <p>c) Website -- The website <a href="http://xalan.apache.org">xalan.apache.org</a>
+ <p>c) Website -- The website <a href="http://xalan.apache.org">xalan.apache.org</a>
will contain information about the Apache Xalan project and its subprojects,
including documentation, downloads of releases, and this charter.</p>
<p>d) Mailing Lists -- appropriate mailing lists will be created
@@ -448,8 +448,8 @@
for example include: a PMC mailing list, a general mailing list,
project or subproject public developer mailing lists,
project or subproject public user mailing lists.</p>
-
-
+
+
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
@@ -463,23 +463,23 @@
it is the responsibility of the committer, in consultation with
the PMC, to conduct due diligence on the pedigree of the
contribution under consideration; see sections 7.3 and 7.4. </p>
-
-
+
+
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
-<h3>11 THE DEVELOPMENT PROCESS</h3>
+<h3>11 THE DEVELOPMENT PROCESS</h3>
<p>11.1 For a committer to commit a change to the MAIN branch of the
repository an issue-record must be opened in the "Issue Database"
to track the change. The status of the issue must be kept up to date.</p>
- <p>11.2 No voting is required to commit changes, but one other active
+ <p>11.2 No voting is required to commit changes, but one other active
committer must review the changes. Before the changes are committed, the reviewer
must add a comment in the corresponding issue-record indicating that
they have reviewed and approve the changes.</p>
<p>11.3 Issue-records and reviews are not required for committing changes to
other experimental branches (not the MAIN branch) in a repository.</p>
-
-
+
+
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
@@ -488,8 +488,8 @@
proposals must be made within two weeks of the proposal. A challenge to
a proposal must also be made within two weeks of the proposal. Likewise,
votes cast on challenges must be cast within two weeks of the challenge.</p>
-
-
+
+
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
@@ -498,7 +498,7 @@
projects, such as Xerces and XML, to avoid redundancy
and achieve a coherent architecture among Apache Xalan and these
projects.</p>
-
+
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
diff --git a/xalan-j/commandline.html b/xalan-j/commandline.html
index fbd0a2e..74a2bac 100644
--- a/xalan-j/commandline.html
+++ b/xalan-j/commandline.html
@@ -75,7 +75,7 @@
<a href="http://xalan.apache.org/index.html">Home</a>
</li></ul><hr /><ul>
<li>
-<a href="index.html">Xalan-J 2.7.2</a>
+<a href="index.html">Xalan-J 2.7.3</a>
</li>
<li>
<a href="charter.html">Charter</a>
diff --git a/xalan-j/commandline_xsltc.html b/xalan-j/commandline_xsltc.html
index 73df6d7..d45ed94 100644
--- a/xalan-j/commandline_xsltc.html
+++ b/xalan-j/commandline_xsltc.html
@@ -75,7 +75,7 @@
<a href="http://xalan.apache.org/index.html">Home</a>
</li></ul><hr /><ul>
<li>
-<a href="index.html">Xalan-J 2.7.2</a>
+<a href="index.html">Xalan-J 2.7.3</a>
</li>
<li>
<a href="charter.html">Charter</a>
diff --git a/xalan-j/contact_us.html b/xalan-j/contact_us.html
index 8c8c091..5c614b7 100644
--- a/xalan-j/contact_us.html
+++ b/xalan-j/contact_us.html
@@ -75,7 +75,7 @@
<a href="http://xalan.apache.org/index.html">Home</a>
</li></ul><hr /><ul>
<li>
-<a href="index.html">Xalan-J 2.7.2</a>
+<a href="index.html">Xalan-J 2.7.3</a>
</li>
<li>
<a href="charter.html">Charter</a>
diff --git a/xalan-j/downloads.html b/xalan-j/downloads.html
index cf4f021..622445b 100644
--- a/xalan-j/downloads.html
+++ b/xalan-j/downloads.html
@@ -75,7 +75,7 @@
<a href="http://xalan.apache.org/index.html">Home</a>
</li></ul><hr /><ul>
<li>
-<a href="index.html">Xalan-J 2.7.2</a>
+<a href="index.html">Xalan-J 2.7.3</a>
</li>
<li>
<a href="charter.html">Charter</a>
@@ -192,37 +192,16 @@
<p> You can download the pre-built binary distributions from one of the
mirror sites at <a href="http://www.apache.org/dyn/closer.cgi/xalan/xalan-j">xalan-j distribution directory</a>.
</p>
-
- <p>Xalan-J has two processors,
- an interpretive one, Xalan Interpretive, and a compiled one, Xalan Compiled (XSLTC).
- Your choice of which binary distribution to download depends on which
- of the processors you want to use.
- There are 2 binary distributions available; you only need to choose one of them.
- Both binary distributions contain <code>xml-apis.jar</code> and <code>xercesImpl.jar</code> from <a href="http://xerces.apache.org/xerces2-j/index.html">Xerces-Java 2.11.0</a>.</p>
- <ul>
- <li>The first binary distribution, <code>xalan-j_2_7_2-bin.zip</code> or
- <code>xalan-j_2_7_2-bin.tar.gz</code>,
- contains the Xalan Interpretive processor, the Xalan Compiled processor (XSLTC) and the
- runtime support packages in a single jar, called <code>xalan.jar</code>.
- The reason to use this distribution would be that you don't know
- which processor you are going to use, or might be using both.
- </li>
-<br />
-<br />
- <li>The second binary distribution, <code>xalan-j_2_7_2-bin-2jars.zip</code> or
- <code>xalan-j_2_7_2-bin-2jars.tar.gz</code>
- contains the Xalan Interpretive processor in <code>xalan.jar</code>, and the Xalan Compiled
- processor (XSLTC) and the runtime support packages in <code>xsltc.jar</code>.
- The reason to using this distribution is that you want more control.
- If you are using just XSLTC you can put <code>xsltc.jar</code> on the classpath
- and not <code>xalan.jar</code>. If you are using just the interpretive processor
- you can put xalan <code>xalan.jar</code> on the classpath and not <code>xsltc.jar</code>. Of course
- you can put both <code>xalan.jar</code> and <code>xsltc.jar</code> from this distribution
- on your classpath if you want to use both.
- </li>
- </ul>
-
+ <p>Xalan-J has two processors,
+ an interpretive one "Xalan Interpretive", and a compiled one "Xalan Compiled (XSLTC)".
+ The Xalan-J binary distribution contain <code>xml-apis.jar</code> and <code>xercesImpl.jar</code> from
+ <a href="http://xerces.apache.org/xerces2-j/index.html">Xerces-Java 2.12.2</a>.</p>
+
+ <p>The Xalan-J binary distribution, <code>xalan-j_2_7_3-bin.zip</code> or <code>xalan-j_2_7_3-bin.tar.gz</code>,
+ contains the Xalan Interpretive processor, the Xalan Compiled processor (XSLTC) and the
+ runtime support packages in a single jar, called <code>xalan.jar</code>.</p>
+
<p>
We provide two distributions: a binary distribution, and a source distribution.
You can also download a source distribution from one of the same
@@ -232,7 +211,7 @@
</p>
<p>To use Xalan-Java, you need the following which are available from
- either a binary or source distribution:</p>
+ either a binary or source distribution:</p>
<ul>
<li>
<code>xml-apis.jar</code> JAXP APIs</li>
@@ -242,44 +221,42 @@
<code>xalan.jar</code>
</li>
<li>
-<code>xsltc.jar</code> the XSLTC processor, if you choose a 2jars distribution</li>
- <li>
<code>serializer.jar</code> which are the serializer classes of
Xalan-Java</li>
</ul>
- <p>
- If you have downloaded a binary distribution, you already have a build
+ <p>
+ If you have downloaded a binary distribution, you already have a build
(you have the jars). This is also true for a source distribution, however
- if you downloaded a source distribution,
- you have the option to use Ant to build Xalan-Java,
+ if you downloaded a source distribution,
+ you have the option to use Ant to build Xalan-Java,
including <code>xalan.jar</code>, <code>xsltc.jar</code>, <code>serializer.jar</code>
and other things, see <a href="#using-ant">Using Ant</a> for more
details.
- </p>
-
-
+ </p>
+
+
<a name="download"></a>
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
<h3>Downloading what else you might need</h3>
- <p>To use Xalan-Java, you need the following:</p>
+ <p>To use Xalan-Java, you need the following:</p>
<ul>
<li>The JDK or JRE 1.3.x, 1.4.x, or 5.x</li>
</ul>
<p>
You can get the JDK or JRE from <a href="http://www-128.ibm.com/developerworks/java/jdk/index.html">
IBM developerWorks</a> or <a href="http://www.java.sun.com">java.sun.com</a>.
- </p>
- <p>If you plan to run <a href="extensions.html">XSLT extensions</a>
+ </p>
+ <p>If you plan to run <a href="extensions.html">XSLT extensions</a>
through extension functions or elements, and you want to implement
that support in languages
other than Java, then you will need an implementation of the Bean Scripting Framework (BSF).
- An open source implementation is available for download from Apache. See the
+ An open source implementation is available for download from Apache. See the
<a href="http://jakarta.apache.org/bsf/index.html">Apache Jakarta
- BSF project</a>. If you plan to run XSLT extensions implemented in scripting
- languages, you will need <code>bsf.jar</code> and one or more additional files as indicated in
+ BSF project</a>. If you plan to run XSLT extensions implemented in scripting
+ languages, you will need <code>bsf.jar</code> and one or more additional files as indicated in
<a href="extensions.html#supported-lang">extensions language requirements</a>.
</p>
@@ -306,16 +283,16 @@
</td>
<td class="noteTxt">
You can use Xalan-Java with other XML parsers that implement
- the <a href="https://jaxp.java.net/">Java API for XML Processing (JAXP) 1.3</a>.
+ the <a href="https://jaxp.java.net/">Java API for XML Processing (JAXP) 1.3</a>.
See <a href="usagepatterns.html#plug">Plugging in the Transformer and XML parser</a>.
</td>
</tr>
</table>
<p>
- The Xalan-Java download includes <code>xercesImpl.jar</code> from Xerces-Java 2.11.0. In conjunction with <code>xml-apis.jar</code>,
- this is all you need to run Xalan-Java with the Xerces-Java XML parser. You can, however, download the
+ The Xalan-Java download includes <code>xercesImpl.jar</code> from Xerces-Java 2.11.0. In conjunction with <code>xml-apis.jar</code>,
+ this is all you need to run Xalan-Java with the Xerces-Java XML parser. You can, however, download the
complete Xerces-Java binary or source distribution from the <a href="http://www.apache.org/dyn/closer.cgi/xerces/j/">xerces-j distribution directory</a>.
- If you cannot find Xerces-Java 2.11.0 at that location, have a look at the
+ If you cannot find Xerces-Java 2.11.0 at that location, have a look at the
<a href="http://archive.apache.org/dist/xml/xerces-j/">Apache archive location for
Xerces Java</a>.
</p>
@@ -325,11 +302,11 @@
<img src="resources/note.gif" alt="note" />
</td>
<td class="noteTxt">
- If you plan to use a different XML parser, see <a href="usagepatterns.html#plug">Plugging
+ If you plan to use a different XML parser, see <a href="usagepatterns.html#plug">Plugging
in a Transformer and XML parser</a>.
</td>
</tr>
-</table>
+</table>
<a name="viewcode"></a>
@@ -342,11 +319,11 @@
whole project you can view it at
<a href="http://svn.apache.org/viewvc/xalan/">http://svn.apache.org/viewvc/xalan/</a>
or at
- <a href="http://svn.apache.org/repos/asf/xalan/">http://svn.apache.org/repos/asf/xalan/</a>.
+ <a href="http://svn.apache.org/repos/asf/xalan/">http://svn.apache.org/repos/asf/xalan/</a>.
The link with "viewvc" in it is slightly prettier.
</p>
<p>
- The java/trunk and test/trunk subdirectories are the ones with the latest development code.
+ The java/trunk and test/trunk subdirectories are the ones with the latest development code.
</p>
@@ -361,7 +338,7 @@
using subversion, this section may be of interest to you.
</p>
<p>
- If you wish to download Xalan and build it yourself, perhaps because you want to
+ If you wish to download Xalan and build it yourself, perhaps because you want to
apply a patch and test it, you will need a subversion client and anonymous access
to the repository.
Don't worry, everyone has anonymous access.
@@ -369,10 +346,10 @@
operating systems here:
<a href="http://subversion.tigris.org/project_packages.html#binary-packages">
http://subversion.tigris.org/project_packages.html#binary-packages</a>.
- See
+ See
<a href="http://www.apache.org/dev/version-control.html">
http://www.apache.org/dev/version-control.html
- </a> for more information on Apache and subversion.
+ </a> for more information on Apache and subversion.
</p>
<p>
Once the subverion client is installed on your local machine you
@@ -380,22 +357,22 @@
to get the latest Xalan-J using a command line something like this:
<blockquote class="source">
<pre>
- svn checkout http://svn.apache.org/repos/asf/xalan/java/trunk java
+ svn checkout http://svn.apache.org/repos/asf/xalan/java/trunk java
</pre>
</blockquote>
where the argument after <b>checkout</b> is the Subversion repository location,
in this case the location of the latest development code, and the last argument,
in this case <b>java</b> is the location of the local directory that the repository is
- copied to.
+ copied to.
</p>
<p>
Similarly for the test harness, you can download the latest test harness with a Subversion command
something like this:
<blockquote class="source">
<pre>
- svn checkout http://svn.apache.org/repos/asf/xalan/test/trunk test
+ svn checkout http://svn.apache.org/repos/asf/xalan/test/trunk test
</pre>
-</blockquote>
+</blockquote>
</p>
<p>
Those two commands will put a copy of the latest parts in the local
@@ -409,7 +386,7 @@
<blockquote class="source">
<pre>
build clean
- build
+ build
</pre>
</blockquote>
</p>
@@ -430,7 +407,7 @@
</blockquote>
The first target, <b>jar</b> builds the test harness and only needs to be done
once after the <b>test</b> repository is checked out. The second target, <b>smoketest</b>,
- runs the Xalan-J intepretive smoketest.
+ runs the Xalan-J intepretive smoketest.
Running the <b>build smoketest</b> or other targets in the <b>test</b> directory
automatically looks for the jars in the directory <b>../java/build</b>
and that is why it is easiest to download the projects into suggested sibling
@@ -458,7 +435,7 @@
BUILD SUCCESSFUL
Total time: 2 minutes 4 seconds
-build completed!
+build completed!
</pre>
</blockquote>
</p>
@@ -466,7 +443,7 @@
Don't be fooled by the <b>BUILD SUCCESSFUL</b> messages, look for the two CONGRATULATIONS!
messages. If you run the smoketest for XSLTC with <b>build smoketest.xsltc</b> you wil
only get one CONGRATULATIONS! message if all goes well.
- </p>
+ </p>
<a name="using-ant"></a>
@@ -478,11 +455,11 @@
If you have downloaded a source distribution, or obtained source code
using subversion, this section may be of interest to you.
</p>
-
+
<p>Apache <a href="http://jakarta.apache.org/ant/index.html">Ant</a> is a flexible, powerful, and easy-to-use Java build tool that we include with the
- Xalan-Java distribution. The Ant JAR file is in the tools directory, and the cross-platform XML build file (build.xml) is in
- the root directory along with a Windows32 batch file (build.bat) and a UNIX shell file (build.sh). The build file defines
- the "targets" that you can use Ant to build. The batch and shell files set up the classpath and launch Ant with the target
+ Xalan-Java distribution. The Ant JAR file is in the tools directory, and the cross-platform XML build file (build.xml) is in
+ the root directory along with a Windows32 batch file (build.bat) and a UNIX shell file (build.sh). The build file defines
+ the "targets" that you can use Ant to build. The batch and shell files set up the classpath and launch Ant with the target
(and any other arguments) you provide.</p>
<p>
<b>Instructions for using Ant</b>
@@ -494,21 +471,21 @@
bin directory on the classpath.<br />
<br />
</li>
- <li>Depending on your environment, run the batch file (build.bat) or shell file (build.sh)
+ <li>Depending on your environment, run the batch file (build.bat) or shell file (build.sh)
from the Xalan-Java root directory, optionally with arguments (see the table of targets below).<br />
<br />
- The batch/shell file adds several JAR files to the classpath and launches Ant with any arguments
- you provide. If you provide no target, Ant compiles the source files and rebuilds <code>xalan.jar</code>
+ The batch/shell file adds several JAR files to the classpath and launches Ant with any arguments
+ you provide. If you provide no target, Ant compiles the source files and rebuilds <code>xalan.jar</code>
(the "jar" target).</li>
</ol>
-
+
<p>The Xalan-Java source code tree is in the src directory.
</p>
<p>
- If you are using Ant, the target is jar (the default).
+ If you are using Ant, the target is jar (the default).
</p>
-
- <p>You can also set up your classpath manually (see build.bat or build.sh for the details), and
+
+ <p>You can also set up your classpath manually (see build.bat or build.sh for the details), and
then run Ant as follows:<br />
<br />
<code>java org.apache.tools.ant.Main <b>
@@ -568,7 +545,7 @@
<tr>
<td class="content" rowspan="1" colspan="1">clean</td>
<td class="content" rowspan="1" colspan="1">purges the build and distribution</td>
-</tr>
+</tr>
</table>
<p>If you build a target that depends on other targets, Ant creates those other targets in the correct order.
</p>
@@ -594,7 +571,7 @@
<h3>Rebuilding a sample application</h3>
<p>If you modify a sample and want to recompile it, you can run the Java compiler in the directory containing the
example. Be sure <code>xalan.jar</code>, <code>serializer.jar</code>, <code>xml-apis.jar</code>, and <code>xercesImpl.jar</code> are on the classpath. </p>
- <p>To recompile and run the class files in the servlet subdirectory, the javax.servlet and
+ <p>To recompile and run the class files in the servlet subdirectory, the javax.servlet and
javax.servlet.http packages must also be on the classpath. These packages are available via
the <code>servlet.jar</code> file found in Apache Tomcat ( see <a href="http://tomcat.apache.org/">The Jakarta Site - Apache Tomcat</a> ).</p>
<p>After recompiling a sample, you can use the jar utility to place your new .class files in
diff --git a/xalan-j/dtm.html b/xalan-j/dtm.html
index 5cf815f..7814193 100644
--- a/xalan-j/dtm.html
+++ b/xalan-j/dtm.html
@@ -75,7 +75,7 @@
<a href="http://xalan.apache.org/index.html">Home</a>
</li></ul><hr /><ul>
<li>
-<a href="index.html">Xalan-J 2.7.2</a>
+<a href="index.html">Xalan-J 2.7.3</a>
</li>
<li>
<a href="charter.html">Charter</a>
diff --git a/xalan-j/extensions.html b/xalan-j/extensions.html
index 4f965db..15b4b1b 100644
--- a/xalan-j/extensions.html
+++ b/xalan-j/extensions.html
@@ -75,7 +75,7 @@
<a href="http://xalan.apache.org/index.html">Home</a>
</li></ul><hr /><ul>
<li>
-<a href="index.html">Xalan-J 2.7.2</a>
+<a href="index.html">Xalan-J 2.7.3</a>
</li>
<li>
<a href="charter.html">Charter</a>
diff --git a/xalan-j/extensions_xsltc.html b/xalan-j/extensions_xsltc.html
index ad5f31c..8a44217 100644
--- a/xalan-j/extensions_xsltc.html
+++ b/xalan-j/extensions_xsltc.html
@@ -75,7 +75,7 @@
<a href="http://xalan.apache.org/index.html">Home</a>
</li></ul><hr /><ul>
<li>
-<a href="index.html">Xalan-J 2.7.2</a>
+<a href="index.html">Xalan-J 2.7.3</a>
</li>
<li>
<a href="charter.html">Charter</a>
diff --git a/xalan-j/extensionslib.html b/xalan-j/extensionslib.html
index c21b7c3..0c46913 100644
--- a/xalan-j/extensionslib.html
+++ b/xalan-j/extensionslib.html
@@ -75,7 +75,7 @@
<a href="http://xalan.apache.org/index.html">Home</a>
</li></ul><hr /><ul>
<li>
-<a href="index.html">Xalan-J 2.7.2</a>
+<a href="index.html">Xalan-J 2.7.3</a>
</li>
<li>
<a href="charter.html">Charter</a>
diff --git a/xalan-j/faq.html b/xalan-j/faq.html
index fc5d256..1a926fd 100644
--- a/xalan-j/faq.html
+++ b/xalan-j/faq.html
@@ -75,7 +75,7 @@
<a href="http://xalan.apache.org/index.html">Home</a>
</li></ul><hr /><ul>
<li>
-<a href="index.html">Xalan-J 2.7.2</a>
+<a href="index.html">Xalan-J 2.7.3</a>
</li>
<li>
<a href="charter.html">Charter</a>
diff --git a/xalan-j/features.html b/xalan-j/features.html
index 0c29cee..ba6a4e3 100644
--- a/xalan-j/features.html
+++ b/xalan-j/features.html
@@ -75,7 +75,7 @@
<a href="http://xalan.apache.org/index.html">Home</a>
</li></ul><hr /><ul>
<li>
-<a href="index.html">Xalan-J 2.7.2</a>
+<a href="index.html">Xalan-J 2.7.3</a>
</li>
<li>
<a href="charter.html">Charter</a>
diff --git a/xalan-j/getstarted.html b/xalan-j/getstarted.html
index cd38993..45d295b 100644
--- a/xalan-j/getstarted.html
+++ b/xalan-j/getstarted.html
@@ -75,7 +75,7 @@
<a href="http://xalan.apache.org/index.html">Home</a>
</li></ul><hr /><ul>
<li>
-<a href="index.html">Xalan-J 2.7.2</a>
+<a href="index.html">Xalan-J 2.7.3</a>
</li>
<li>
<a href="charter.html">Charter</a>
diff --git a/xalan-j/history.html b/xalan-j/history.html
index 8fead4b..a73e0f3 100644
--- a/xalan-j/history.html
+++ b/xalan-j/history.html
@@ -75,7 +75,7 @@
<a href="http://xalan.apache.org/index.html">Home</a>
</li></ul><hr /><ul>
<li>
-<a href="index.html">Xalan-J 2.7.2</a>
+<a href="index.html">Xalan-J 2.7.3</a>
</li>
<li>
<a href="charter.html">Charter</a>
diff --git a/xalan-j/index.html b/xalan-j/index.html
index b74ba7c..5236603 100644
--- a/xalan-j/index.html
+++ b/xalan-j/index.html
@@ -2,7 +2,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html>
<head>
-<title>ASF: Xalan-Java Version 2.7.2</title>
+<title>ASF: Xalan-Java</title>
<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<link rel="stylesheet" type="text/css" href="resources/apache-xalan.css" />
@@ -39,7 +39,7 @@
</th>
</tr>
<tr>
-<td valign="middle">Xalan-Java Version 2.7.2</td>
+<td valign="middle">Xalan-Java Version 2.7.3</td>
</tr>
</tbody>
</table>
@@ -74,7 +74,7 @@
<li>
<a href="http://xalan.apache.org/index.html">Home</a>
</li></ul><hr /><ul>
-<li>Xalan-J 2.7.2<br />
+<li>Xalan-J 2.7.3<br />
</li>
<li>
<a href="charter.html">Charter</a>
@@ -157,7 +157,7 @@
</ul>
</div>
<div id="content">
-<h2>Xalan-Java Version 2.7.2</h2>
+<h2>Xalan-Java Version 2.7.3</h2>
<ul>
<li>
<a href="#whatisit">What is it?</a>
@@ -167,36 +167,36 @@
</li>
<li>
<a href="#moreinfo">For more information...</a>
-</li>
+</li>
<li>
<a href="#license">Apache License Version 2.0</a>
-</li>
+</li>
<li>
<a href="#notice">Notice file</a>
-</li>
+</li>
<li>
<a href="#license1.1">Apache License Version 1.1</a>
</li>
</ul>
-
+
<a name="whatisit"></a>
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
<h3>What is it?</h3>
- <p>Xalan-Java is an XSLT processor for transforming XML documents into
- HTML, text, or other XML document types. It implements <a href="http://www.w3.org/TR/xslt">XSL Transformations (XSLT) Version 1.0</a> and
- <a href="http://www.w3.org/TR/xpath">XML Path Language (XPath) Version 1.0</a> and can be used from the command line, in an applet or a
+ <p>Xalan-Java is an XSLT processor for transforming XML documents into
+ HTML, text, or other XML document types. It implements <a href="http://www.w3.org/TR/xslt">XSL Transformations (XSLT) Version 1.0</a> and
+ <a href="http://www.w3.org/TR/xpath">XML Path Language (XPath) Version 1.0</a> and can be used from the command line, in an applet or a
servlet, or as a module in other program.</p>
- <p>Xalan-Java implements the javax.xml.transform interface in
+ <p>Xalan-Java implements the javax.xml.transform interface in
<a href="https://jaxp.java.net/">Java API for XML Processing (JAXP) 1.3</a>. This interface provides a modular
- framework and a standard API for performing XML transformations, and utilizes system
+ framework and a standard API for performing XML transformations, and utilizes system
properties to determine which Transformer and which XML parser to use.</p>
- <p>Xalan-Java also implements the javax.xml.xpath interface in JAXP 1.3, which provides an
- object-model neutral API for evaluation of XPath expressions and access to the evaluation
+ <p>Xalan-Java also implements the javax.xml.xpath interface in JAXP 1.3, which provides an
+ object-model neutral API for evaluation of XPath expressions and access to the evaluation
environment.</p>
<p>Xalan-Java also builds on <a href="http://sax.sourceforge.net/">SAX 2</a> and <a href="http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/">DOM level 3</a>.</p>
-
+
<p>For more information, see <a href="readme.html">the release notes</a>.</p>
<table class="note">
<tr>
@@ -213,20 +213,20 @@
<a href="#content">(top)</a>
</p>
<h3>How about this release?</h3>
- <p>This release includes new features as well as a number of bug fixes. See the
- <a href="whatsnew.html">What's New</a> and <a href="readme.html#done">Release
+ <p>This release includes new features as well as a number of bug fixes. See the
+ <a href="whatsnew.html">What's New</a> and <a href="readme.html#done">Release
Notes</a> for more details.</p>
- <p>Xalan-Java Version 2.7.2 works with Xerces-Java, and the distribution includes xercesImpl.jar from Xerces-Java 2.11.0.</p>
- <p>The Xalan-Java implementation is in xalan.jar and serializer.jar.
+ <p>Xalan-Java Version 2.7.3 works with Xerces-Java, and the distribution includes xercesImpl.jar from Xerces-Java 2.12.2.</p>
+ <p>The Xalan-Java implementation is in xalan.jar and serializer.jar.
The SAX, DOM, and JAXP 1.3 interfaces are in xml-apis.jar.</p>
-<a name="moreinfo"></a>
+<a name="moreinfo"></a>
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
<h3>For more information...</h3>
- <p>For more information, go to <a href="overview.html">Xalan-Java Overview</a>,
+ <p>For more information, go to <a href="overview.html">Xalan-Java Overview</a>,
<a href="downloads.html">Xalan-Java Downloads</a>, <a href="getstarted.html">Getting Started
with Interpretive Processing</a> and <a href="xsltc_usage.html">Getting Started with XSLTC</a>.
All of the Xalan-Java documentation on this website is included in the Xalan-Java download, as are a number of
@@ -238,12 +238,12 @@
<a href="#content">(top)</a>
</p>
<h3>Apache License Version 2.0</h3>
-<p>The Apache Software License Version 2.0 applies to all releases of Xalan-Java starting with
+<p>The Apache Software License Version 2.0 applies to all releases of Xalan-Java starting with
Version 2.6.0. A copy of this license is included in the distribution.</p>
<blockquote class="source">
<pre>
-
-
+
+
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
@@ -447,7 +447,7 @@
limitations under the License.
</pre>
-</blockquote>
+</blockquote>
<a name="notice"></a>
@@ -468,12 +468,12 @@
The Apache Software Foundation (http://www.apache.org/).
Portions of this software was originally based on the following:
-
+
- software copyright (c) 1999-2002, Lotus Development Corporation., http://www.lotus.com.
- software copyright (c) 2001-2002, Sun Microsystems., http://www.sun.com.
- software copyright (c) 2003, IBM Corporation., http://www.ibm.com.
- - voluntary contributions made by Ovidiu Predescu (ovidiu@cup.hp.com) on behalf of the
- Apache Software Foundation and was originally developed at Hewlett Packard Company.
+ - voluntary contributions made by Ovidiu Predescu (ovidiu@cup.hp.com) on behalf of the
+ Apache Software Foundation and was originally developed at Hewlett Packard Company.
</pre>
</blockquote>
@@ -489,7 +489,7 @@
/*
* The Apache Software License, Version 1.1
*
- * Copyright (c) 1999-2003 The Apache Software Foundation. All rights
+ * Copyright (c) 1999-2003 The Apache Software Foundation. All rights
* reserved.
*
* Redistribution and use in source and binary forms, with or without
@@ -497,7 +497,7 @@
* are met:
*
* 1. Redistributions of source code must retain the above copyright
- * notice, this list of conditions and the following disclaimer.
+ * notice, this list of conditions and the following disclaimer.
*
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in
@@ -505,7 +505,7 @@
* distribution.
*
* 3. The end-user documentation included with the redistribution,
- * if any, must include the following acknowledgment:
+ * if any, must include the following acknowledgment:
* "This product includes software developed by the
* Apache Software Foundation (http://www.apache.org/)."
* Alternately, this acknowledgment may appear in the software itself,
@@ -513,7 +513,7 @@
*
* 4. The names "Xalan" and "Apache Software Foundation" must
* not be used to endorse or promote products derived from this
- * software without prior written permission. For written
+ * software without prior written permission. For written
* permission, please contact apache@apache.org.
*
* 5. Products derived from this software may not be called "Apache",
@@ -549,15 +549,15 @@
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
-<h3>Other licenses</h3>
- <p>For the licences that apply to the JARs other than xalan.jar, see the licenses and
+<h3>Other licenses</h3>
+ <p>For the licences that apply to the JARs other than xalan.jar, see the licenses and
associated readme files in the root directory of this distribution.</p>
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
</div>
-<div id="footer">Copyright © 1999-2014 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Thu 2014-05-15</div>
+<div id="footer">Copyright © 1999-2023 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Tue 2023-04-04</div>
</div>
</body>
</html>
diff --git a/xalan-j/overview.html b/xalan-j/overview.html
index caa6cc4..ba4210e 100644
--- a/xalan-j/overview.html
+++ b/xalan-j/overview.html
@@ -75,7 +75,7 @@
<a href="http://xalan.apache.org/index.html">Home</a>
</li></ul><hr /><ul>
<li>
-<a href="index.html">Xalan-J 2.7.2</a>
+<a href="index.html">Xalan-J 2.7.3</a>
</li>
<li>
<a href="charter.html">Charter</a>
@@ -180,23 +180,23 @@
<a href="#content">(top)</a>
</p>
<h3>Introduction</h3>
-<p>Xalan-Java fully implements <a href="http://www.w3.org/TR/xslt">XSL Transformations (XSLT) Version 1.0</a>
- and the <a href="http://www.w3.org/TR/xpath">XML Path Language (XPath) Version 1.0</a>. XSLT is the first part of the XSL stylesheet language for
- XML. It includes the XSL Transformation vocabulary and XPath, a language for addressing parts of
- XML documents. For links to background materials, discussion groups, frequently asked questions,
- and tutorials on XSLT, see <a href="#uptospeed">Getting up to speed with XSLT</a>.</p>
+<p>Xalan-Java fully implements <a href="https://www.w3.org/TR/1999/REC-xslt-19991116">XSL Transformations (XSLT) Version 1.0</a>
+ and the <a href="https://www.w3.org/TR/1999/REC-xpath-19991116">XML Path Language (XPath) Version 1.0</a>. XSLT is the first
+ part of the XSL stylesheet language for XML. It includes the XSL Transformation vocabulary and XPath, a language for
+ addressing parts of XML documents. For links to background materials, discussion groups, frequently asked questions,
+ and tutorials on XSLT, see <a href="#uptospeed">Getting up to speed with XSLT</a>.</p>
<table class="note">
<tr>
<td class="noteImg">
<img src="resources/note.gif" alt="note" />
</td>
-<td class="noteTxt">XSL also includes a vocabulary for formatting documents, which is not part of Xalan-Java.
- For more information, see <a href="http://www.w3.org/TR/xsl">Extensible Stylesheet Language (XSL) Version 1.0</a> and the <a href="http://xmlgraphics.apache.org/fop">Apache XmlGraphics FOP (Formatting Objects Project)</a>.</td>
+<td class="noteTxt">XSL also includes a vocabulary for formatting documents, which is not part of Xalan-Java.
+ For more information, see <a href="http://www.w3.org/TR/xsl">Extensible Stylesheet Language (XSL) Version 1.1</a> and the <a href="http://xmlgraphics.apache.org/fop">Apache XmlGraphics FOP (Formatting Objects Project)</a>.</td>
</tr>
</table>
-<p>XSL stylesheets are written in the XSLT language. An XSL stylesheet contains instructions
+<p>XSL stylesheets are written in the XSLT language. An XSL stylesheet contains instructions
for transforming XML documents into XML, HTML, XHTML or plain text. In structural terms, an XSL
- stylesheet specifies the transformation of one tree of
+ stylesheet specifies the transformation of one tree of
nodes (the XML input) into another tree of nodes (the output or transformation result).</p>
<table class="note">
<tr>
@@ -205,7 +205,7 @@
</td>
<td class="noteTxt">The XSL stylesheet may generate and refer to cascading style sheets (<a href="http://www.w3.org/Style/CSS/">CSS</a>) as part of its output.</td>
</tr>
-</table>
+</table>
<p>In the following example, the foo.xsl stylesheet is used to transform foo.xml into foo.out:</p>
<p>foo.xml:</p>
<blockquote class="source">
@@ -214,7 +214,7 @@
</blockquote>
<p>foo.xsl:</p>
<blockquote class="source">
-<pre><?xml version="1.0"?>
+<pre><?xml version="1.0"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:template match="doc">
<out><xsl:value-of select="."/></out>
@@ -225,12 +225,12 @@
<blockquote class="source">
<pre><out>Hello</out></pre>
</blockquote>
-<p>By default, Xalan-Java uses Xerces-Java, but it may be configured with system properties to work with
- other XML parsers (see <a href="usagepatterns.html#plug">Plugging in a Transformer and
- XML parser</a>). The input may be submitted in the form of a stream of XML markup (from a URI,
+<p>By default, Xalan-Java uses Xerces-Java, but it may be configured with system properties to work with
+ other XML parsers (see <a href="usagepatterns.html#plug">Plugging in a Transformer and
+ XML parser</a>). The input may be submitted in the form of a stream of XML markup (from a URI,
a character or byte stream, or another transformation), a SAX InputStream, or a DOM Node.</p>
-<p>Xalan-Java performs the transformations specified in the XSL stylesheet and packages a sequence of
- SAX events that may be serialized to an output stream or writer, used to build a DOM tree, or
+<p>Xalan-Java performs the transformations specified in the XSL stylesheet and packages a sequence of
+ SAX events that may be serialized to an output stream or writer, used to build a DOM tree, or
forwarded as input to another transformation.</p>
@@ -239,16 +239,16 @@
<a href="#content">(top)</a>
</p>
<h3>Xalan-Java Features</h3>
-<ul>
- <li>Includes an Interpretive processor for use in a tooling and debugging environment and
+<ul>
+ <li>Includes an Interpretive processor for use in a tooling and debugging environment and
a Compiling processor (XSLTC) for use in a high performance runtime environment.<br />
<br />
</li>
- <li>Implements the relevant W3C specifications: <a href="http://www.w3.org/TR/xslt">XSL Transformations (XSLT) Version 1.0</a> and
+ <li>Implements the relevant W3C specifications: <a href="http://www.w3.org/TR/xslt">XSL Transformations (XSLT) Version 1.0</a> and
<a href="http://www.w3.org/TR/xpath">XML Path Language (XPath) Version 1.0</a>.<br />
<br />
</li>
- <li>Implements <a href="https://jaxp.java.net/">Java API for XML Processing (JAXP) 1.3</a>, and builds on
+ <li>Implements <a href="https://jaxp.java.net/">Java API for XML Processing (JAXP) 1.3</a>, and builds on
<a href="http://sax.sourceforge.net/">SAX 2</a> and <a href="http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/">DOM level 3</a>.<br />
<br />
</li>
@@ -256,7 +256,7 @@
<br />
</li>
<li>May be configured to work with any XML parser, such as
- <a href="http://xml.apache.org/xerces-j/index.html">Xerces-Java</a>, that implements
+ <a href="http://xml.apache.org/xerces-j/index.html">Xerces-Java</a>, that implements
<a href="https://jaxp.java.net/">JAXP 1.3</a> (see <a href="usagepatterns.html#plug">Plugging in an XML
parser</a>).<br />
<br />
@@ -275,13 +275,13 @@
<li>Includes an <a href="usagepatterns.html#applet">applet wrapper</a>.<br />
<br />
</li>
- <li>May be used in a <a href="samples.html#servlet">servlet</a> to transform XML documents
+ <li>May be used in a <a href="samples.html#servlet">servlet</a> to transform XML documents
into HTML and serve the results to clients.<br />
<br />
</li>
- <li>Supports the creation of <a href="extensions.html">Java and scripting language extensions</a>.
+ <li>Supports the creation of <a href="extensions.html">Java and scripting language extensions</a>.
and provides a growing library of extension elements and functions.</li>
-</ul>
+</ul>
<a name="towork"></a>
@@ -292,7 +292,7 @@
<p>For instructions and some suggestions about how to get started using the XSLT Interpretive
processor, see <a href="getstarted.html">Getting Started with Interpretive Processing</a>.</p>
<p>For instructions and some suggestions about how to get started using the XSLT Compiling
- processor, see <a href="xsltc_usage.html">Getting Started with XSLTC</a>.</p>
+ processor, see <a href="xsltc_usage.html">Getting Started with XSLTC</a>.</p>
<a name="uptospeed"></a>
@@ -300,16 +300,16 @@
<a href="#content">(top)</a>
</p>
<h3>Getting up to speed with XSLT</h3>
-<p>If you are still working through the details of the XSLT spec (the W3C 1.0 Recommendation), you
+<p>If you are still working through the details of the XSLT spec (the W3C 1.0 Recommendation), you
may want to consult one or more of the following:</p>
<ul>
- <li>XSLT - XSL Transformations in
+ <li>XSLT - XSL Transformations in
<a href="http://www.brics.dk/~amoeller/XML/">
- The XML Revolution: Technologies for the future Web</a> by Anders Møller and Michael
+ The XML Revolution: Technologies for the future Web</a> by Anders Møller and Michael
I. Schwartzbach (Web pages, but designed for sequential reading)<br />
<br />
</li>
- <li>Crane Softwright's <a href="http://www.CraneSoftwrights.com/training/">Free preview of
+ <li>Crane Softwright's <a href="http://www.CraneSoftwrights.com/training/">Free preview of
Practical Transformation Using XSLT and XPath</a>
<br />
<br />
@@ -317,26 +317,26 @@
<li>Doug Tidwell's <a href="http://www.oreilly.com/catalog/xslt/">XSLT</a>, O'Reilly, 2001
<br />
<br />
-</li>
- <li>Bob Ducharme's <a href="http://www.manning.com/ducharme/index.html">XSLT Quickly</a>,
+</li>
+ <li>Bob Ducharme's <a href="http://www.manning.com/ducharme/index.html">XSLT Quickly</a>,
Manning Publications, 2001<br />
<br />
-</li>
- <li>John Robert Gardner and Zarella Rendon's
- <a href="http://vig.prenhall.com/catalog/academic/product/1,4096,0130404462,00.html">XSLT
+</li>
+ <li>John Robert Gardner and Zarella Rendon's
+ <a href="http://vig.prenhall.com/catalog/academic/product/1,4096,0130404462,00.html">XSLT
and XPath: A Guide to Transformations</a>, Prentice-Hall, 2001<br />
<br />
-</li>
- <li>Michael Kay's <a href="http://www.wrox.com/books/0764543814.shtml">XSLT
+</li>
+ <li>Michael Kay's <a href="http://www.wrox.com/books/0764543814.shtml">XSLT
Programmer's Reference</a>, 2nd ed., Wrox Press, 2001<br />
<br />
-</li>
+</li>
- <li>Dave Pawson's <a href="http://www.dpawson.co.uk/xsl/">XSL Frequently Asked Questions</a> to search out particular answers and
+ <li>Dave Pawson's <a href="http://www.dpawson.co.uk/xsl/">XSL Frequently Asked Questions</a> to search out particular answers and
techniques<br />
<br />
</li>
- <li>Miloslav Nic's <a href="http://zvon.vscht.cz/HTMLonly/XSLTutorial/Books/Book1/index.html">XSL
+ <li>Miloslav Nic's <a href="http://zvon.vscht.cz/HTMLonly/XSLTutorial/Books/Book1/index.html">XSL
Tutorial</a>, a collection of stylesheet examples<br />
<br />
</li>
@@ -345,26 +345,26 @@
<br />
<br />
</li>
- <li>The Mulberry <a href="http://www.mulberrytech.com/xsl/xsl-list/">XSL-List -- Open Forum on
+ <li>The Mulberry <a href="http://www.mulberrytech.com/xsl/xsl-list/">XSL-List -- Open Forum on
XSL</a> (of interest to XSL users at all levels)<br />
<br />
</li>
<li>Objects by Design's <a href="http://www.objectsbydesign.com/projects/xmi_to_html.html">
- Transforming XMI to HTML</a> (oriented towards XMI, "an XML-based, stream representation
- of a UML model," but also covers "generic" XML transformations) and their related
+ Transforming XMI to HTML</a> (oriented towards XMI, "an XML-based, stream representation
+ of a UML model," but also covers "generic" XML transformations) and their related
<a href="http://objectsbydesign.com/projects/xslt/xslt_by_example.html">XSLT by Example</a>
<br />
<br />
-</li>
- <li>OASIS (the Organization for the Advancement of Structured Information Standards):
- <a href="http://www.oasis-open.org/cover/xsl.html">Extensible Stylesheet Language (XSL)</a>
+</li>
+ <li>OASIS (the Organization for the Advancement of Structured Information Standards):
+ <a href="http://www.oasis-open.org/cover/xsl.html">Extensible Stylesheet Language (XSL)</a>
by Robin Cover<br />
<br />
-</li>
+</li>
</ul>
-<p>When you come across other useful introductory or background materials, please email
+<p>When you come across other useful introductory or background materials, please email
<a href="mailto:dev@xalan.apache.org">Xalan Development Mailing List</a>, so we can add them to this list.</p>
-
+
<a name="glossary"></a>
<p align="right" size="2">
<a href="#content">(top)</a>
@@ -374,68 +374,64 @@
<p class="label">
<em>XSLT Namespace</em>
</p>
- <blockquote class="item">The <a href="http://www.w3.org/TR/REC-xml-names/">XML namespace</a> for XSLT. An XML
- namespace is a collection of element and attribute names, identified by a Unique Resource
- Identifier (URI), which often takes the form of a URL, but is really just a unique string,
- not a pointer to a web page. The XSLT namespace URI is http://www.w3.org/1999/XSL/Transform.
- In each XSLT stylesheet, you must declare this namespace in the stylesheet element tag and
- bind it to a local prefix. Like the XSLT specification, we always use xsl as the XSLT
- namespace prefix in our descriptions and examples, although you are free to bind any prefix
+ <blockquote class="item">The <a href="http://www.w3.org/TR/REC-xml-names/">XML namespace</a> for XSLT. An XML
+ namespace is a collection of element and attribute names, identified by a Unique Resource
+ Identifier (URI), which often takes the form of a URL, but is really just a unique string,
+ not a pointer to a web page. The XSLT namespace URI is http://www.w3.org/1999/XSL/Transform.
+ In each XSLT stylesheet, you must declare this namespace in the stylesheet element tag and
+ bind it to a local prefix. Like the XSLT specification, we always use xsl as the XSLT
+ namespace prefix in our descriptions and examples, although you are free to bind any prefix
to this namespace.<br />
<br />
</blockquote>
-
+
<p class="label">
<em>XSL Instruction</em>
</p>
<blockquote class="item">Any tag associated with the XSLT namespace.<br />
<br />
</blockquote>
-
+
<p class="label">
<em>Template</em>
</p>
- <blockquote class="item">An element, usually with child elements, that specifies a "rule" or set of
- instructions to perform when a particular kind of node is encountered in the source
+ <blockquote class="item">An element, usually with child elements, that specifies a "rule" or set of
+ instructions to perform when a particular kind of node is encountered in the source
tree.<br />
<br />
</blockquote>
-
+
<p class="label">
<em>XSL Template Instruction</em>
</p>
- <blockquote class="item">Any tag that occurs inside an xsl:template element and is associated with the XSLT
+ <blockquote class="item">Any tag that occurs inside an xsl:template element and is associated with the XSLT
namespace.<br />
<br />
</blockquote>
-
+
<p class="label">
<em>Source Tree</em>
</p>
<blockquote class="item">The XML tree input to the XSL process.<br />
<br />
</blockquote>
-
+
<p class="label">
<em>Result Tree</em>
</p>
<blockquote class="item">The tree that is output by the XSL process.<br />
<br />
</blockquote>
-
+
<p class="label">
<em>Match Pattern</em>
</p>
- <blockquote class="item">The part of a template that defines the kind(s) of nodes to which the template
+ <blockquote class="item">The part of a template that defines the kind(s) of nodes to which the template
applies.<br />
<br />
</blockquote>
</div>
-<p>For more definitions of XSLT terminology, see Dave Pawson's
- <a href="http://www.dpawson.co.uk/xsl/xslvocab.html">XSLT Terminology
- Clarification</a> and the Glossary in Michael Kay's
- <a href="http://www.wrox.com/books/0764543814.shtml">XSLT Programmer's Reference</a>.</p>
<p align="right" size="2">
<a href="#content">(top)</a>
diff --git a/xalan-j/public_apis.html b/xalan-j/public_apis.html
index 9036c12..58453f9 100644
--- a/xalan-j/public_apis.html
+++ b/xalan-j/public_apis.html
@@ -75,7 +75,7 @@
<a href="http://xalan.apache.org/index.html">Home</a>
</li></ul><hr /><ul>
<li>
-<a href="index.html">Xalan-J 2.7.2</a>
+<a href="index.html">Xalan-J 2.7.3</a>
</li>
<li>
<a href="charter.html">Charter</a>
diff --git a/xalan-j/readme.html b/xalan-j/readme.html
index 9415456..b13656c 100644
--- a/xalan-j/readme.html
+++ b/xalan-j/readme.html
@@ -75,7 +75,7 @@
<a href="http://xalan.apache.org/index.html">Home</a>
</li></ul><hr /><ul>
<li>
-<a href="index.html">Xalan-J 2.7.2</a>
+<a href="index.html">Xalan-J 2.7.3</a>
</li>
<li>
<a href="charter.html">Charter</a>
@@ -160,7 +160,10 @@
<h2>Release Notes</h2>
<ul>
<li>
-<a href="#notes_latest">Release notes for version 2.7.2</a>
+ <a href="#notes_latest">Release notes for version 2.7.3</a>
+</li>
+ <li>
+<a href="#notes_272">Release notes for version 2.7.2</a>
</li>
<li>
<a href="#notes_271">Release notes for version 2.7.1</a>
@@ -193,8 +196,57 @@
<a href="#other">Other points of interest</a>
</li>
</ul>
-
- <a name="notes_latest"></a>
+
+ <a name="notes_latest"></a>
+ <p align="right" size="2">
+ <a href="#content">(top)</a>
+ </p>
+ <h3>Release notes for Xalan-Java 2.7.3</h3>
+ <p>
+ Xalan-Java 2.7.3 was released in April 2023.
+ </p>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Java 8 requirement</h4>
+<p>
+ This XalanJ release, requires users to use Java minimum version 8 for working with XalanJ.
+</p>
+<h4>Fix for CVE-2022-34169 An integer truncation issue when processing malicious XSLT stylesheets</h4>
+<p>
+ This issue was fixed within XalanJ's XSLTC processor. This XalanJ issue, when present causes
+ following problems: Malicious XSLT stylesheets may be written, which could result in XalanJ
+ invalid translet Java byte code to be produced by XalanJ XSLTC processor. The XalanJ translet
+ is a Java byte code compiled representation, of an XSLT transformation.
+</p>
+<h4>Upgrade to Apache Commons BCEL 6.7.0</h4>
+<p>
+ This XalanJ release, contains upgraded version of Apache Commons BCEL library [Gary Gregory].
+</p>
+<h4>Enhancements for, performing XalanJ build and running of XalanJ tests from source distribution</h4>
+<p>
+ The XalanJ users, can now make XalanJ builds and perform XalanJ tests from the XalanJ source
+ distribution. The XalanJ build scripts for the implementation and the tests, both for the
+ Windows and Linux platforms, were enhanced to support building XalanJ with JDK 1.8.
+ [Gary Gregory, Joseph Kessselman, Mukul Gandhi]
+</p>
+<h4>Upgrade to Xerces-J 2.12.2</h4>
+<p>
+ This XalanJ release, contains upgraded versions of <CODE><FONT face="courier, monospaced">xercesImpl.jar</FONT></CODE>
+ and <CODE><FONT face="courier, monospaced">xml-apis.jar</FONT></CODE> (Xerces-J 2.12.2).
+</p>
+<h4>XALANJ Jira bug fixes</h4>
+<p>
+ <a href="https://issues.apache.org/jira/browse/XALANJ-2638">2638</a>,
+ <a href="https://issues.apache.org/jira/browse/XALANJ-2623">2623</a>,
+ <a href="https://issues.apache.org/jira/browse/XALANJ-2607">2607</a>,
+ <a href="https://issues.apache.org/jira/browse/XALANJ-2601">2601</a>,
+ <a href="https://issues.apache.org/jira/browse/XALANJ-2600">2600</a>,
+ <a href="https://issues.apache.org/jira/browse/XALANJ-2584">2584</a>,
+ <a href="https://issues.apache.org/jira/browse/XALANJ-2346">2346</a>
+</p>
+
+ <a name="notes_272"></a>
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
@@ -202,7 +254,7 @@
<p>
Xalan-Java 2.7.2 was released in April 2014.
</p>
-
+
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
@@ -222,32 +274,32 @@
<p>
These properties can be used to load an arbitrary class or access an arbitrary URL/resource so are problematic when secure processing is desired.
</p>
- <p>
- <code>
+ <p>
+ <code>
<xsl:output xalan:content-handler="org.example.BadClass" ...
- </code>
+ </code>
</p>
- <p>
- <code>
+ <p>
+ <code>
<xsl:output xalan:entities="http://example.org/reallyLargeFile.bin" ...
- </code>
+ </code>
</p>
<p>
- These features could be used to load a class that had undesirable side-effects or to load a large file and exhaust memory, etc.
+ These features could be used to load a class that had undesirable side-effects or to load a large file and exhaust memory, etc.
</p>
<p>
- See <a href="#https://issues.apache.org/jira/browse/XALANJ-2435">XALANJ-2435</a>.
+ See <a href="#https://issues.apache.org/jira/browse/XALANJ-2435">XALANJ-2435</a>.
</p>
-
-
+
+
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
<h4>Upgrade to Xerces-J 2.11.0 and XML Commons External 1.4.01</h4>
The distributions contain upgraded versions of <code>xercesImpl.jar</code>
(Xerces-J 2.11.0) and <code>xml-apis.jar</code> (XML Commons External 1.4.01).
-
-
+
+
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
@@ -266,13 +318,13 @@
<a href="https://issues.apache.org/jira/browse/XALANJ-2446">2446</a>,
<a href="https://issues.apache.org/jira/browse/XALANJ-2447">2447</a>
</p>
- <p>You can also view the list in
+ <p>You can also view the list in
<a href="https://issues.apache.org/jira/browse/XALANJ-2424?jql=project%20%3D%20XALANJ%20AND%20fixVersion%20%3D%202.7.2%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC">Jira</a>
</p>
-
-
-
-
+
+
+
+
<a name="notes_271"></a>
<p align="right" size="2">
<a href="#content">(top)</a>
@@ -286,11 +338,11 @@
for an XML parser. These changes are seen in the new class
<a href="apidocs/org/apache/xml/serializer/DOM3Serializer.html">
<code>org.apache.xml.serializer.DOM3Serializer</code>
-</a>
+</a>
and the new package
<code>org.apache.xml.serializer.dom3</code>
- as well as a new method,
- <code>asDOM3Serializer()</code> on the older
+ as well as a new method,
+ <code>asDOM3Serializer()</code> on the older
<a href="apidocs/org/apache/xml/serializer/Serializer.html">
<code>org.apache.xml.serializer.Serializer</code>
</a> interface.
@@ -299,8 +351,8 @@
More details are in the javadoc of those classes and interfaces.
</p>
- <p>
- The distributions contain upgraded versions of <code>xercesImpl.jar</code>
+ <p>
+ The distributions contain upgraded versions of <code>xercesImpl.jar</code>
(Xerces-J 2.9.0) and <code>xml-apis.jar</code> (XML Commons External 1.3.04).
The distributions were tested with these versions of Xerces-J
and XML Commons External and are the recommended versions to use with
@@ -311,9 +363,9 @@
if your Xalan-Java and Xerces-Java builds are not in synch.
</p>
-
+
<p>
- Xalan-Java 2.7.1 contains the following functional enhancements,
+ Xalan-Java 2.7.1 contains the following functional enhancements,
performance enhancements and bug fixes since 2.7.0:
</p>
<ul>
@@ -329,7 +381,7 @@
<a href="http://issues.apache.org/jira/secure/ViewIssue.jspa?key=XALANJ-2061">2061</a>,
<a href="http://issues.apache.org/jira/secure/ViewIssue.jspa?key=XALANJ-2091">2091</a>,
<a href="http://issues.apache.org/jira/secure/ViewIssue.jspa?key=XALANJ-2108">2108</a>,
- <a href="http://issues.apache.org/jira/secure/ViewIssue.jspa?key=XALANJ-2159">2159</a>,
+ <a href="http://issues.apache.org/jira/secure/ViewIssue.jspa?key=XALANJ-2159">2159</a>,
<a href="http://issues.apache.org/jira/secure/ViewIssue.jspa?key=XALANJ-2184">2184</a>,
<a href="http://issues.apache.org/jira/secure/ViewIssue.jspa?key=XALANJ-2196">2196</a>,
<a href="http://issues.apache.org/jira/secure/ViewIssue.jspa?key=XALANJ-2199">2199</a>,
@@ -393,8 +445,8 @@
<a href="http://issues.apache.org/jira/secure/ViewIssue.jspa?key=XALANJ-2395">2395</a>
</li>
</ul>
-
-
+
+
<a name="notes_270"></a>
<p align="right" size="2">
<a href="#content">(top)</a>
@@ -402,91 +454,91 @@
<h3>Release notes for Xalan-Java 2.7.0</h3>
<p>Xalan-Java 2.7.0 was released on August 8, 2005.
</p>
- <p>Xalan-Java 2.7.0 contains the following functional enhancements, performance enhancements and
+ <p>Xalan-Java 2.7.0 contains the following functional enhancements, performance enhancements and
bug fixes since 2.6.0.
</p>
<h5>Support for JAXP 1.3</h5>
<p>Support for JAXP 1.3 has been introduced in this release of Xalan-Java. JAXP 1.3
includes a new javax.xml.xpath package, which provides an object-model neutral
- API for the evaluation of XPath expressions and access to the evaluation environment.
- Please refer to <a href="xpath_apis.html">Using the JAXP 1.3 XPath API</a> for details on how to
- use the new XPath API. You can also look at the code in the samples
- <a href="samples.html#applyxpathjaxp">ApplyXPathJAXP</a> ,
- <a href="samples.html#xpathresolver">XPathResolver</a> and
+ API for the evaluation of XPath expressions and access to the evaluation environment.
+ Please refer to <a href="xpath_apis.html">Using the JAXP 1.3 XPath API</a> for details on how to
+ use the new XPath API. You can also look at the code in the samples
+ <a href="samples.html#applyxpathjaxp">ApplyXPathJAXP</a> ,
+ <a href="samples.html#xpathresolver">XPathResolver</a> and
<a href="samples.html#extensionresolver">ExtensionFunctionResolver</a>.</p>
-
+
<p>There are also a few new transformer features
in JAXP 1.3, as described in the following list:<br />
<br />
- <li>A new method
+ <li>A new method
<a href="apidocs/javax/xml/transform/TransformerFactory.html#setFeature(java.lang.String, boolean)">
TransformerFactory.setFeature(String name, boolean value)</a>
</li>
<li>A new method <a href="apidocs/javax/xml/transform/Transformer.html#reset()">
Transformer.reset()</a>
</li>
- <li>A new nextSibling attribute is introduced for
- <a href="apidocs/javax/xml/transform/dom/DOMResult.html">DOMResult</a>, accessible
+ <li>A new nextSibling attribute is introduced for
+ <a href="apidocs/javax/xml/transform/dom/DOMResult.html">DOMResult</a>, accessible
by the constructors, getter and setter methods.</li>
<li>Support for the <a href="features.html#secureprocessing">secure processing feature</a>
</li>
</p>
-
+
<h5>New default error handling behavior</h5>
The behavior of the default <a href="apidocs/javax/xml/transform/ErrorListener.html">ErrorListener</a>
- was changed in this release of Xalan-Java,
- in order to conform with a clarification of the required behavior described by JAXP 1.3.
- If an application does not register its own ErrorListener, the default ErrorListener is
- used which reports all warnings and errors to System.err and does not throw any Exceptions. Applications
- are strongly encouraged to register and use ErrorListeners that insure proper behavior for warnings and errors.
+ was changed in this release of Xalan-Java,
+ in order to conform with a clarification of the required behavior described by JAXP 1.3.
+ If an application does not register its own ErrorListener, the default ErrorListener is
+ used which reports all warnings and errors to System.err and does not throw any Exceptions. Applications
+ are strongly encouraged to register and use ErrorListeners that insure proper behavior for warnings and errors.
The default ErrorListener of the old Xalan-Java Interpretive processor throws exceptions on errors and fatal errors. If your
code expects exceptions to be thrown on errors and fatal errors, you have to set a customized ErrorListener on
- TransformerFactory and/or Transformer. You can use
+ TransformerFactory and/or Transformer. You can use
<a href="apidocs/org/apache/xml/utils/DefaultErrorHandler.html">org.apache.xml.utils.DefaultErrorHandler</a>
as a sample ErrorListener implementation.
-
+
<h5>Support for XML 1.1</h5>
<p>This release of Xalan-Java adds support for Namespaces in XML 1.1 and XML 1.1 output documents.
The processors: <br />
<br />
<li> support C0 control characters </li>
<li> handle C1 control characters in a way that is consistent with the requirements of XML 1.1 </li>
- <li> treat NEL (U+0085) and LSEP (U+2028) as end-of-line markers </li>
+ <li> treat NEL (U+0085) and LSEP (U+2028) as end-of-line markers </li>
<li> support <a href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized Resource Identifiers (IRIs)</a> </li>
<li> support the additional characters in NCNames and QNames permitted by XML 1.1 and Namespaces in XML 1.1 </li>
</p>
- <p>The processors do not undeclare namespaces other than the default namespace in serialized documents Also, Full
+ <p>The processors do not undeclare namespaces other than the default namespace in serialized documents Also, Full
normalization is not supported.</p>
- <p>An input document can be either XML 1.0 or XML 1.1. Also, a stylesheet document can be either XML 1.0 or XML 1.1.
+ <p>An input document can be either XML 1.0 or XML 1.1. Also, a stylesheet document can be either XML 1.0 or XML 1.1.
A stylesheet document must conform to the XSLT 1.0 specifications.</p>
- <p>Note that it is possible for a stylesheet module that is an XML 1.1 document to use constructs that cannot be
- serialized as part of a valid XML 1.0 document, and for a stylesheet module that is an XML 1.0 document to use
- constructs that cannot be serialized as part of a valid XML 1.1 document. For example, a stylesheet module that
- is an XML 1.1 document might contain a literal result element whose name contains characters that are not permitted
- as part of a QName in a document that conforms to Namespaces for XML 1.0. The user needs to ensure that the nodes
- created by the stylesheet can be serialized as part of a well-formed document of the required version of XML.</p>
-
+ <p>Note that it is possible for a stylesheet module that is an XML 1.1 document to use constructs that cannot be
+ serialized as part of a valid XML 1.0 document, and for a stylesheet module that is an XML 1.0 document to use
+ constructs that cannot be serialized as part of a valid XML 1.1 document. For example, a stylesheet module that
+ is an XML 1.1 document might contain a literal result element whose name contains characters that are not permitted
+ as part of a QName in a document that conforms to Namespaces for XML 1.0. The user needs to ensure that the nodes
+ created by the stylesheet can be serialized as part of a well-formed document of the required version of XML.</p>
+
<h5>Support for Alternative BSF Implementations</h5>
- <p>Extensions written in Java are directly supported by Xalan-Java. For extensions written in languages other than
- Java, Xalan-Java uses the Bean Scripting Framework (BSF), an architecture for incorporating scripting into Java
+ <p>Extensions written in Java are directly supported by Xalan-Java. For extensions written in languages other than
+ Java, Xalan-Java uses the Bean Scripting Framework (BSF), an architecture for incorporating scripting into Java
applications and applets, and an implementation of BSF must be available on the classpath. In previous
- releases, IBM's BSF implementation (<code>bsf.jar</code> from 2001) has been included in the Xalan-Java distribution.
+ releases, IBM's BSF implementation (<code>bsf.jar</code> from 2001) has been included in the Xalan-Java distribution.
Some time ago IBM donated their BSF implementation to the <a href="http://jakarta.apache.org/bsf/index.html">
- Apache Jakarta BSF</a> project. As of this release,
- the IBM <code>bsf.jar</code> is no longer included in the Xalan-Java distribution. To use extensions written in
+ Apache Jakarta BSF</a> project. As of this release,
+ the IBM <code>bsf.jar</code> is no longer included in the Xalan-Java distribution. To use extensions written in
languages other than Java, please download a version of Jakarta BSF and put it on your classpath. To use
a different BSF implementation, please refer to <a href="extensions.html#BSFManager">setting the BSFManager</a>.</p>
-
+
<h5>New serializer.jar</h5>
- <p>In this release of Xalan-Java the code related to serialization of output result trees has been pulled out of
+ <p>In this release of Xalan-Java the code related to serialization of output result trees has been pulled out of
<code>xalan.jar</code> and moved into a new jar file, named <code>serializer.jar</code>.</p>
- <p>The code in <code>serializer.jar</code> has been modified to have no build or runtime dependencies on the rest of the
- code in Xalan-Java, therefore, <code>serializer.jar</code> can be used in a stand-alone fashion through its public APIs.
+ <p>The code in <code>serializer.jar</code> has been modified to have no build or runtime dependencies on the rest of the
+ code in Xalan-Java, therefore, <code>serializer.jar</code> can be used in a stand-alone fashion through its public APIs.
Although the code has been modified to create a stand-alone jar, the serializer public APIs have not changed
and the package names and classnames are the same as they were last release.</p>
-
+
<p>Also the following:</p>
@@ -515,14 +567,14 @@
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=29411">29411</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=29655">29655</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=29706">29706</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=30056">30056</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=30056">30056</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=30142">30142</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=30262">30262</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=30301">30301</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=30658">30658</a>
</li>
<li>XALANJ Jira bug fixes:
- <a href="http://issues.apache.org/jira/secure/ViewIssue.jspa?key=XALANJ-936">936</a>,
+ <a href="http://issues.apache.org/jira/secure/ViewIssue.jspa?key=XALANJ-936">936</a>,
<a href="http://issues.apache.org/jira/secure/ViewIssue.jspa?key=XALANJ-1186">1186</a>,
<a href="http://issues.apache.org/jira/secure/ViewIssue.jspa?key=XALANJ-1368">1368</a>,
<a href="http://issues.apache.org/jira/secure/ViewIssue.jspa?key=XALANJ-1417">1417</a>,
@@ -550,7 +602,7 @@
<a href="http://issues.apache.org/jira/secure/ViewIssue.jspa?key=XALANJ-1888">1888</a>,
<a href="http://issues.apache.org/jira/secure/ViewIssue.jspa?key=XALANJ-1891">1891</a>,
<a href="http://issues.apache.org/jira/secure/ViewIssue.jspa?key=XALANJ-1908">1908</a>,
- <a href="http://issues.apache.org/jira/secure/ViewIssue.jspa?key=XALANJ-1912">1912</a>,
+ <a href="http://issues.apache.org/jira/secure/ViewIssue.jspa?key=XALANJ-1912">1912</a>,
<a href="http://issues.apache.org/jira/secure/ViewIssue.jspa?key=XALANJ-1924">1924</a>,
<a href="http://issues.apache.org/jira/secure/ViewIssue.jspa?key=XALANJ-1925">1925</a>,
<a href="http://issues.apache.org/jira/secure/ViewIssue.jspa?key=XALANJ-1937">1937</a>,
@@ -619,10 +671,10 @@
</li>
<li>For a list of Xalan-Java commits, see xalan-cvs@xml.apache.org in the
<a href="http://mail-archives.apache.org/mod_mbox/">Apache mail archives</a>.
- </li>
+ </li>
</ul>
-
-
+
+
<a name="notes_260"></a>
<p align="right" size="2">
<a href="#content">(top)</a>
@@ -630,7 +682,7 @@
<h3>Release notes for Xalan-Java 2.6.0</h3>
<p>Xalan-Java 2.6.0 was released on February 29, 2004 (a leap year!).
</p>
- <p>Xalan-Java 2.6.0 contains the following functional enhancements, performance enhancements and
+ <p>Xalan-Java 2.6.0 contains the following functional enhancements, performance enhancements and
bug fixes since 2.5.2:</p>
<ul>
<li>Improvement in translet initialization time.</li>
@@ -639,32 +691,32 @@
XSLTC runtime, an error will be reported.</li>
<li>Changes that allow XSLTC to use other DTM implementations.</li>
<li>Release notes for the XML Serializer. The serializer will no longer put a newline after
- the xml header tag unless indent="yes". See bugzilla
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=24304">24304</a>.</li>
- <li>Rename of Xalan Java's xalan:doc-cache-off processing instruction to
+ the xml header tag unless indent="yes". See bugzilla
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=24304">24304</a>.</li>
+ <li>Rename of Xalan Java's xalan:doc-cache-off processing instruction to
xalan-doc-cache-off. This change was necessary due to a recent
- change in Xerces. Xerces has started detecting the Namespace
- well-formedness rule that a processing instruction's PITarget must not contain
+ change in Xerces. Xerces has started detecting the Namespace
+ well-formedness rule that a processing instruction's PITarget must not contain
a colon. The old-style PI (xalan:doc-cache-off) will be accepted provided that
- the XML parser does not report it as an error. See bugzilla
+ the XML parser does not report it as an error. See bugzilla
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=26217">26217</a>.</li>
<li>Enhancement to XSLTC's URIResolvers and the general mechanism to resolve relative URIs.
XSLTC is now compatible with Xalan Intepretive.</li>
<li>Addition of a TransformThread sample that demonstrates how to use different transformers
on different threads and in different modes.</li>
<li>Upgrade to Xerces-J (2.6.2) and a new version of xml-commons (xml-commons-external-1.2.01)</li>
- <li>Elimination of "enum" as a name to allow compilation under JDK 1.5</li>
-
- <li>Bugzilla fixes:
+ <li>Elimination of "enum" as a name to allow compilation under JDK 1.5</li>
+
+ <li>Bugzilla fixes:
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=797">797</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=1396">1396</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=5761">5761</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=15140">15140</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=16889">16889</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=18351">18351</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=18351">18351</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=19194">19194</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=19464">19464</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=22376">22376</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=22376">22376</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=23046">23046</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=23591">23591</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=24278">24278</a>,
@@ -673,15 +725,15 @@
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=24188">24188</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=24302">24302</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=24304">24304</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=24365">24365</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=24365">24365</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=24414">24414</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=24518">24518</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=24695">24695</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=24728">24728</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=24728">24728</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=24788">24788</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=24793">24793</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=24958">24958</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=24979">24979</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=24958">24958</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=24979">24979</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=24985">24985</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=24988">24988</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=25368">25368</a>,
@@ -698,14 +750,14 @@
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=26697">26697</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=26742">26742</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=26829">26829</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=26842">26842</a>
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=26842">26842</a>
</li>
<li>For a list of Xalan-Java commits, see xalan-cvs@xml.apache.org in the
<a href="http://mail-archives.apache.org/mod_mbox/">Apache mail archives</a>.
- </li>
+ </li>
</ul>
-
-
+
+
<a name="notes_252"></a>
<p align="right" size="2">
<a href="#content">(top)</a>
@@ -719,61 +771,61 @@
<li>
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=782">782</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=788">788</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=789">789</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=795">795</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=789">789</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=795">795</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=890">890</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=3415">3415</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=5133">5133</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=3415">3415</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=5133">5133</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=5972">5972</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=6155">6155</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=7205">7205</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=7408">7408</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=6155">6155</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=7205">7205</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=7408">7408</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=10900">10900</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=11414">11414</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=12441">12441</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=12441">12441</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=13082">13082</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14149">14149</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14607">14607</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=15090">15090</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14607">14607</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=15090">15090</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=15327">15327</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=15700">15700</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=15700">15700</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=15828">15828</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=15901">15901</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=15901">15901</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=16311">16311</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=16512">16512</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=16512">16512</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=16675">16675</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=17630">17630</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=17630">17630</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=18821">18821</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=18907">18907</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=19297">19297</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=19591">19591</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=19770">19770</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=19823">19823</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=19823">19823</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=19890">19890</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=19918">19918</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=19972">19972</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=19973">19973</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=19973">19973</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=20074">20074</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=20114">20114</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=20256">20256</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=20537">20537</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=20572">20572</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=20572">20572</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=20625">20625</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=20685">20685</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=20685">20685</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=20795">20795</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=20819">20819</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=20819">20819</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=20832">20832</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=20841">20841</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=20841">20841</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=20909">20909</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=20913">20913</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=20920">20920</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=21039">21039</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=21048">21048</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=21087">21087</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=20913">20913</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=20920">20920</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=21039">21039</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=21048">21048</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=21087">21087</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=21300">21300</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=21309">21309</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=21309">21309</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=21449">21449</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=21452">21452</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=21452">21452</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=21471">21471</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=21478">21478</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=21491">21491</a>,
@@ -781,36 +833,36 @@
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=21713">21713</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=21805">21805</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=21893">21893</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=22025">22025</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=22115">22115</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=22167">22167</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=22025">22025</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=22115">22115</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=22167">22167</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=22342">22342</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=22422">22422</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=22438">22438</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=22438">22438</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=22623">22623</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=22769">22769</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=22777">22777</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=22808">22808</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=22880">22880</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=22880">22880</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=23200">23200</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=23113">23113</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=23115">23115</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=23271">23271</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=23418">23418</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=23706">23706</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=23812">23812</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=23896">23896</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=23812">23812</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=23896">23896</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=23983">23983</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=24013">24013</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=24025">24025</a>
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=24013">24013</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=24025">24025</a>
</li>
<li>For a list of Xalan-Java commits, see xalan-cvs@xml.apache.org in the
<a href="http://mail-archives.apache.org/mod_mbox/">Apache mail archives</a>.
- </li>
+ </li>
</ul>
-
-
- <a name="notes_251"></a>
+
+
+ <a name="notes_251"></a>
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
@@ -821,7 +873,7 @@
<p>Fixes in this release include the following: </p>
<ul>
<li>
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=15200">15200</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=15200">15200</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=18585">18585</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=18926">18926</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=19029">19029</a>,
@@ -837,10 +889,10 @@
</li>
<li>For a list of Xalan-Java commits, see xalan-cvs@xml.apache.org in the
<a href="http://mail-archives.apache.org/mod_mbox/">Apache mail archives</a>.
- </li>
+ </li>
</ul>
-
-
+
+
<a name="notes_250"></a>
<p align="right" size="2">
<a href="#content">(top)</a>
@@ -848,23 +900,23 @@
<h3>Release notes for Xalan-Java 2.5.0</h3>
<p>Xalan-Java 2.5.0 was released on April 16,2003.
</p>
- <p>Xalan-Java 2.5.0 contains a variety of features, bug fixes and
+ <p>Xalan-Java 2.5.0 contains a variety of features, bug fixes and
performance enhancements since 2.5.D1.</p>
<p>New features in Xalan-Java 2.5.0 include:
<ul>
- <li>integration of the Document Table Model (DTM) with the XSLTC
+ <li>integration of the Document Table Model (DTM) with the XSLTC
processor [Henry Zongaro, Morris Kwan] and </li>
- <li>integration of the Xalan Interpretive and Xalan Compiled
- serializers into a common serializer [Brian Minchau].</li>
- </ul>
- These features have been driven by a need to get common behavior,
- improve maintainability, reduce duplication of effort for future work,
+ <li>integration of the Xalan Interpretive and Xalan Compiled
+ serializers into a common serializer [Brian Minchau].</li>
+ </ul>
+ These features have been driven by a need to get common behavior,
+ improve maintainability, reduce duplication of effort for future work,
and in some cases improve performance and conformance.</p>
- <p>Refer to <a href="whatsnew.html">What's New</a> for a description of the new function
- and <a href="history.html">History of software changes</a> for a list of the various
+ <p>Refer to <a href="whatsnew.html">What's New</a> for a description of the new function
+ and <a href="history.html">History of software changes</a> for a list of the various
bug fixes and other enhancements in this release.</p>
-
-
+
+
<a name="notes_25D1"></a>
<p align="right" size="2">
<a href="#content">(top)</a>
@@ -873,64 +925,64 @@
<p>Xalan-Java 2.5.D1 was released on March 3, 2003.
</p>
<p>This developer's release, Xalan-Java 2.5.D1, has changes since 2.4.1 and
- is primarily for the purpose of releasing
- various bug fixes to the community. These will eventually be released officially in
+ is primarily for the purpose of releasing
+ various bug fixes to the community. These will eventually be released officially in
a future Xalan-Java 2.5 version, along with some new function.</p>
<p>Fixes in this release include the following: </p>
<ul>
<li>
-<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=4858">4858</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=5140">5140</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=6075">6075</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=6157">6157</a>,
+<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=4858">4858</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=5140">5140</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=6075">6075</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=6157">6157</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=10053">10053</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=10626">10626</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=10626">10626</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=12481">12481</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=13414">13414</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=13651">13651</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=13774">13774</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=13775">13775</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=13414">13414</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=13651">13651</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=13774">13774</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=13775">13775</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=13977">13977</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14112">14112</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14148">14148</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14157">14157</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14178">14178</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14148">14148</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14157">14157</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14178">14178</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14229">14229</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14236">14236</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14237">14237</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14241">14241</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14236">14236</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14237">14237</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14241">14241</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14244">14244</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14300">14300</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14322">14322</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14324">14324</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14365">14365</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14368">14368</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14406">14406</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14300">14300</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14322">14322</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14324">14324</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14365">14365</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14368">14368</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14406">14406</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14578">14578</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14753">14753</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14856">14856</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14856">14856</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14862">14862</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14965">14965</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=15074">15074</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=15074">15074</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=15094">15094</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=15218">15218</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=15218">15218</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=15254">15254</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=15373">15373</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=15373">15373</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=15586">15586</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=16745">16745</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=16745">16745</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=17030">17030</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=17136">17136</a>
</li>
- <li>Support for and bundling of Xerces Java 2.3.</li>
+ <li>Support for and bundling of Xerces Java 2.3.</li>
<li>Support for and bundling of <code>xml-apis.jar</code> from the tck-jaxp-1_2_0 branch of xml-commons.
- This version of the Java APIs for XML Processing successfully passes the JAXP 1.1 and
- JAXP 1.2 TCKs.</li>
+ This version of the Java APIs for XML Processing successfully passes the JAXP 1.1 and
+ JAXP 1.2 TCKs.</li>
<li>For a list of Xalan-Java commits, see xalan-cvs@xml.apache.org in the
- <a href="http://mail-archives.apache.org/mod_mbox/">Apache mail archives</a>.</li>
- </ul>
-
-
- <a name="notes_241"></a>
+ <a href="http://mail-archives.apache.org/mod_mbox/">Apache mail archives</a>.</li>
+ </ul>
+
+
+ <a name="notes_241"></a>
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
@@ -940,7 +992,7 @@
<ul>
<li>Performance fixes and enhancements to address the degradation of performance between Xalan-Java
version 2.3.1 and Xalan-Java 2.4.0.</li>
- <li>A prototype implementation of the <a href="http://www.w3.org/TR/2002/WD-DOM-Level-3-XPath-20020328/">DOM Level 3 XPath Specification</a>.
+ <li>A prototype implementation of the <a href="http://www.w3.org/TR/2002/WD-DOM-Level-3-XPath-20020328/">DOM Level 3 XPath Specification</a>.
The implementation is considered 'experimental' at this time due to the status of the specification.
See the new sample, <a href="samples.html#applyxpathdom">ApplyXPathDOM</a> for an
example of how to use this API.</li>
@@ -948,13 +1000,13 @@
<ul>
<li>Implement canonical namespaces for all Xalan extensions. All extensions
now use namespaces starting with <code>http://xml.apache.org/xalan</code>. The old namespaces are
- still supported for backward compatibility. See the updated
+ still supported for backward compatibility. See the updated
<a href="extensionslib.html#intro">extensions</a> documentation for details.</li>
- <li>Added new EXSLT extension functions, including the EXSLT dynamic extension functions
- max, min, sum, map, evaluate and closure, the EXSLT strings extension functions align,
+ <li>Added new EXSLT extension functions, including the EXSLT dynamic extension functions
+ max, min, sum, map, evaluate and closure, the EXSLT strings extension functions align,
concat, padding, split and tokenize, and some new extension functions in the math module.</li>
<li>Reorganized the extension functions for new EXSLT extensions.
- The implementation of some extension functions (intersection, difference, distinct,
+ The implementation of some extension functions (intersection, difference, distinct,
evaluate and tokenize) are moved from the main Extensions class to the corresponding EXSLT modules.</li>
<li>Enable the EXSLT extensions for XSLTC. The EXSLT common, math, sets, dates-and-times and strings
modules can be used in XSLTC.</li>
@@ -963,8 +1015,8 @@
<li>Enhancement in Java extenion for XSLTC. Three namespace formats (Java, package and class) can all
be used in XSLTC. More type conversion rules are added as well.</li>
</ul>
- <li>Enable support for invoking transformations using the Xalan compiler (XSLTC) via the
- Xalan interpretive Process command line. Specifically, the -XSLTC option was added. The
+ <li>Enable support for invoking transformations using the Xalan compiler (XSLTC) via the
+ Xalan interpretive Process command line. Specifically, the -XSLTC option was added. The
-TT, -TG, -TS, -TTC, -QC, -L, -INCREMENTAL, -NOOPTIMIZE and -RL option do not work in XSLTC mode. All
other existing options can be used with -XSLTC. Additional options were added to enable XSLTC compile
and transform modes: -XO, -XD, -XJ, -XP, -XN, -XX, -XT. See the Process usage statement for more
@@ -973,42 +1025,42 @@
return a JDBC exception.</li>
<li>Fixed a limitation for XPath expressions. The token queue and operations map can now grow
to accomodate really large XPath expressions.</li>
- <li>Fixes for the following bugzilla defects:
+ <li>Fixes for the following bugzilla defects:
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=4344">4344</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=5046">5046</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=5046">5046</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=6181">6181</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=6927">6927</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=6927">6927</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=7161">7161</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=7357">7357</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=8175">8175</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=8473">8473</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=8939">8939</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=9731">9731</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=9731">9731</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=9959">9959</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=10176">10176</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=10384">10384</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=10414">10414</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=10643">10643</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=11073">11073</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=10643">10643</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=11073">11073</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=11341">11341</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=11661">11661</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=11661">11661</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=11743">11743</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=11809">11809</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=12077">12077</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=12127">12127</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=12127">12127</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=12298">12298</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=12687">12687</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=13059">13059</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=13303">13303</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=13303">13303</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=13305">13305</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=13106">13106</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=13501">13501</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=13106">13106</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=13501">13501</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=13711">13711</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=13754">13754</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=13863">13863</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=13863">13863</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=13944">13944</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=14022">14022</a>
-</li>
+</li>
<li>Support for and bundling of Xerces Java 2.2.</li>
<li>Support for and bundling of <code>xml-apis.jar</code> from the factoryfinder-build of the RIVERCOURT1 branch of xml-commons. This version of the Java
APIs for XML Processing successfully passes the JAXP 1.1 and JAXP 1.2 TCKs.</li>
@@ -1016,8 +1068,8 @@
<a href="http://mail-archives.apache.org/mod_mbox/">Apache mail archives</a>.</li>
<li>Support building Xalan with JDK 1.4.</li>
</ul>
-
-
+
+
<a name="notes_240"></a>
<p align="right" size="2">
<a href="#content">(top)</a>
@@ -1026,50 +1078,50 @@
<p>Xalan-Java 2.4.0 was released on September 3, 2002.
</p>
<ul>
- <li>Fixes for the following bugzilla defects :
+ <li>Fixes for the following bugzilla defects :
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=3238">3238</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=4603">4603</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=5013">5013</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=5013">5013</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=5016">5016</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=5941">5941</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=6071">6071</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=6268">6268</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=6284">6284</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=6284">6284</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=6356">6356</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=6547">6547</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=6798">6798</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=6833">6833</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=6833">6833</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=6925">6925</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=6972">6972</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=7023">7023</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=7023">7023</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=7118">7118</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=7123">7123</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=7123">7123</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=7157">7157</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=7410">7410</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=7776">7776</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=8324">8324</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=8358">8358</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=8551">8551</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=8894">8894</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=8894">8894</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=9068">9068</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=9137">9137</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=9137">9137</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=9146">9146</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=9171">9171</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=9174">9174</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=9179">9179</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=9572">9572</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=9575">9575</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=9572">9572</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=9575">9575</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=9683">9683</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=9753">9753</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=10137">10137</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=10306">10306</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=10137">10137</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=10306">10306</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=10323">10323</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=10625">10625</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=10715">10715</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=10832">10832</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=10837">10837</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=10839">10839</a>,
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=10914">10914</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=10839">10839</a>,
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=10914">10914</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=10945">10945</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=11123">11123</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=11166">11166</a>,
@@ -1079,13 +1131,13 @@
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=11987">11987</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=11828">11828</a>,
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=12075">12075</a>
-</li>.
- <li>Xalan-Java now uses a list of supported encodings in a properties file
- (org.apache.xml.serializer.Encodings.properties). Fixes Bugzilla 6356. Patch from Sergey Ushakov. </li>
- <li>Support for the <a href="http://www.exslt.org/">EXSLT</a> function and result elements, and EXSLT
+</li>.
+ <li>Xalan-Java now uses a list of supported encodings in a properties file
+ (org.apache.xml.serializer.Encodings.properties). Fixes Bugzilla 6356. Patch from Sergey Ushakov. </li>
+ <li>Support for the <a href="http://www.exslt.org/">EXSLT</a> function and result elements, and EXSLT
date-and-time functions.</li>
- <li>Improvements to the extensions mechanism to more efficiently handle the detection and analysis of extensions
- during the stylesheet "composition" process, and the generation of the required extension handlers during
+ <li>Improvements to the extensions mechanism to more efficiently handle the detection and analysis of extensions
+ during the stylesheet "composition" process, and the generation of the required extension handlers during
initialization of the transformation process.</li>
<li>Performance improvement. Instead of looping through the ExtendedType objects, use a hashtable and go
directly to the correct object.</li>
@@ -1097,20 +1149,20 @@
<li>For a list of Xalan-Java commits, see xalan-cvs@xml.apache.org in the
<a href="http://mail-archives.apache.org/mod_mbox/">Apache mail archives</a>.</li>
</ul>
-
+
<a name="other"></a>
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
<h3>Other points of interest</h3>
<ul>
- <li>Xalan Java 2 is integrated with release 2 of Xerces-Java. Xalan-Java Version 2.7.2 does not include support for the deprecated Xalan-Java 1 compatability API.
+ <li>Xalan Java 2 is integrated with release 2 of Xerces-Java. Xalan-Java Version 2.7.2 does not include support for the deprecated Xalan-Java 1 compatability API.
The Xalan-Java 1 compatability code does NOT compile with Xerces-Java 2.<br />
<br />
</li>
- <li>The <a href="samples.html#sql">SQL extension samples</a> continue to use InstantDB, but based on our realization of changes
+ <li>The <a href="samples.html#sql">SQL extension samples</a> continue to use InstantDB, but based on our realization of changes
that have occurred in the licensing of InstantDB, we no longer include InstantDB and the associated sample database with our distibution.
- We do, however, provide information on how to <a href="samples.html#instantdbsetup">set up InstantDB</a> to support our SQL
+ We do, however, provide information on how to <a href="samples.html#instantdbsetup">set up InstantDB</a> to support our SQL
extension samples.<br />
<br />
</li>
@@ -1118,7 +1170,7 @@
document on <a href="features.html">Transform features</a>.<br />
<br />
</li>
- <li>If an attempt is made to coerce a different namespace onto a prefix already in use in xsl:attribute, the attribute will come out
+ <li>If an attempt is made to coerce a different namespace onto a prefix already in use in xsl:attribute, the attribute will come out
in the wrong namespace. Workaround: either provide an NCName instead of a QName for the attribute, or provide a QName with a prefix not
used elsewhere.<br />
<br />
@@ -1129,18 +1181,18 @@
<br />
If a literal result element has a namespace prefix, the prefix will be preserved and the namespace URI of the element will be as
specified in the xsl:namespace-alias element, but the result-prefix is not required to appear in the result. This also applies to the
- two other cases of "Literal namespace URI" mentioned in the XSLT Recommendation on
+ two other cases of "Literal namespace URI" mentioned in the XSLT Recommendation on
<a href="http://www.w3.org/TR/xslt#literal-result-element">Literal Result Elements</a>. More simply, if the stylesheet calls for
<axsl:foo> to be output as a literal result element, then it will be output as <axsl:foo> in the result, but the namespace
associated with this "axsl" prefix will be as designated in the xsl:namespace-alias declaration.<br />
<br />
</li>
- <li>For HTML output, Xalan-Java 2 outputs character entity references (&copy; etc.) for the special characters designated in
+ <li>For HTML output, Xalan-Java 2 outputs character entity references (&copy; etc.) for the special characters designated in
<a href="http://www.w3.org/TR/xhtml1/#dtds">Appendix A. DTDs of the XHTML 1.0: The Extensible HyperText Markup
Language</a>. Xalan-Java 1.x, on the other hand, outputs literal characters for some of these special characters.<br />
<br />
</li>
- <li>In conformance with the <a href="http://www.w3.org/TR/xslt#section-HTML-Output-Method">XSLT Recommendation on the HTML
+ <li>In conformance with the <a href="http://www.w3.org/TR/xslt#section-HTML-Output-Method">XSLT Recommendation on the HTML
Output Method</a> and <a href="http://www.w3.org/TR/REC-html40/appendix/notes.html#h-B.2.1">Section B.2.1 of the HTML 4.0
Recommendation</a>, Xalan-Java 2 uses %hh encoding for each byte of the UTF-8 representation of non-ASCII characters in HTML URI
attributes.<br />
@@ -1157,7 +1209,7 @@
for), and if the XML parser supports this feature (Xerces-Java 2.11.0 does not).<br />
<br />
</li>
- <li>When you traverse the namespace axis for a collection of element nodes, Xalan-Java includes <b>one</b> namespace node for each namespace in scope
+ <li>When you traverse the namespace axis for a collection of element nodes, Xalan-Java includes <b>one</b> namespace node for each namespace in scope
for one or more of the nodes in that collection. The XPath expression does not return additional (redundant) namespace nodes for each element
for which the namespace nodes are in scope.<br />
<br />
@@ -1166,11 +1218,11 @@
use of the default character encoding to read META-INF/Services.<br />
<br />
</li>
- <li>As <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=1800">Bugzilla bug 1800</a> reports, the Transformer does not get the
- setTransformState event until after the startDocument event. This could present a problem for tools developers, and we do intend to fix this
- bug.</li>
+ <li>As <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=1800">Bugzilla bug 1800</a> reports, the Transformer does not get the
+ setTransformState event until after the startDocument event. This could present a problem for tools developers, and we do intend to fix this
+ bug.</li>
</ul>
-
+
diff --git a/xalan-j/resources.html b/xalan-j/resources.html
index 67d14f1..7c3fc16 100644
--- a/xalan-j/resources.html
+++ b/xalan-j/resources.html
@@ -73,7 +73,7 @@
<a href="http://xalan.apache.org/index.html">Home</a>
</li></ul><hr /><ul>
<li>
-<a href="index.html">Xalan-J 2.7.2</a>
+<a href="index.html">Xalan-J 2.7.3</a>
</li>
<li>
<a href="charter.html">Charter</a>
diff --git a/xalan-j/samples.html b/xalan-j/samples.html
index 3e53c79..2f712da 100644
--- a/xalan-j/samples.html
+++ b/xalan-j/samples.html
@@ -75,7 +75,7 @@
<a href="http://xalan.apache.org/index.html">Home</a>
</li></ul><hr /><ul>
<li>
-<a href="index.html">Xalan-J 2.7.2</a>
+<a href="index.html">Xalan-J 2.7.3</a>
</li>
<li>
<a href="charter.html">Charter</a>
diff --git a/xalan-j/trax.html b/xalan-j/trax.html
index f60caa7..01fbc27 100644
--- a/xalan-j/trax.html
+++ b/xalan-j/trax.html
@@ -75,7 +75,7 @@
<a href="http://xalan.apache.org/index.html">Home</a>
</li></ul><hr /><ul>
<li>
-<a href="index.html">Xalan-J 2.7.2</a>
+<a href="index.html">Xalan-J 2.7.3</a>
</li>
<li>
<a href="charter.html">Charter</a>
diff --git a/xalan-j/usagepatterns.html b/xalan-j/usagepatterns.html
index 88cecbd..d093da2 100644
--- a/xalan-j/usagepatterns.html
+++ b/xalan-j/usagepatterns.html
@@ -75,7 +75,7 @@
<a href="http://xalan.apache.org/index.html">Home</a>
</li></ul><hr /><ul>
<li>
-<a href="index.html">Xalan-J 2.7.2</a>
+<a href="index.html">Xalan-J 2.7.3</a>
</li>
<li>
<a href="charter.html">Charter</a>
diff --git a/xalan-j/whatsnew.html b/xalan-j/whatsnew.html
index 3354e5f..381f756 100644
--- a/xalan-j/whatsnew.html
+++ b/xalan-j/whatsnew.html
@@ -75,7 +75,7 @@
<a href="http://xalan.apache.org/index.html">Home</a>
</li></ul><hr /><ul>
<li>
-<a href="index.html">Xalan-J 2.7.2</a>
+<a href="index.html">Xalan-J 2.7.3</a>
</li>
<li>
<a href="charter.html">Charter</a>
@@ -162,71 +162,13 @@
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
-<h3>What's new in Xalan-Java Version 2.7.2</h3>
+<h3>Xalan-Java's latest version is 2.7.3, released in April 2023</h3>
<p>
- Here's what new in Xalan-Java Version 2.7.2.
+ Please read the Xalan-J release notes, within these documentation pages, to know what new improvements are
+ available within Xalan-J 2.7.3.
</p>
-
- <p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h4>Fix for CVE-2014-0107 insufficient secure processing</h4>
- <p>
- When using FEATURE_SECURE_PROCESSING ("http://javax.xml.XMLConstants/feature/secure-processing") on a TransformerFactory, the output properties:
- </p>
- <ul>
- <li>{http://xml.apache.org/xalan}content-handler</li>
- <li>{http://xml.apache.org/xalan}entities</li>
- <li>{http://xml.apache.org/xslt}content-handler</li>
- <li>{http://xml.apache.org/xslt}entities</li>
- </ul>
- <p>
- should be ignored (see http://xml.apache.org/xalan-j/usagepatterns.html#outputprops)
- </p>
- <p>
- These properties can be used to load an arbitrary class or access an arbitrary URL/resource so are problematic when secure processing is desired.
- </p>
- <p>
- <code>
- <xsl:output xalan:content-handler="org.example.BadClass" ...
- </code>
- </p>
- <p>
- <code>
- <xsl:output xalan:entities="http://example.org/reallyLargeFile.bin" ...
- </code>
- </p>
- <p>
- These features could be used to load a class that had undesirable side-effects or to load a large file and exhaust memory, etc.
- </p>
- <p>
- See <a href="#https://issues.apache.org/jira/browse/XALANJ-2435">XALANJ-2435</a>.
- </p>
-
-
- <p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h4>Upgrade to Xerces-J 2.11.0 and XML Commons External 1.4.01</h4>
- The distributions contain upgraded versions of <code>xercesImpl.jar</code>
- (Xerces-J 2.11.0) and <code>xml-apis.jar</code> (XML Commons External 1.4.01).
-
-
- <p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h4>Bug fixes</h4>
- Xalan-Java Version 2.7.2 contains performance enhancements and other bug fixes since 2.7.1. You can find the list
- in <a href="readme.html#notes_latest">the release notes</a>.
-
-
-
-
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
</div>
-<div id="footer">Copyright © 1999-2014 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Thu 2014-05-15</div>
+<div id="footer">Copyright © 1999-2023 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Thu 2023-04-04</div>
</div>
</body>
</html>
diff --git a/xalan-j/xpath_apis.html b/xalan-j/xpath_apis.html
index 0ded892..0546d06 100644
--- a/xalan-j/xpath_apis.html
+++ b/xalan-j/xpath_apis.html
@@ -75,7 +75,7 @@
<a href="http://xalan.apache.org/index.html">Home</a>
</li></ul><hr /><ul>
<li>
-<a href="index.html">Xalan-J 2.7.2</a>
+<a href="index.html">Xalan-J 2.7.3</a>
</li>
<li>
<a href="charter.html">Charter</a>
diff --git a/xalan-j/xsltc_history.html b/xalan-j/xsltc_history.html
index 145e807..8f84872 100644
--- a/xalan-j/xsltc_history.html
+++ b/xalan-j/xsltc_history.html
@@ -75,7 +75,7 @@
<a href="http://xalan.apache.org/index.html">Home</a>
</li></ul><hr /><ul>
<li>
-<a href="index.html">Xalan-J 2.7.2</a>
+<a href="index.html">Xalan-J 2.7.3</a>
</li>
<li>
<a href="charter.html">Charter</a>
diff --git a/xalan-j/xsltc_usage.html b/xalan-j/xsltc_usage.html
index 9f1d923..e9cc336 100644
--- a/xalan-j/xsltc_usage.html
+++ b/xalan-j/xsltc_usage.html
@@ -75,7 +75,7 @@
<a href="http://xalan.apache.org/index.html">Home</a>
</li></ul><hr /><ul>
<li>
-<a href="index.html">Xalan-J 2.7.2</a>
+<a href="index.html">Xalan-J 2.7.3</a>
</li>
<li>
<a href="charter.html">Charter</a>
