You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xalan.apache.org by sh...@apache.org on 2012/09/28 23:26:07 UTC
svn commit: r1391665 [3/4] - in /xalan/c/branches/GSoC-2012/xdocs: ./
sources/ sources/xalan/ style/dtd/ style/stylesheets/
Modified: xalan/c/branches/GSoC-2012/xdocs/sources/xalan/overview.xml
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xalan/overview.xml?rev=1391665&r1=1391664&r2=1391665&view=diff
==============================================================================
--- xalan/c/branches/GSoC-2012/xdocs/sources/xalan/overview.xml (original)
+++ xalan/c/branches/GSoC-2012/xdocs/sources/xalan/overview.xml Fri Sep 28 21:26:05 2012
@@ -36,7 +36,7 @@
discussion groups, frequently asked questions, and tutorials on XSLT, see <link anchor="uptospeed">Getting up to speed with
XSLT</link>.</p>
<note>XSL also includes a vocabulary for formatting documents, which is not part of &xslt4c;. For more information, see
- <resource-ref idref="XSL"/> and the <jump href="http://xml.apache.org/fop">Apache XML FOP (Formatting Objects Project)
+ <resource-ref idref="XSL"/> and the <jump href="http://xmlgraphics.apache.org/fop">Apache XML FOP (Formatting Objects Project)
</jump>.
</note>
<p>You use the XSLT language to compose XSL stylesheets. An XSL stylesheet contains instructions for transforming XML documents
@@ -68,7 +68,7 @@
<ul>
<li>&xslt4c; fully implements the <resource-ref idref="XSLT"/>.</li>
<li>&xslt4c; incorporates the <resource-ref idref="XPath"/>.<br/><br/></li>
- <li>&xslt4c; uses <jump href="http://xml.apache.org/xerces-c/index.html">&xml4c;</jump> to parse XML documents and XSL
+ <li>&xslt4c; uses <jump href="http://xerces.apache.org/xerces-c/index.html">&xml4c;</jump> to parse XML documents and XSL
stylesheets.<br/><br/>
The input may appear in the form of a file or URL, a stream, or a <resource-ref idref="DOM"/>.
&xslt4c; performs the transformations specified in the XSL stylesheet and produces a file, a stream, or a DOM as you
@@ -82,7 +82,7 @@
<anchor name="towork"/>
<s2 title="Getting to work with &xslt4c;">
<p>For instructions and some suggestions about how to get started using &xslt4c;, see <link idref="download">Downloading &xslt4c;</link>,
- <link idref="build_instruct">Building &xslt4c;</link>, and <link idref="install">Installing &xslt4c;</link>.</p>
+ <link idref="buildlibs">Building &xslt4c;</link>, and <link idref="install">Installing &xslt4c;</link>.</p>
</s2>
<anchor name="uptospeed"/>
@@ -90,32 +90,16 @@
<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
- <jump href="http://www.brics.dk/~amoeller/XML/">The XML Revolution: Technologies for the future Web</jump> by
- Anders Møller and Michael I. Schwartzbach (Web pages, but designed for sequential reading)</li>
<li>Crane Softwright's <jump href="http://www.CraneSoftwrights.com/training/">Free preview of Practical
Transformation Using XSLT and XPath</jump><br/><br/></li>
- <li>Doug Tidwell's <jump href="http://www.oreilly.com/catalog/xslt/">XSLT</jump>, O'Reilly, 2001<br/><br/></li>
+ <li>Doug Tidwell's <jump href="http://www.oreilly.com/catalog/xslt/">XSLT</jump>, O'Reilly, 2001<br/><br/> </li>
<li>Bob DuCharme's <jump href="http://www.manning.com/ducharme/index.html">XSLT Quickly</jump>, Manning Publications,
2001<br/><br/></li>
<li>John Robert Gardner and Zarella Rendon's
<jump href="http://vig.prenhall.com/catalog/academic/product/1,4096,0130404462,00.html">XSLT and XPath: A Guide to
Transformations</jump>, Prentice-Hall, 2001<br/><br/></li>
- <li>Michael Kay's <jump href="http://www.wrox.com/Books/Book_Details.asp?ISBN=1861005067">XSLT Programmer's
- Reference</jump>, 2nd ed., Wrox Press, 2001<br/><br/></li>
- <!--
- <li>Steven Holzner's <jump href="http://www.newriders.com/books/title.cfm?isbn=0735711364">Inside XSLT</jump>,
- New Riders, 2001<br/><br/></li>
- -->
- <li>Neil Bradley's <jump href="http://www.aw-bc.com/catalog/academic/product/0,1144,0201770830,00.html">XSL Companion</jump>,
- Addison-Wesley, 2000<br/><br/></li>
- <!--
- <li>Khun Yee Fung's <jump href="http://www.awlonline.com/product/0,2627,0201711036,00.html">XSLT: Working with XML and
- HTML</jump>, Addison-Wesley, 2001<br/><br/></li>
- -->
- <li>Dave Pawson's <resource-ref idref="dpawsonxslfaq"/> to search out particular answers and techniques<br/><br/></li>
- <li>Miloslav Nic's <jump href="http://zvon.vscht.cz/HTMLonly/XSLTutorial/Books/Book1/index.html">XSL Tutorial</jump>,
- a collection of stylesheet examples<br/><br/></li>
+
+
<li>Elliotte Rusty Harold's <jump href="http://www.ibiblio.org/xml/books/bible2/chapters/ch17.html">Chapter 17 of
the XML Bible: XSL Transformations</jump><br/><br/></li>
<li>The Mulberry <jump href="http://www.mulberrytech.com/xsl/xsl-list/">XSL-List -- Open Forum on XSL</jump>
@@ -123,12 +107,16 @@
<li>Objects by Design's <jump href="http://www.objectsbydesign.com/projects/xmi_to_html.html">Transforming XMI to
HTML</jump> (oriented towards XMI, "an XML-based, stream representation of a UML model," but also covers "generic"
XML transformations) and their related <jump href="http://objectsbydesign.com/projects/xslt/xslt_by_example.html">XSLT
- by Example</jump><br/><br/></li>
+ by Example</jump><br/><br/></li>
+
<li>OASIS (the Organization for the Advancement of Structured Information Standards):
<jump href="http://www.oasis-open.org/cover/xsl.html">Extensible Stylesheet Language (XSL)</jump> by Robin
Cover<br/><br/></li>
- <li>Donald Ball's <jump href="http://www.webslingerZ.com/balld/xsl/designer_manual.xml">A Guide to XML and XSL for
- Designers</jump><br/><br/></li>
+ <li>Aaron Skonnard and Martin Gudgin's
+<jump href="http://www.theserverside.net/tt/books/addisonwesley/EssentialXML/index.tss">Essential
+XML Quick Reference:</jump> A Programmer's Reference to
+XML, XPath, XSLT, XML Schema, SOAP and More. This reference is published by Addison Wesley, 2003, ISBN/0201740958.<br/><br/></li>
+
</ul>
<p>When you come across other useful introductory or background materials, please email <human-resource-ref
idref="xalandev"/>, so we can add them to this list.</p>
Modified: xalan/c/branches/GSoC-2012/xdocs/sources/xalan/programming.xml
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xalan/programming.xml?rev=1391665&r1=1391664&r2=1391665&view=diff
==============================================================================
--- xalan/c/branches/GSoC-2012/xdocs/sources/xalan/programming.xml (original)
+++ xalan/c/branches/GSoC-2012/xdocs/sources/xalan/programming.xml Fri Sep 28 21:26:05 2012
@@ -27,20 +27,19 @@
<anchor name="intro"/>
<s2 title="Introduction">
<p>This section was created to guide users on how to use some of the new features going into the Xalan
-source code base. Some of the features discussed in this section was based on feedback and questions
-posted on the xalan-c-users newsgroup postings. This section will cover the benefits of certain features
+source code base. Some of the features discussed in this section are based on feedback and questions
+posted on the xalan-c-users newsgroup. This section will cover the benefits of certain features
and provide users with programming hints on how to utilize the features in their applications.</p>
</s2>
<anchor name="memory"/>
<s2 title="Pluggable Memory Management">
-<p>Pluggable memory management was added as a new feature in &xslt4c-current;. This feature introduces an
+<p>Pluggable memory management was added as a new feature in Xalan-C Version 1.8;. This feature introduces an
object called MemoryManager which allows applications with stricter memory management requirements to
utilize a more efficient allocation method. This MemoryManager object can be applied to
each processor instance, thus recovery procedures from memory leaks or processor crashes will be applied to
the associated instance only.</p>
-<p>The memory management model is similar to the memory management feature provided by &xml4c;. For more
-information on the &xml4c; memory management feature, please see <resource-ref idref="xercesmm"/>.</p>
+<p>The memory management model is similar to the memory management feature provided by the Xerces-C XML Parser.</p>
<s3 title="How To Use This Feature">
<p>To apply memory management to your application, the MemoryManager object needs to be specified in two
stages:</p>
@@ -87,6 +86,8 @@ SimpleTransform</link> sample that has b
<anchor name="more"/>
<s2 title="More Topics">
-<p>Please feel free to give us feedback on what topics you would like to see</p>
+<p>Please feel free to give us feedback on what topics you would like to see.</p>
+<p>Send comments to <human-resource-ref idref="xalandev"/>.</p>
+
</s2>
</s1>
Modified: xalan/c/branches/GSoC-2012/xdocs/sources/xalan/readme.xml
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xalan/readme.xml?rev=1391665&r1=1391664&r2=1391665&view=diff
==============================================================================
--- xalan/c/branches/GSoC-2012/xdocs/sources/xalan/readme.xml (original)
+++ xalan/c/branches/GSoC-2012/xdocs/sources/xalan/readme.xml Fri Sep 28 21:26:05 2012
@@ -59,10 +59,10 @@
<anchor name="bugs"/>
<s3 title="Bug reporting">
- <p>All known &xslt4c; bugs are listed in <resource-ref idref="bugzilla"/>. For a list of open bugs with links to each bug
+ <p>All known &xslt4c; bugs are listed in <resource-ref idref="jira"/>. For a list of open bugs with links to each bug
report, see <resource-ref idref="buglist"/>. If you find a new bug, please enter a XalanC bug report in this
database.</p>
- <note>Before you can enter your first bug report, you must submit your email address to Bugzilla and receive a password.</note>
+ <note>Before you can enter your first bug report, you must submit your email address to Jira and receive a password.</note>
<p>We strongly encourage you write patches for problems you find and submit them to
xalan-dev@xml.apache.org. We review the patches we receive to make sure they do not break something else, and (assuming they
do not) include them in our next release. In the interest of fixing bugs, adding enhancements, and addressing outstanding design
Added: xalan/c/branches/GSoC-2012/xdocs/sources/xalan/releasenotes.xml
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xalan/releasenotes.xml?rev=1391665&view=auto
==============================================================================
--- xalan/c/branches/GSoC-2012/xdocs/sources/xalan/releasenotes.xml (added)
+++ xalan/c/branches/GSoC-2012/xdocs/sources/xalan/releasenotes.xml Fri Sep 28 21:26:05 2012
@@ -0,0 +1,337 @@
+<?xml version="1.0" standalone="no"?>
+<!DOCTYPE s1 SYSTEM "../../style/dtd/document.dtd"[
+<!ENTITY done-c SYSTEM "DONE">
+<!ENTITY status-c SYSTEM "STATUS">
+<!ENTITY history-c SYSTEM "history.xml">]>
+
+<!--
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+-->
+<s1 title="&xslt4c; Release Notes">
+<p>Release notes for &xslt4c-current;</p>
+ <ul>
+ <li><link anchor="status">Status</link></li>
+ <li><link anchor="build">Rebuilding &xslt4c; and the sample applications</link></li>
+ <li><link anchor="contact">Getting in touch</link></li>
+ <li><link anchor="history">History of software changes</link></li>
+ </ul>
+ <anchor name="status"/>
+ <s2 title="Status">
+ <ul>
+ <li><link anchor="done">Changes for &xslt4c; version 1.8</link></li>
+ <li><link anchor="bugs">Bug reporting</link></li>
+ <li><link anchor="xml4c">Version of &xml4c; to use</link></li>
+ <li><link anchor="to-do">To-do tasks for future &xslt4c; releases</link></li>
+ </ul>
+ <anchor name="done"/>
+ <s3 title="Changes for &xslt4c; version 1.8">
+ <p>Major updates since version 1.7 include:</p>
+ <ul>
+ <li><resource-ref idref="bugsfixedforthisrelease"/>.</li>
+ <li>Upgrade from Xerces-C 2.4 to Xerces-C 2.5. </li>
+ <li>Provide build support for Cygwin and HP-UX 11.00 on Itanium. Although binary distributions are not provided for the Cygwin environment and
+ HP-UX 11.00 on Itanium platform, the build configuration files provided in the source distribution can be used to build on these platforms. </li>
+ <li>Project files for supporting Microsoft Visual Studio .NET. Although a binary distribution for the Microsoft Visual Studio .NET
+ is not provided in this release, Visual Studio solution files are provided in the Windows source distribution for those who choose to build
+ on this platform. Please see <link anchor="dotNet">"Step for doing a Windows Build with Visual Studio .NET"</link> for details.</li>
+ <li>Additional changes to Xerces Deprecated DOM support. This is another step towards phasing out the support for Xerces Deprecated DOM. Users are encouraged to modify their applications to interface with the new Xerces DOM support. For more information on the effects of these changes to your build environment, please see <link anchor="xercesdepdom">"Steps for doing a Build with Xerces Deprecated DOM Support"</link></li>
+ <!--
+ <li>Porting of conf utility to the UNIX platform. The conf utility is a test harness designed to run the conformance tests located under the xml-xalan/test/tests directory. After the tests have been run, a results report is generated in HTML format for easy viewing. For more information on how to use this tool, please see <link idref="commandline" anchor="confexe">"Using the command line utility"</link>.</li>
+ -->
+ <li>Implemented optimizations to significantly improve the throughput of the ICU-enabled "format-number" function.</li>
+ <li>Changes in the XML Serializer. The serializer will no longer put a newline after the xml header tag unless indent="yes". See bugzilla <jump href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24304">24304</jump> and <jump href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=28386">28386</jump>.</li>
+ </ul>
+ </s3>
+
+ <anchor name="bugs"/>
+ <s3 title="Bug reporting">
+ <p>All known &xslt4c; bugs are listed in <resource-ref idref="jira"/>. For a list of open bugs with links to each bug
+ report, see <resource-ref idref="buglist"/>. If you find a new bug, please enter a XalanC bug report in this
+ database.</p>
+ <note>Before you can enter your first bug report, you must submit your email address to Jira and receive a password.</note>
+ <p>We strongly encourage you write patches for problems you find and submit them to
+ xalan-dev@xml.apache.org. We review the patches we receive to make sure they do not break something else, and (assuming they
+ do not) include them in our next release. In the interest of fixing bugs, adding enhancements, and addressing outstanding design
+ issues, we sincerely want (and need!) your active participation in the ongoing development of Xalan.</p>
+ </s3><anchor name="xml4c"/>
+ &status-c;
+ </s2><anchor name="build"/>
+ <s2 title="Rebuilding &xslt4c;">
+<ul>
+<li><link anchor="jar">Rebuilding &xslt4c;</link></li>
+<li><link anchor="samples">Rebuilding sample applications</link></li>
+</ul>
+<anchor name="jar"/>
+ <s3 title="Rebuilding &xslt4c;">
+ <ul>
+ <li><link anchor="needed">What you need from the distributions</link></li>
+ <li><link anchor="win32">Steps for doing a Windows Build</link></li>
+ <li><link anchor="dotNet">Steps for doing a Windows Build with Visual Studio .NET</link></li>
+ <li><link anchor="unix">Steps for doing a UNIX build</link></li>
+ <li><link anchor="locale">Steps for doing a Build with Message Localization Support</link></li>
+ <li><link anchor="xercesdepdom">Steps for doing a Build with Xerces Deprecated DOM Support</link></li>
+ </ul></s3><anchor name="needed"/>
+ <s3 title="What you need from the distributions">
+ <p>To rebuild &xslt4c;, you need the &xslt4c; source files, the &xml4c; header files, and
+ for Windows the &xml4c; .lib file. If you want to rebuild with the ICU, you will need to download the ICU source package to build the ICU libraries. </p>
+
+<note>You can also download &xslt4c; source distributions from <resource-ref idref="xslt4c-distdir"/>: &xslt4c-dist;-src.zip and &xslt4c-dist;-src.tar.gz. &xml4c; source distributions are available from <resource-ref idref="xml4c-distdir"/>:
+&xml4c-dist;-src.zip and &xml4c-dist;-src.tar.gz.</note>
+<p>Keep in mind that at any given point in time the &xslt4c; and &xml4c; source trees in the Apache XML repository may not be consistent. When we release a version of &xslt4c; we certify that it is compatible with a given version of &xml4c;. To be safe, use the Xerces distributions that we certify as compatible. Reminder: &xslt4c-current; is compatible with &xml4c-used;.</p>
+ <p>For information on using the <resource-ref idref="icu"/>, see
+ <link idref="usagepatterns" anchor="icu">Using the ICU</link>.
+ The recommended version of ICU for &xslt4c-current; is &icu-current;. You may be able to use newer ICU releases as they appear.</p>
+ </s3><anchor name="win32"/>
+ <s3 title="Steps for doing a Windows build">
+ <p>To build &xslt4c; on Windows, you need &xml4c; and MS Visual C++ 6.0 installed with Service Pack 5 for Visual C++ and Visual Studio .NET.</p>
+ <p>If you are using a different Service Pack, you must rebuild all of the Xerces and Xalan binaries.</p>
+<p>Before you do the following, be sure you have <link idref="getstarted" anchor="windowspath">provided Visual C++ the paths to the Xerces headers and libraries</link>.</p>
+ <ol>
+ <li>Create the ICUROOT environment variable and set it the the path of the ICU root.</li>
+ <li>Create the XERCESCROOT environment variable and set it to the path of the root of &xml4c;.</li>
+ <li>Use Visual C++ to open the Xalan workspace (.dsw) from the &xslt4c-win_root;\Projects\Win32\VC6. If you are building with ICU, then use XalanICU.dsw. Otherwise, open the Xalan.dsw workspace.<br/><br/>
+ <note>You may need to restart Visual Studio .NET in order for ICUROOT and XERCESCROOT to take effect.</note>
+ <br/>
+ As an alternative method to the steps described above, would be to go to "Tools" and select "Options" from Visual C++. From the "Options" window, click on the "Directories" tab and do the following:
+ <ol>
+ <li>Show Directories for: Executable files. Add the Xerces bin directory to the list.</li>
+ <li>Show Directories for: Include files. Add the Xerces include directory to the list. If you are building with ICU, add the ICU include directory to the list as well.</li>
+ <li>Show Directories for: Library files. Add the Xerces lib directory to the list. If you are building with ICU, add the ICU lib directory to the list as well.</li>
+ </ol></li>
+ </ol>
+ <note>To recompile existing applications without changing your source code, be sure to modify your Project settings to pick up the Xalan headers in its new location. (see image below)</note>
+ <p><img src="options-sane.gif" alt="Visual C++ 6.0 Include Directories change"/></p>
+</s3>
+<anchor name="dotNet"/>
+<s3 title="Steps for doing a Windows Build with Microsoft Visual Studio .NET">
+ <p>For users who want to build with Visual Studio .NET,</p>
+ <ol>
+ <li>Create the ICUROOT environment variable and set it the the path of the ICU root.</li>
+ <li>Create the XERCESCROOT environment variable and set it to the path of the root of &xml4c;.</li>
+ <li>Use Visual Studio .NET to open the Xalan solution (.sln) from the &xslt4c-win_root;\Projects\Win32\VC7. If you are building with ICU, then use XalanICU.sln. Otherwise, open the Xalan.sln solution file.<br/><br/>
+ <note>You may need to restart Visual Studio .NET in order for ICUROOT and XERCESCROOT to take effect.</note>
+ <br/>
+ An alternative method to the steps described above, would be to go to "Tools" and select "Options" from Visual Studio .NET. From the "Options" window, click on the "Projects" folder to expand the list. Select "VC++ Directories" from the list and do the following:
+ <ol>
+ <li>Show Directories for: Executable files. Add the Xerces bin directory to the list.</li>
+ <li>Show Directories for: Include files. Add the Xerces include directory to the list. If you are building with ICU, add the ICU include directory to the list as well.</li>
+ <li>Show Directories for: Library files. Add the Xerces lib directory to the list. If you are building with ICU, add the ICU lib directory to the list as well.</li>
+ </ol></li>
+ </ol>
+ <note>To recompile existing applications without changing your source code, be sure to modify your Project settings to pick up the Xalan headers in its new location. (see image below)</note>
+ <p><img src="NET_options.jpg" alt="Visual Studio .NET Include Directories change"/></p>
+ </s3><anchor name="unix"/>
+<s3 title="Steps for doing a UNIX build">
+ <p>For users who want to build in the UNIX environment,</p>
+ <ol>
+ <li>The Xalan build files are written for GNU make, and will not work with other make utilities.<br/><br/></li>
+ <li>Set the XERCESCROOT environment variable to the path to the root of &xml4c;.<br/><br/></li>
+ <li>Set the XALANCROOT environment variable to the path to the c directory in the root of the &xslt4c;
+ distribution. For example, if the distribution is located in "/home/mydir", you would set the XALANCROOT to "/home/mydir/&xslt4c-unix_root;". <br/><br/></li>
+ <li>(Optional) If you are including the ICUBridge, install the ICU, use the shell to define XALAN_USE_ICU and to set the ICUROOT environment variable to the path to the ICU root. For more information, see (see <link idref="usagepatterns" anchor="icu">Using the ICU</link>). Note that building Xalan with ICU requires that Xerces must also be built with ICU.<br/><br/></li>
+ <li>Change directory to XALANCROOT. You can also
+ build Xalan-C outside of the source tree, but you will need to adjust the path to the
+ runConfigure script in the next step.<br/><br/></li>
+ <li>Run the runConfigure utility and provide the platform, C compiler, and C++ compiler flags as
+ indicated below. The runConfigure utility is used to generate the appropriate Makefile for
+ the desired build platform based on the options specified by the user. Valid options for the
+ runConfigure utility are:<br/><br/>
+ <code>./runConfigure -p <value> -c <value> -x <value> [-[flag] <value>]</code><br/><br/>
+ <table>
+ <tr><th>flag</th><th>Description</th></tr>
+ <tr><td>p</td><td>Build platform. Option must be provided by user. Valid values <br/>include:
+ aix, linux, freebsd, netbsd, solaris, hp-10, hp-11, hp-11-ia64, irix,<br/> tru64, macosx, cygwin. </td></tr>
+ <tr><td>c</td><td>C compiler name. Example: gcc, cc, c89, xlc_r, etc.</td></tr>
+ <tr><td>x</td><td>C++ compiler name. Example: g++, xlC_r, CC, etc.</td></tr>
+ <tr><td>d</td><td>Indicates build is a debug build. Takes no values. Default is no <br/>debug.</td></tr>
+ <tr><td>t</td><td>Transcoder to use. Valid value is 'icu'. Default is null.</td></tr>
+ <tr><td>m</td><td>Type of localization support method. Valid values include: inmem, <br/>icu, and nls.
+ Default is inmem.</td></tr>
+ <tr><td>M</td><td>Locale for Message Localization Support. Default is "en_US"</td></tr>
+ <tr><td>r</td><td>Threads option. Valid values include: pthread or dce. Default is <br/>dce</td></tr>
+ <tr><td>b</td><td>Specify whether it is a 32-bit or 64-bit build. Valid values are 32 <br/>and 64.
+ Default is 32-bit</td></tr>
+ <tr><td>P</td><td>Install root directory. Used if invoking build with gmake install or <br/>gmake
+ install-package. Default install root directory is /usr/local</td></tr>
+ <tr><td>l</td><td>Extra link options other than the default. Default is null</td></tr>
+ <tr><td>z</td><td>Extra compiler options other than the default. Default is null</td></tr>
+ <tr><td>C</td><td>Extra configuration options.</td></tr>
+ <tr><td>h</td><td>To get help on the above commands. Default is no help.</td></tr>
+ </table><br/>
+ <ref>Linux using GCC:</ref> <code>./runConfigure -p linux -c gcc -x c++</code><br/>
+ <ref>Linux using the Intel compiler:</ref> <code>./runConfigure -p linux -c icc -x icpc</code><br/>
+ <ref>AIX (32-bit):</ref> <code>./runConfigure -p aix -c xlc_r -x xlC_r</code><br/><br/>
+ <ref>AIX (64-bit):</ref> <code>./runConfigure -p aix -c xlc_r -x xlC_r -b 64</code><br/><br/>
+ <ref>Cygwin (32-bit):</ref> <code>./runConfigure -p cygwin -c gcc -x g++</code><br/><br/>
+ <ref>HP-UX 11 (32-bit):</ref> <code>./runConfigure -p hp-11 -c cc -x aCC</code><br/><br/>
+ <ref>HP-UX 11 (64-bit):</ref> <code>./runConfigure -p hp-11 -c cc -x aCC -b 64</code><br/><br/>
+ <ref>HP-UX 11 for Itanium (32-bit):</ref> <code>./runConfigure -p hp-11-ia64 -c cc -x aCC</code><br/><br/>
+ <ref>HP-UX 11 for Itanium (64-bit):</ref> <code>./runConfigure -p hp-11-ia64 -c cc -x aCC -b 64</code><br/><br/>
+ <ref>Solaris (32-bit):</ref> <code>./runConfigure -p solaris -c cc -x CC</code><br/><br/>
+ <ref>Solaris (64-bit):</ref> <code>./runConfigure -p solaris -c cc -x CC -b 64</code><br/><br/>
+ If you choose to install the distribution after building the libraries and executables,
+ then you will need to indicate where you would like the distribution to be installed.
+ To specify the install directory for your distribution, specify the flag -P <install directory>.
+ For example, building and installing on the AIX platform:<br/><br/>
+ <code>./runConfigure -p aix -c xlc_r -x xlC_r -P $HOME/my_xalan</code><br/><br/>
+ <note>The standard binary directories bin, lib, and include are created in the specified directory only if the install or install-package option is
+ specified in the build process.<br/><br/></note>
+ To see the other runConfigure flags you may include, use the help flag:<br/><br/>
+ <code>./runConfigure -h</code><br/><br/></li>
+ <li>Purge the previous build:<br/><br/>
+ <code> make clean</code><br/><br/></li>
+ <li>Run the new build:<br/><br/>
+ <code>make</code><br/>
+ or<br/>
+ <code>make <ref>targ</ref></code><br/><br/>
+ where <ref>targ</ref> can be one of:
+ <table>
+ <tr><th>targ</th><th>Description</th></tr>
+ <tr><td>all</td><td>Build the libraries and Xalan executable. This is the default target <br/>if no targ
+ is specified.</td></tr>
+ <tr><td>clean</td><td>Deletes existing binaries, executables, libraries, tests, and <br/>samples.</td></tr>
+ <tr><td>install</td><td>Build the library, executables and copy them (along with <br/>the header files)
+ the specified install location.</td></tr>
+ <tr><td>install-package</td><td>Installs the library, executables, samples to the <br/>specified location.</td></tr>
+ <tr><td>Samples</td><td>Builds the samples.</td></tr>
+ <tr><td>Tests</td><td>Builds the tests.</td></tr>
+ </table>
+ </li>
+ </ol>
+ <note>To recompile existing applications without changing your source code, be sure to modify the command line in your Makefile to pick up the Xalan headers from it's new location. e.g: if your xalan source location is in /home/&xslt4c-unix_root;,</note><p>
+ <br/> <code>CC ... -I/home/&xslt4c-unix_root;/src -I/home/&xslt4c-unix_root;/src/xalanc mysrc.cpp</code><anchor name="64"/></p>
+ </s3>
+ <anchor name="locale"/>
+ <s3 title="Steps for doing a Build with Message Localization Support">
+ <p>Message Localization Support is a new feature to allow users to build &xslt4c; such that
+ diagnostic messages are issued in the language of their choice. Message localization support
+ comes in three flavours:</p>
+ <ul>
+ <li>Building static messages in the form of a library (DLL or shared object) which can be bound
+ to the Xalan executable. This method is referred to as "in memory". By default, &xslt4c; is built using "in memory" method.
+ </li>
+ <li>Building messages in the form of a library using localization support provided by the
+ International Components for Unicode (ICU). </li>
+ <li>Building messages in the form of a message catalog. This method utilizes the localization
+ support provided by the Unix National Language Support (NLS) system. This method is supported
+ for UNIX platforms only. </li>
+ </ul>
+ <p>Regardless of which method you choose, a message file containing translated messages in the
+ language of your choice must be provided. The standard message file provided in the &xslt4c;
+ version 1.8 source package is in XML Localization Interchange File Format (XLIFF) format
+ and conforms to the XLIFF 1.1 standard (please see
+ <jump href="http://www.oasis-open.org/committees/xliff/documents/xliff-specification.htm">
+ http://www.oasis-open.org/committees/xliff/documents/xliff-specification.htm</jump> for more
+ information.) All message files must be written and conform with the XLIFF 1.1 standard.</p>
+ <p>Once an XLIFF message file has been created, the XLIFF file should be stored under
+ &xslt4c-unix_root;/src/xalanc/NLS/<locale_name> directory (for example, the default XLIFF message file
+ provided is XalanMsg_en_US.xlf). To build, you will need to follow the same steps
+ as shown above for building in Unix or Windows but with a small change.</p>
+ <p>For building on Windows platform with "In Memory" method:</p>
+ <ol>
+ <li>Create the environment variable XERCESCROOT and set it to the path to the root of &xml4c;.</li>
+ <li>Create the environment variable ICUROOT and set it to the path to the ICU root.</li>
+ <li>Open the Xalan.dsw workspace using Microsoft Visual C++. The "inmem" localization method should be configured by default.</li>
+ <li>Select the Localization project, and go to Settings and click on the "General" tab.Verify
+ the build command line to use "nmake /f BuildMessages.mak TYPE=inmem LOCAL=en_US"</li>
+ <li>Run "Build all" with the configuration of your choice. </li>
+ </ol>
+ <p>For building on the Windows platform with ICU method:</p>
+ <ol>
+ <li>Create the environment variable XERCESCROOT and set it to the path to the root of &xml4c;.</li>
+ <li>Create the environment variable ICUROOT and set it to the path to the ICU root.</li>
+ <li>Open the XalanICU.dsw workspace using Microsoft Visual C++. </li>
+ <li>Select the AllInOneWithICU project, and ensure that the project depends on the LocalizationWithICU
+ project. </li>
+ <li>Select the LocalizationWithICU project, and go to Settings and click on the "General" tab. Modify
+ the build command line to use "nmake /f BuildMessages.mak TYPE=icu LOCAL=en_US"</li>
+ <li>Open the tools.ini file under Projects\Win32\VC6\Utils\Localization and add the ICU root
+ directory to the ICUROOT variable setting.</li>
+ <li>Run "Build all" with the configuration of your choice. </li>
+ </ol>
+ <p>For building on the Unix platform:</p>
+ <ol>
+ <li>Repeat steps 1 through 5 as outlined under "Steps for doing a UNIX Build" </li>
+ <li>Run the runConfigure and provide the platform, C compiler, C++ compiler, the message locale
+ system flavour you are intending to build, and the locale support.<br/><br/>
+ Example 1: to use the NLS method for localization support using the default locale en_US:<br/><br/>
+ <ref>AIX (32-bit):</ref> <code>./runConfigure -p aix -c xlc_r -x xlC -m nls</code><br/><br/>
+ <ref>AIX (64-bit):</ref> .<code>/runConfigure -p aix -c xlc_r -x xlC_r -b 64 -m nls</code><br/><br/>
+ Example 2: to use the 'icu' method for localization support using the locale fr_FR:<br/><br/>
+ <ref>AIX (32-bit):</ref> <code>./runConfigure -p aix -c xlc_r -x xlC_r -m icu -M fr_Fr</code><br/><br/>
+ <ref>AIX (64-bit):</ref> <code>./runConfigure -p aix -c xlc_r -x xlC_r -b 64 -m icu -M fr_Fr</code><br/><br/>
+ </li>
+ <li>Perform steps 7 and 8 as outlined under "Steps for doing a UNIX Build" </li>
+ </ol>
+ <p>After &xslt4c; and associated libraries have been successfully built, the message catalog
+ will be stored in the directory &xslt4c-unix_root;/bin.<br/><br/>
+ <table>
+ <tr><th>Localization Build Type</th><th>File Name</th></tr>
+ <tr><td><ref>ICU or "in memory" method:</ref></td><td>libxalanMsg18.so (for UNIX)<br/>
+ XalanMessages_1_8.dll and XalanMessages_1_8.lib (for Windows)
+ </td></tr>
+ <tr><td><ref>NLS method:</ref></td><td>xalanMsg1_8.cat can be found in $XALANCROOT/nls/<locale_name>/ directory</td></tr>
+ </table>
+ </p>
+ <p>The location of the message library, &xslt4c; and &xml4c; binaries need to be added to the PATH and
+ library path variables. Depending on the Message Localization Support method you've chosen, the
+ following steps will need to be performed such that &xslt4c; will be able to utilize the message
+ library. </p>
+ <ul>
+ <li>For an "in memory" or "icu" build, the location of the &xslt4c; and &xml4c; executables need to
+ be added to the PATH variable. The location of the message library will need to be added to:
+ <ul>
+ <li>the LIBPATH variable for AIX users </li>
+ <li>the LD_LIBRARY_PATH variable for RedHat, SuSE, and Solaris users </li>
+ <li>the SHLIB_PATH variable for HP-UX users. </li>
+ </ul></li>
+ <li>For an NLS build, the message catalog will need to be added to the NLSPATH. </li>
+ </ul>
+ </s3>
+ <anchor name="xercesdepdom"/>
+ <s3 title="Steps for doing a Build with Xerces Deprecated DOM Support">
+ <p>If you application is dependent on the XercesBridge classes to interface with the deprecated Xerces DOM, then the following steps must be taken.</p>
+ <p>For a Windows build using Microsoft Visual C++ version 6.0:</p>
+ <ol>
+ <li>Open the Xalan.dsw workspace</li>
+ <li>Go to "Projects" and select "Settings". From the "Project Settings panel", highlight the AllInOne project.</li>
+ <li>Click on the "C/C++" tab on the right hand side. From the "Category" pull down menu, scroll down to find "Preprocessor" and click to highlight this category.</li>
+ <li>Under the "Preprocessor Definitions" box, add "XALAN_BUILD_DEPRECATED_DOM_BRIDGE" to the list of definitions.</li>
+ <li>Rebuild &xslt4c; as described under <link anchor="win32">"Steps for doing a Windows Build"</link></li>
+ </ol>
+ <p>For a UNIX build, the following parameter should be added to your runConfigure step: <code>-z -DXALAN_BUILD_DEPRECATED_DOM_BRIDGE</code>. for example,</p>
+ <code>./runConfigure -p aix -c xlc_r -x xlC_r -z -DXALAN_BUILD_DEPRECATED_DOM_BRIDGE</code><br/><br/>
+
+ </s3>
+ <anchor name="samples"/>
+ <s3 title="Rebuilding a Sample application">
+ <p>In the 32-bit Windows distribution, all of the sample applications can be built from the Xalan.dsw Visual C++ workspace.</p>
+<p>The Makefile that come with the UNIX distributions include targets for rebuilding one or all of the sample applications . To rebuild one or more sample applications, go to the root directory of your source package or the samples directory of your binary package, and run<br/><br/>
+ <code>gmake <ref>Target</ref></code><br/><br/>
+where <ref>Target</ref> is <code>Samples</code> (all the samples), <code>ApacheModuleXSLT</code>, <code>CompileStylesheet</code>, <code>DocumentBuilder</code>, <code>ExternalFunctions</code>, <code>ParsedSourceWrappers</code>, <code>SerializedNodeSet</code>, <code>SimpleTransform</code>, <code>SimpleXPathAPI</code>, <code>SimpleXPathCAPI</code>, <code>StreamTransform</code>, <code>ThreadSafe</code> (Windows only), <code>TraceListen</code>, <code>TransformToXercesDOM</code>, <code>UseStylesheetParam</code>, <code>XPathWrapper</code>, <code>XalanTransform</code>, or <code>XalanTransformerCallback</code>.</p>
+<note>For information on building Apache Module, see <link idref="samples" anchor="apachemodulexslt">ApacheModuleXSLT</link></note>
+ </s3>
+ </s2><anchor name="contact"/>
+ <s2 title="Getting in Touch">
+ <p>Your feedback is more than welcome. Offers of help are even more so! Perhaps you would like to contribute to the ongoing development, testing, or documentation of &xslt4c;.</p>
+<p>Please email your comments, questions, suggestions, bug reports, and offers to help to <human-resource-ref idref="xalandev"/>.</p>
+ </s2><anchor name="history"/>
+ <s2 title="Cumulative history of software changes">
+ <p>The following sections list the changes in each release since &xslt4c; version 0.40.0.</p>
+ &history-c;
+ </s2>
+</s1>
Modified: xalan/c/branches/GSoC-2012/xdocs/sources/xalan/resources.xml
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xalan/resources.xml?rev=1391665&r1=1391664&r2=1391665&view=diff
==============================================================================
--- xalan/c/branches/GSoC-2012/xdocs/sources/xalan/resources.xml (original)
+++ xalan/c/branches/GSoC-2012/xdocs/sources/xalan/resources.xml Fri Sep 28 21:26:05 2012
@@ -34,16 +34,16 @@
<resource id="xslt4c-current"
title="&xslt4c-current;"
- location="http://xml.apache.org/xalan"/>
+ location="http://xalan.apache.org/xalan-c"/>
<resource id="xml4c-used"
title="&xml4c-used;"
- location="http://xml.apache.org/xerces-c/index.html"/>
+ location="http://xerces.apache.org/xerces-c/index.html"/>
<resource id="xslt4c-distdir"
title="Xalan-C downloads"
- location="http://www.apache.org/dyn/closer.cgi/xml/xalan-c"/>
+ location="http://www.apache.org/dyn/closer.cgi/xalan/xalan-c"/>
<resource id="xml4c-distdir"
title="Xerces-C downloads"
- location="http://www.apache.org/dyn/closer.cgi/xml/xerces-c/"/>
+ location="http://www.apache.org/dyn/closer.cgi/xerces/c"/>
<resource id="xslt4c-win32-download"
title="&xslt4c-dist;-win32.zip"
location="http://www.apache.org/dyn/closer.cgi/xml/xalan-c/binaries/&xslt4c-dist;-win32.zip"/>
@@ -73,8 +73,8 @@
title="STLport"
location="http://www.stlport.org/"/>
<resource id="ApacheLicense"
- title="The Apache Software License, Version 1.1"
- location="http://xml.apache.org/dist/LICENSE.txt"/>
+ title="The Apache Software License, Version 2.0"
+ location="http://www.apache.org/licenses/LICENSE-2.0"/>
<resource id="Readme"
title="Xalan Repository Release Notes"
location="http://www.apache.org/websrc/cvsweb.cgi/xml-xalan/README"/>
@@ -90,32 +90,34 @@
<resource id="DOM"
title="DOM"
location="http://www.w3.org/DOM"/>
-<resource id="dpawsonxslfaq"
- title="XSL Frequently Asked Questions"
- location="http://www.dpawson.co.uk/xsl/xslfaq.html"/>
<resource id="xercesmm"
title="Pluggable Memory Manager"
- location="http://xml.apache.org/xerces-c/program-others.html#PluggableMemoryManager"/>
+ location="http://xerces.apache.org/c/program-others.html#PluggableMemoryManager"/>
<human-resource id="xalandev"
name="Xalan Development Mailing List"
- mailto="xalan-dev@xml.apache.org"/>
-
+ mailto="dev@xalan.apache.org"/>
+
+<human-resource id="xalancusers"
+ name="Xalan-C/C++ Users Mailing List"
+ mailto="c-users@xalan.apache.org"/>
+
<resource id="bugzilla"
title="Bugzilla (the Apache bug database)"
location="http://nagoya.apache.org/bugzilla"/>
<resource id="jira"
title="JIRA (the Apache bug database)"
- location="http://nagoya.apache.org/jira"/>
+ location="https://issues.apache.org/jira/browse/XALANC"/>
<resource id="buglist"
title="XalanC open bugs"
- location="http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=XalanC&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&order=Reuse+same+sort+as+last+time"/>
+ location="https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+XALANC+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC"/>
<resource id="bugsfixedforthisrelease"
title="XalanC bugs fixed for this release"
- location="http://nagoya.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=10582&statusIds=1"/>
+ location="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10582&version=10833"/>
+
</resources>
Modified: xalan/c/branches/GSoC-2012/xdocs/sources/xalan/samples.xml
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xalan/samples.xml?rev=1391665&r1=1391664&r2=1391665&view=diff
==============================================================================
--- xalan/c/branches/GSoC-2012/xdocs/sources/xalan/samples.xml (original)
+++ xalan/c/branches/GSoC-2012/xdocs/sources/xalan/samples.xml Fri Sep 28 21:26:05 2012
@@ -119,8 +119,8 @@ package. </p>
has been completed.</p>
<note>You may need to adjust the Visual C++ or Makefile settings to locate the required Apache header files. As shipped, the Visual C++
project file looks in \Apache Group\Apache\src\include, and the UNIX Makefile looks in usr/lib.</note>
-<p>To build the Apache module, follow the instructions in <link idref="build_instruct" anchor="win32">Steps for doing a Windows
- build</link> or <link idref="build_instruct" anchor="unix">Steps for doing a UNIX build</link>. For UNIX platforms, you do the build with<br/>
+<p>To build the Apache module, follow the instructions in <link idref="buildlibs" anchor="winbldenv">Steps for doing a Windows
+ build</link> or <link idref="buildlibs" anchor="unixbldenv">Steps for doing a UNIX build</link>. For UNIX platforms, you do the build with<br/>
<code>gmake ApacheModuleXSLT</code>.</p>
<s3 title="Setting up and using ApacheModuleXSLT">
@@ -341,20 +341,37 @@ theProcessor.addTraceListener(&theTr
</s2>
<anchor name="usestylesheetparam"/>
-<s2 title="UseStylesheetParam">
-<p>What it does: Set a stylesheet parameter that the stylesheet uses during the transformation.</p>
+<s2 title="UseStylesheetParam">
+
+<p>What it does: Performs a transformation using top-level stylesheet parameters. There are three supported types of parameters. One is a text string. A second is a number of type double. A nodeset or parsed document can also be used.</p>
+
<p>You can run it from the UseStylesheetParam subdirectory with</p>
-<p><code>UseStylesheetParam <ref>key expression</ref></code></p>
-<p>where <ref>key</ref> is the parameter key (or name) and <ref>expression</ref> is a string expression enclosed
- in single quotes.</p>
-<p>The example uses a stylesheet (foo.xsl) with a parameter named param1. The stylesheet accepts any string
- expression. Enclose the string expression in single quotes (so it is interpreted as an expression); if it
- includes more than a single word, enclose the resulting string in double quotes so the executable interprets it
- as a single argument. For example:</p>
-<p><code>UseStylesheetParam param1 "'hello out there'"</code></p>
-<p>See also: <link idref="usagepatterns" anchor="params">Setting stylesheet parameters</link>.</p>
+
+<p><code>UseStylesheetParam <ref>xmlfile</ref> <ref>stylesheet</ref> <ref>outfile</ref> [options]</code></p>
+
+<p>where the options are:</p>
+
+<p><code> -s key "'String-Value'"</code><br/>
+<code> -n key Number</code><br/>
+<code> -d key "Document-URL"</code></p>
+
+<p>The files used by the sample program and the top-level parameter nodesets for this illustration are to be in working directory in which the sample program runs.</p>
+
+<p>Using the sample program:</p>
+
+<p><code>UseStylesheetParam foo.xml foo.xslt foo.out \<br/>
+ -s stringA "'This is a test string value'" \<br/>
+ -n numberA 123.012345 \<br/>
+ -d parmA "parmA.xml" \<br/>
+ -d parmB "parmB.xml"</code></p>
+
+<p>The <ref>parmA.xml</ref> and <ref>parmB.xml</ref> are parsed and converted to nodesets. The stylesheet <ref>foo.xslt</ref> merges the contents of <ref>foo.xml</ref> and the parameters into the <ref>foo.out</ref> file.</p>
+
+<p>The source sample is implemented in C++. Another example is implemented in 'C' using the XalanCAPI library <ref>TestCAPIparm.c</ref>. The usage interface for both is the same.</p>
+
+<p>See also: <link idref="usagepatterns" anchor="params">Setting stylesheet parameters</link>.</p>
</s2>
-
+
<anchor name="xalantransform"/>
<s2 title="XalanTransform">
<p>What it does: XalanTransform uses the XalanTransformer class and the associated C++ API to apply an XSL stylesheet
Added: xalan/c/branches/GSoC-2012/xdocs/sources/xalan/secureweb.xml
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xalan/secureweb.xml?rev=1391665&view=auto
==============================================================================
--- xalan/c/branches/GSoC-2012/xdocs/sources/xalan/secureweb.xml (added)
+++ xalan/c/branches/GSoC-2012/xdocs/sources/xalan/secureweb.xml Fri Sep 28 21:26:05 2012
@@ -0,0 +1,391 @@
+<?xml version="1.0" standalone="no"?>
+<!DOCTYPE s1 SYSTEM "../../style/dtd/document.dtd">
+<!--
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+-->
+
+<s1 title="XML Security Overview">
+<ul>
+<li><link anchor="xsov_xmlParser">XML Parser Threats</link></li>
+<li><link anchor="xsov_resolvEntity">Resolving External Entities</link></li>
+<li><link anchor="xsov_trustEntity">Trusted External Entities</link></li>
+<li><link anchor="xsov_piThreat">Processing Instruction (PI) Threats</link></li>
+<li><link anchor="xsov_soapThreat">SOAP Simple Object Access Protocol</link></li>
+<li><link anchor="xsov_wsdlThreat">WSDL Web Service Description Language</link></li>
+<li><link anchor="xsov_uriThreat">URI Uniform Resource Identifiers</link></li>
+<li><link anchor="xsov_urlThreat">URL Uniform Resource Locators</link></li>
+<li><link anchor="xsov_malUtfStrings">Malformed UTF-8 and UTF-16 Strings</link></li>
+<li><link anchor="xsov_canonicalXML">Canonical XML Issues</link></li>
+<li><link anchor="xsov_xhtmlWorkaround">XHTML Output Mode - Workaround</link></li>
+</ul>
+
+<br/>
+<p><em>This document goes well beyond XSLT. Use it as a general reference.</em>
+</p>
+<p>There are numerous security issues and problems that are
+endemic to the XML architecture.
+I will try to identify some of the most common issues and threats
+and describe some mitigation strategies.
+</p>
+<p>The biggest threat issue is a matter of trust.
+How well do you trust your sources of XML data?
+What are the tools that can help increase the trust?
+</p>
+<p>Most Web Service communications uses HTTP over standard TCP ports.
+The HTTP protocol on standard TCP ports has free access through business firewalls.
+How well do your proxy servers handle the Web Service security issues
+required for your applications?
+</p>
+<p>How well are your resource identifiers protected?
+How well do your applications cope with resource identifier spoofing?
+Can your resource identifiers be trusted by outside clients?
+Can you trust the credentials of your clients?
+</p>
+<p>Will the SOAP interface for your Web Service send error messages
+to an untrusted Web Service address?
+</p>
+<p>Is your WSDL interface description file readily available for download,
+thus enabling persons with malicious intent to create targeted attacks on your Web Services?
+</p>
+<p>Can you trust the client credentials that use your Web Service application?
+</p>
+<p>There are numerous security issues that are not directly involved in
+the markup of XML or its processing.
+These issues relate to infrastructure.
+</p>
+<p>Can you trust your DNS (Domain Name Service) and reduce its vulnerability to hijacking?
+</p>
+<p>Are your web servers hardened against known application vulnerabilities?
+</p>
+<p>Are your applications hardened against
+cross site scripting and SQL injection?
+</p>
+<p>Can your client applications trust the scripts
+that are transmitted as web pages?
+</p>
+<p>Can your web server trust the scripts that are submitted?
+</p>
+<p>Is application data sanitized before being consumed by your applications?
+</p>
+
+<anchor name="xsov_xmlParser"/>
+<s2 title="XML Parser Threats">
+
+<p>This list will help you find the XML threat vectors that need to be addressed.
+Some vectors cannot be easily resolved.
+</p>
+<ul>
+<li>Resolving External Entities</li>
+<li>Implicit Trust of Internal DTD</li>
+<li>Resource Identifier Spoofing</li>
+<li>Malformed UTF-8 and UTF-16</li>
+<li>Secure the trust of external DTD descriptions</li>
+<li>Secure the trust of external Schema definitions</li>
+<li>Secure the trust of entity import and include constructs</li>
+<li>Configuration of Entity Resolver Catalogs</li>
+</ul>
+</s2>
+
+<anchor name="xsov_resolvEntity"/>
+<s2 title="Resolving External Entities">
+
+<p>The XML1.0 and XML1.1 standards specify a <code>DOCTYPE</code> format.
+The processing may uncover significant entity resolver deficiencies.
+</p>
+
+<p><code><!DOCTYPE name PUBLIC "public-id" "system-id" [internal-DTD]></code><br/>
+<code><!DOCTYPE name SYSTEM "system-id" [internal-DTD]></code>
+</p>
+<p>XML Parsers MUST process the <code>[internal-DTD]</code> if it exists.
+</p>
+<p>XML Parsers MAY process the external <code>"system-id"</code> if it can be found.
+</p>
+<p>XML Parsers MAY process the external <code>"public-id"</code> if it can be found.
+</p>
+<p>XML Parsers MAY prefer either the <code>"public-id"</code> or <code>"system-id"</code>
+if both are specified.
+</p>
+<p>XML Parsers MAY ignore both the <code>"public-id"</code> and <code>"system-id"</code>
+if present.
+</p>
+<p>Declaring a parameter entity notation <code>"%entity;"</code>
+in the <code>[internal-DTD]</code> and expanding the content within the
+<code>[internal-DTD]</code> will force the XML parser to import the content
+referenced by the <code>"%entity;"</code> notation.
+</p>
+<p>Declaring a general entity notation <code>"&entity;"</code> in the
+<code>[internal-DTD]</code> and expanding the content within the body of
+the XML document will force the XML parser to import the content referenced
+by the <code>"&entity"</code> notation.
+</p>
+<p>The default method of resolving external entities is by resolving entity
+name strings relative to DNS named hosts and/or path names relative to the
+local computer system. When receiving XML documents from an outside source,
+these entity reference locations may be unreachable, unreliable, or untrusted.
+</p>
+<p>Web Service SOAP XML documents MUST NOT have <code>DOCTYPE</code> definitions.
+SOAP processors should not process DOCTYPE definitions.
+The conformance is implementation dependent.
+</p>
+<p><jump href="http://www.w3.org/TR/soap">http://www.w3.org/TR/soap</jump>
+</p>
+</s2>
+
+<anchor name="xsov_trustEntity"/>
+<s2 title="Trusted External Entities">
+
+<p>The <ref>OASIS XML Catalogs</ref> specification, if implemented by an application,
+can specify a set of external entities that can be trusted by mapping known
+identifiers to local or trusted resources. A secure application should
+not trust entity identifiers whose resources cannot be localized and secured.
+</p>
+<p><jump href="http://www.oasis-open.org/committees/entity">http://www.oasis-open.org/committees/entity</jump>
+</p>
+<p>A similar method can be designed specifically for each application.
+</p>
+<p>A trusted application may need to pre-screen any entity definitions in XML
+before passing the information into the core of the application.
+</p>
+<p>A trusted application should install some type of entity resolving catalog
+or database that can be trusted.
+</p>
+</s2>
+
+<anchor name="xsov_piThreat"/>
+<s2 title="Processing Instruction (PI) Threats">
+
+<p>Processing instructions are a mechanism to send specific information
+into an application. A common processing instruction is a
+stylesheet declaration.
+This information is part of an XML document and comes usually
+after the XML header and before the root element.
+</p>
+<p>A stylesheet declaration may cause an application to look for an
+untrusted XSLT stylesheet to use for transformation of the
+following root element. A standard exists for associating style sheets with XML documents.
+</p>
+<p><jump href="http://www.w3.org/TR/xml-stylesheet">http://www.w3.org/TR/xml-stylesheet</jump>
+</p>
+<p>Examples in the xml-stylesheet recommendation describes how to use the
+processing instruction to associate CSS stylesheets for XHTML.
+Applications that use XSLT transformations will interpret the
+xml-stylesheet processing instruction as the location of a
+XSLT transformation stylesheet.
+</p>
+<p>As more processing instructions become standardized and in common use,
+their threat of misuse increases.
+</p>
+</s2>
+
+<anchor name="xsov_soapThreat"/>
+<s2 title="SOAP Simple Object Access Protocol">
+
+<p>The SOAP specification explicitly forbids the transport of
+DOCTYPE definitions and PI processing instructions.
+</p>
+<p>The SOAP specifies a transport envelope that encapsulates
+an XML message for transport. SOAP can also handle various
+transmission status indicators implying confirmation of delivery,
+error messages, and queue status messages.
+SOAP transports can be loosely coupled and intermittent.
+SOAP is used extensively in the design and deployment of Web Service architectures.
+A companion Web Service specification is WSDL, the Web Service Definition Language.
+</p>
+<p>The SOAP protocol as widely deployed by Microsoft and other vendors
+is based on specifications that predate the adoption
+by the <jump href="http://www.w3.org">World Wide Web Consortium (W3C)</jump>.
+SOAP is not based on Microsoft technology.
+It is an open standard drafted by UserLand, Ariba, Commerce One, Compaq,
+Developmentor, HP, IBM, IONA, Lotus, Microsoft, and SAP.
+<jump href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508">SOAP 1.1</jump>
+was presented to the W3C in May 2000 as an official Internet standard.
+</p>
+<p>The original <jump href="http://www.w3.org/TR/soap11">SOAP 1.1</jump> standard
+is associated with this URI namespace prefix.
+</p>
+<p><code>http://schemas.xmlsoap.org/soap/</code>
+</p>
+<p>There are significant changes in naming conventions since SOAP 1.1
+was adopted by W3C as a recommended standard.
+The current iteration is <jump href="http://www.w3.org/TR/soap12">SOAP 1.2</jump>
+and is associated with this URI namespace prefix.
+</p>
+<p><code>http://www.w3.org/2003/05</code>
+</p>
+<p>The basic security threat to the SOAP architecture is
+the ability to spoof Web Service addresses and telling a
+SOAP server to respond to a rogue Web Service address
+when a <code>mustUnderstand</code> attribute is processed
+and an error indication is raised.
+</p>
+<p>Other intelligence that can be obtained might be the
+location of a public accessible WSDL definition
+of the messages being transported by SOAP,
+thus allowing additional malware attacks to be automatically generated.
+</p>
+</s2>
+
+<anchor name="xsov_wsdlThreat"/>
+<s2 title="WSDL Web Service Description Language">
+
+<p>WSDL is known as the Web Service Description Language.
+The WSDL XML document is a an interface description that can be transformed
+into various programming languages.
+Such transformed interface descriptions are recognized as
+Java Interfaces and C++ Virtual Classes.
+</p>
+<p>The original <jump href="http://www.w3.org/TR/wsdl">WSDL 1.1</jump> standard
+is associated with this URI namespace prefix.
+</p>
+<p><code>http://schemas.xmlsoap.org/wsdl/</code>
+</p>
+<p>The current <jump href="http://www.w3.org/TR/wsdl20">WSDL 2.0</jump> standard
+is maintained by W3C in their namespace with prefix.
+</p>
+<p><code>http://www.w3.org/</code>
+</p>
+<p>The WSDL can provide a template for generating a compliant Web Service systems
+for multiple and hetrogeneous platforms.
+</p>
+<p>A WSDL document that can benefit developers can also be used by malware
+and hackers to taylor specific threats against targeted Web Services.
+</p>
+<p>The SOA (Service Oriented Architecure),
+SAAS (Software As A Service),
+PAAS (Platform As A Service) are families of
+Web Services used as interfaces into what is
+generally known as Cloud Computing.
+</p>
+</s2>
+
+<anchor name="xsov_uriThreat"/>
+<s2 title="URI Uniform Resource Identifiers">
+
+<p>The URI does not need to specify the location of a resource.
+It merely provides a resource name. A catalog, database,
+or other mechanism is used to map URIs to resource locations.
+</p>
+<p>The security issue here is that most URIs are used with a
+DNS (Domain Name Service) to find a host and path to a resource.
+The URI is then treated as a URL (Uniform Resource Locator).
+</p>
+<p>The mitigation of these threats requires diligence of the
+application architects to ensure an appropriate level of trust
+for the URIs and URLs used in their applications.
+</p>
+<p>The transmission media is inherently untrusted.
+Often SOAP bindings and HTTP transports are used.
+Web Service addressing is readily spoofed.
+</p>
+</s2>
+
+<anchor name="xsov_urlThreat"/>
+<s2 title="URL Uniform Resource Locators">
+
+<p>See: <link anchor="xsov_uriThreat">URI Uniform Resource Identifiers</link>
+</p>
+</s2>
+
+<anchor name="xsov_malUtfStrings"/>
+<s2 title="Malformed UTF-8 and UTF-16 Strings">
+
+<p>Public Key Infrastructure (X.509) certificates are leased from a
+certificate authority or are self-signed.
+The distinguished names and parts thereof are usually rendered in unicode.
+</p>
+<p>The value of zero is not a valid Unicode character.
+It is possible to create non-zero UTF-8 and UTF-16 sequences that equate to zero,
+which is not allowed.
+Some rogue hackers have successfully obtained wild-card PKI (X.509) certificates
+by prepending a UTF-8(zero) in a distinguished name when applying for a certificate.
+Such a certificate could be used to successfully sign anything.
+</p>
+<p>Applications should not blindly accept UTF-8 and UTF-16 strings
+without verifying the proper encoding for those strings.
+Contents that equate to bad Unicode character values should be denied.
+</p>
+</s2>
+
+<anchor name="xsov_canonicalXML"/>
+<s2 title="Canonical XML Issues">
+
+<p>Canonical XML is a tranformation of an XML document into a
+canonical form useful for signing.
+This is used in some Web Service security implementations.
+</p>
+<p>There are several areas where Canonical XML will create XML documents
+that have severe application problems.
+</p>
+<p>The number values are rendered in Base-10 as decimal fractions.
+The computations performed by computers are usually in Base-2 floating point arithmetic.
+You therefore have truncation or roundoff issues when converting between
+decimal fractions and Base-2 fractions.
+</p>
+<p>The canonical process may collapse whitespace and transform
+multi-character line endings to single-character line endings.
+When whitespace is significant, the canonical issues for signing can cause problems.
+</p>
+<p>It is possible to create XHTML documents that will not work with some browsers.
+The empty <a/> anchor element is not allowed by many browsers,
+therefore <a></a> is required.
+A standard XML canonical process may collapse elements with no content into empty elements.
+The empty paragraph<p/> is disallowed. The <p></p> is supported.
+</p>
+<p>The World Wide Web Consortium (W3C) has additional detailed discussion of
+<jump href="http://www.w3.org/TR/C14N-issues/">canonicalization issues</jump>.
+</p>
+</s2>
+
+<anchor name="xsov_xhtmlWorkaround"/>
+<s2 title="XHTML Output Mode - Workaround">
+
+<p>The Xalan-C/C++ library currently has no XHTML output mode.
+Since XHTML is to be well-formed XML, the desire is to use the XML output method.
+</p>
+<p>XHTML is based on HTML version 4.
+</p>
+<p>Empty elements declared by HTML-4 should have a space before the
+trailing '/>' markup (i.e. <br /> and <hr />).
+XML output mode does not normally have this space when using
+the <xsl:element name="br" /> in your stylesheet.
+Most modern browsers are ok with no space, but viewing the
+browser source shows a warning condition.
+</p>
+<p>Non-empty elements declared by HTML-4 should not be rendered as empty XML elements.
+If there is no content, the elements should be rendered with both a start-tag and end-tag
+(i.e. <a name="xxx"></a>) instead of an XML empty-element.
+XSLT processors usually create an empty-element
+(i.e. <a name="xxx"/>) when the element being defined has no content
+other than attributes.
+</p>
+<p>For XSLT processors creating XML documents for XHTML,
+you can create what looks like an element with no content by including
+the &#8204; character
+(a zero-width non-joining character often known as &zwnj;)
+as the element text content.
+This also allows transitional browsers the ability to find the end tag.
+</p>
+<p><source> DTD <!ENTITY zwnj "&#8204;">
+
+ <a name="marker">&zwnj;</a></source>
+</p>
+<p>Transitional XHTML is not usually well-formed XML.
+It becomes a mix of HTML version 4 and XML markup.
+Strict XHTML is required to be well-formed XML.
+</p>
+</s2>
+</s1>
\ No newline at end of file
Modified: xalan/c/branches/GSoC-2012/xdocs/sources/xalan/usagepatterns.xml
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xalan/usagepatterns.xml?rev=1391665&r1=1391664&r2=1391665&view=diff
==============================================================================
--- xalan/c/branches/GSoC-2012/xdocs/sources/xalan/usagepatterns.xml (original)
+++ xalan/c/branches/GSoC-2012/xdocs/sources/xalan/usagepatterns.xml Fri Sep 28 21:26:05 2012
@@ -1,4 +1,4 @@
-<?xml version="1.0" standalone="no"?>
+<?xml version="1.0" standalone="no"?>
<!DOCTYPE s1 SYSTEM "../../style/dtd/document.dtd">
<!--
* Licensed to the Apache Software Foundation (ASF) under one
@@ -86,7 +86,7 @@ XALAN_USING_XALAN(XalanTransformer)
<p>These macros can be used immediately after the included header files (for global applicability in a given source file) or within
functions and methods for local applicability.</p>
<note>Whilst you can use the standard C++ namespace syntax directly, the &xml4c; and &xslt4c; namespaces are linked to the version
- number. For example, the Xalan namespace is currently <em>xalanc_1_9</em>. The macros will automatically take care of this
+ number. For example, the Xalan namespace is currently <em>xalanc_1_11</em>. The macros will automatically take care of this
when code is re-compiled against a new version of the libraries. Using the namespaces directly will require each namespace
related statement be updated by hand.</note>
</s3>
@@ -185,30 +185,30 @@ int theResult =
</s2>
<anchor name="params"/>
-<s2 title="Setting stylesheet parameters">
-<p>An XSL stylesheet can include parameters that are set at run time before a transformation takes place. When we generate
- the HTML documents that make up the Xalan doc set, for example, we send the stylesheet an id parameter along with each
- XML source document. The id identifies that document and enables the stylesheet to integrate it into the overall doc set.</p>
-<p>To set a stylesheet parameter, use the <jump href="apiDocs/classXalanTransformer.html">XalanTransformer</jump>
- setStylesheetParam() method. The setStylesheetParam() method takes two arguments: the parameter name and the expression.
- For example:</p>
-<source>
-const XalanDOMString key("param1");
-const XalanDOMString expression("'Hello World'");
-theXalanTransformer.setStylesheetParam(key, expression);
-// foo.xsl defines a stylesheet parameter named param1.
-theXalanTransformer.transform("foo.xml","foo.xsl","foo-out.xml")
-</source>
-<note>If the expression is a string, enclose it in single quotes to make it a string expression.</note>
-<p>You can include the -param flag with two arguments when you call the <link idref="commandline">command line utility</link>.
- The first argument is the parameter name or key, and the second argument is the string expression (in single quotes). For example:</p>
-<p><code>Xalan -p param1 'boo' foo.xml foo.xsl</code></p>
-<p>If the string expression includes spaces or other characters that the shell intercepts, first enclose the string in single quotes
- so &xslt4c; interprets it as a string expression, and then enclose the resulting string in double quotes so the shell interprets it as
- a single argument. For example:</p>
-<p><code>Xalan -p "'hello there'" foo.xml foo.xsl</code></p>
-<p>The <link idref="samples" anchor="usestylesheetparam">UseStylesheetParam</link> sample application also uses a command-line parameter.
-</p>
+<s2 title="Setting Stylesheet Parameters">
+
+<p>An XSL stylesheet can include parameters that are set at run time before a transformation takes place. Traditionally, a top-level parameter value is of text string type. The Xalan library now supports three types of top-level parameters that can be set. One is a text string parameter. Another is a number parameter of floating point type double. The third is a nodeset (XalanNode *) parameter, usually implemented as a parsed document.</p>
+
+<p>Any XObject that is created outside of the transformation can be associated with a top-level parameter. The XalanTransformer has an XObject factory whereby top-level parameters can be owned by the XalanTransformer object.</p>
+
+<p>To set a stylesheet parameter, use the
+<jump href="apiDocs/classXalanTransformer.html">XalanTransformer</jump> setStylesheetParam() method. The setStylesheetParam() method takes two arguments: the parameter name and the value. The value can be a string type, a number double type, an (XalanNode *) pointer to a nodeset or parsed document, or any XObjectPtr returned from an XObject factory.</p>
+
+<p>Top level parameters are sticky. Once set to an instance of an XalanTransformer object, they can be used for multiple transformations. The XalanTransformer reset() method prepares a transformer for a new transformation. Use the clearStylesheetParams() method to release the top-level stylesheet parameters.</p>
+
+<p>The Xalan command line utility currently supports only a text string value for a top-level stylesheet parameter. The single quotes are required to identify a text string value.</p>
+
+<p><code>Xalan -p param1 "'string expression'"foo.xml foo.xsl</code></p>
+
+<p>If the string expression includes spaces or other characters that the shell intercepts, first enclose the string in single quotes so Xalan-C++ interprets it as a string expression, and then enclose the resulting string in double quotes so the shell interprets it as a single argument.</p>
+
+<p>The <link idref="samples" anchor="usestylesheetparam">UseStylesheetParam</link> sample application supports all three types of top-level stylesheet parameters.</p>
+
+<p>The 'C' language interface XalanCAPI also supports the three types of top-level parameters. The sample program TestCAPIparms.c shows how to use top-level parameters with 'C' language programs.</p>
+
+<note>The Xalan command line utility should be revised to accommodate the number and nodeset types of top-level stylesheet parameters. Only text string values are currently supported.</note>
+
+<p>Top-level stylesheet parameters of nodeset type (XalanNode *) are useful for the merging of multiple XML documents.</p>
</s2>
<anchor name="incremental"/>
Modified: xalan/c/branches/GSoC-2012/xdocs/sources/xalan/whatsnew.xml
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xalan/whatsnew.xml?rev=1391665&r1=1391664&r2=1391665&view=diff
==============================================================================
--- xalan/c/branches/GSoC-2012/xdocs/sources/xalan/whatsnew.xml (original)
+++ xalan/c/branches/GSoC-2012/xdocs/sources/xalan/whatsnew.xml Fri Sep 28 21:26:05 2012
@@ -1,7 +1,8 @@
<?xml version="1.0" standalone="no"?>
<!DOCTYPE s1 SYSTEM "../../style/dtd/document.dtd"[
-<!ENTITY done-c SYSTEM "DONE">
-<!ENTITY status-c SYSTEM "STATUS">
+<!--<!ENTITY done-c SYSTEM "DONE"> -->
+<!--<!ENTITY status-c SYSTEM "STATUS"> -->
+<!--<!ENTITY todo-c SYSTEM "BUGS"> -->
<!ENTITY history-c SYSTEM "history.xml">]>
<!--
@@ -22,37 +23,161 @@
* limitations under the License.
-->
<s1 title="What's New in this Release">
-<p>Release notes for &xslt4c-current;</p>
+
<ul>
<li><link anchor="status">Status</link></li>
- <li><link anchor="contact">Getting in touch</link></li>
- <li><link anchor="history">History of software changes</link></li>
+ <li><link anchor="contact">Getting in Touch</link></li>
+ <li><link anchor="history">History of Software Changes</link></li>
+ <li><link anchor="bugfix11">Bug Fixes in Release 1.11</link></li>
+ <li><link anchor="bugfix10">Bug Fixes in Release 1.10</link></li>
+ <li><link anchor="bugs">Bug reporting</link></li>
+ <li><link anchor="to-do">To-do tasks for future Xalan-C/C++ releases</link></li>
</ul>
+
<anchor name="status"/>
<s2 title="Status">
- <ul>
- <li><link anchor="done">Changes for &xslt4c; version 1.10</link></li>
- <li><link anchor="bugs">Bug reporting</link></li>
- <li><link anchor="xml4c">Version of &xml4c; to use</link></li>
- <li><link anchor="to-do">To-do tasks for future &xslt4c; releases</link></li>
- </ul>
-
-<anchor name="done"/>
-<s3 title="Changes for &xslt4c; version 1.10">
-<p>Major updates since version 1.9 include:</p>
+
+<p><em>Release notes for Xalan-C/C++ Version 1.11</em>
+</p>
+<p>This is primarily a bug-fix release of version 1.10. Support for number and
+nodeset types for stylesheet top-level parameters has been added. Xerces-C/C++
+versions 3.0 and newer are now supported. Xerces-C/C++ Version 3.1.1 is the
+preferred stable release.
+</p>
+<p>At present, the Xalan-C/C++ Version 1.11 has no binary releases.
+When building Xalan-C/C++ from sources,
+you should use the same platform that was used to
+compile the companion Xerces-C/C++ library.
+</p>
+<p>Binary package releases for Microsoft Windows are being planned.
+</p>
+<p>If you are able to successfully create a new binary package and wish it
+to be included, then we welcome your participation on the
+<jump href="mailto:dev@xalan.apache.org">xalan-dev</jump> mail list.
+</p>
+<p>Xalan-C/C++ no longer supports Microsoft Studio (VC6). The Microsoft Visual
+Studio .NET platforms (2003, 2005, 2008, and 2010) are supported. This equates
+to compilers (VC71, VC8, VC9, and VC10).
+</p>
+
+</s2>
+
+<anchor name="contact"/>
+<s2 title="Getting in Touch">
+<p>Your feedback is more than welcome. Offers of help are even more so!
+Perhaps you would like to contribute to the ongoing development,
+testing, or documentation of &xslt4c;.
+</p>
+<p>Please email your comments, questions, suggestions, bug reports,
+and offers to help to <human-resource-ref idref="xalandev"/>.
+</p>
+<p>Your general user comments on &xslt4c; usage are also welcome on
+<human-resource-ref idref="xalancusers"/>.
+</p>
+</s2>
+
+<anchor name="history"/>
+<s2 title="Cumulative history of software changes">
+<p>The following sections list the changes in each release since &xslt4c; version 0.40.0.</p>
+&history-c;
+</s2>
+
+
+<anchor name="bugfix11"/>
+<s2 title="Bug Fixes in Release 1.11">
+<p>The bugs fixed in &xslt4c-current; include:</p>
<ul>
- <li>Support for XML 1.1 and Namespaces in XML 1.1.</li>
- <li>Added support for IBM XLC 7.0 compiler on Linux.</li>
- <li>Improved and stabilized C pluggable memory management functionality.</li>
- <li>Various improvements in Xalan XML serializers for better performance and stability.</li>
- <li>Upgrade from Xerces-C 2.6 to Xerces-C 2.7.</li>
- <li><link anchor="bugfixes">Bugs fixed in this release</link>.</li>
- </ul>
-</s3>
-
-<anchor name="bugfixes"/>
-<s2 title="Bugs Fixed in this Release">
-<p>The bugs fixed in this release include:</p>
+<li>XALANC-723 Add Top-Level parameter support for XalanCAPI and UseStylesheetParams sample</li>
+<li>XALANC-721: Upgrade support for MS VS 2010 (VC10)</li>
+<li>XALANC-719: Xerces Parser Liaison - errors on elements with no attributes</li>
+<li>XALANC-716: incorrect buffer-size calculation in XalanUTF16Writer.hpp</li>
+<li>XALANC-715: NULL pointer access crash</li>
+<li>XALANC-713: Build Xalan-C/C++ API Reference Manual using Doxygen 1.7 or newer</li>
+<li>XALANC-710: MS-Studio 2008 Debug Build sends Xalan-C_1D.lib to wrong directory</li>
+<li>XALANC-709: Doxygen bug in XalanQName.hpp</li>
+<li>XALANC-708: Including XalanCAPI.hpp does not import Xerces typedef XMLch</li>
+<li>XALANC-705: Crash with pure virtual function call</li>
+<li>XALANC-703: Compiler errors while building on AIX 5.3</li>
+<li>XALANC-700: Broken output when serializing UTF16 surrogates</li>
+<li>XALANC-699: Compile using Visual C++ 2010 (VC10)</li>
+<li>XALANC-698: Buffer overflow from XalanMessageLoader::load()</li>
+<li>XALANC-690: The document function does not handle fragment IDs in URLs correctly</li>
+<li>XALANC-689: XalanC transformation of a 600 kb file takes 43 seconds</li>
+<li>XALANC-684: XPath single quate-comma bug</li>
+<li>XALANC-683: xsl:number with level any does not always count all of the preceeding nodes in the document</li>
+<li>XALANC-681: NamedNodeMapAttributeList constructor asserts when the provided NamedNodeMap is empty</li>
+<li>XALANC-680: Error in match pattern with // and abbreviated attribute node test</li>
+<li>XALANC-679: Possible wrong evaluation of abbreviated XPath in template match</li>
+<li>XALANC-677: Debug assertion switching to HTML mode when the outputter is producing a DOM</li>
+<li>XALANC-675: No error is reported for an unknown key</li>
+<li>XALANC-675: GCC-4.3 cleanup</li>
+<li>XALANC-673: Assertion failed with XalanDOMString::substr</li>
+<li>XALANC-671: Incorrect handling of default namespace in xsl:element</li>
+<li>XALANC-669: XalanOtherEncodingWriter reports an incorrect error message</li>
+<li>XALANC-667: setUseValidation doesn't work</li>
+<li>XALANC-664: Testing harness writes strings to the output XML in the local code page.</li>
+<li>XALANC-661: PlatformSupport/DoubleSupport.cpp compile error on AIX 5.3</li>
+<li>XALANC-660: Compilation errors in Tests/Performance/TestHarness.hpp on some platforms</li>
+<li>XALANC-659: Unnecessary casting in ReusableArenaBlock</li>
+<li>XALANC-658: Misplaced assert in ReusableArenaAllocator::destroyObject()</li>
+<li>XALANC-657: Add Windows x64 targets to the project files</li>
+<li>XALANC-655: Boolean value incorrectly converted ot string in attribute value templates</li>
+<li>XALANC-653: Xalan-C not including namespace declaration in output</li>
+<li>XALANC-650: XPathProcessorImpl uses XalanDOMString copy constructor instead of referring to an existing instance</li>
+<li>XALANC-648: XalanUTF8Writer::write(const XalanDOMChar*, XalanDOMString::size_type) does not handle surrogates properly</li>
+<li>XALANC-647: XalanOtherEncodingWriter::writeNumericCharacterReference() is inefficient</li>
+<li>XALANC-646: During transcoding XalanC fails to append '0' to the transcoded string </li>
+<li>XALANC-645: Pluggin of DOMStringPrintWriter into FormatterToXML leads to assert</li>
+<li>XALANC-641: Class used as exception needs accessible copy constructor</li>
+<li>XALANC-640: Path problem in Makefile under cygwin</li>
+<li>XALANC-638: Performance test program does not build on HP-UX</li>
+<li>XALANC-635: Build fails on Solaris 2.8</li>
+<li>XALANC-634: Build fails with VC6</li>
+<li>XALANC-633: The processor should ignore xsl:fallback element in LRE </li>
+<li>XALANC-632: @use-attribute-sets attribute has to have no effect on xsl:copy when the context item is a documen node.</li>
+<li>XALANC-631: The next stylesheet crashes XalanC</li>
+<li>XALANC-630: Incorrect cast in XalanUTF16Writer</li>
+<li>XALANC-629: Performance improvements for text node stripping</li>
+<li>XALANC-628: Inconsistent flusing of serializers</li>
+<li>XALANC-627: Broken cast in ElemTemplateElement::findTemplateToTransformChild()</li>
+<li>XALANC-626: Fix copyrights in Apache XalanC source</li>
+<li>XALANC-625: Spurious (though harmless) assert failure in XPath::findNodeSet() when an expression contains an empty node-set enclosed in parenthesis</li>
+<li>XALANC-624: The key() function does not work when the context node is the root node of a result tree fragment obtained through exsl:node-set()</li>
+<li>XALANC-623: Compatibility issues with Xerces-C 3.0</li>
+<li>XALANC-621: Selection of compiler definitions file fails on Linux PPC in client code</li>
+<li>XALANC-618: uninstallExternalFunction can run past the end of the array</li>
+<li>XALANC-617: Leak in XalanTransformer</li>
+<li>XALANC-616: xsl:strip-space element doesn't work proprely</li>
+<li>XALANC-615: Xalan resolves a namespace prefix when it should report an error</li>
+<li>XALANC-614: MsgCreator Makefile needs link option</li>
+<li>XALANC-613: Cannot pass value to stylesheet parameter if parameter name is namespace-qualified</li>
+<li>XALANC-609: Template with built-in template rules for namespaces gives and assert</li>
+<li>XALANC-604: ConstructWithNoMemoryManager has a bug which prevents proper default initialization of built-in types.</li>
+<li>XALANC-603: Source does not compile properly on HP-UX with newer versions of the HP compiler</li>
+<li>XALANC-595: EXSLT date-time function missing + or - before timezone offset</li>
+<li>XALANC-588: Floating point exceptions in DoubleSupport::initialize() on Solaris 10 (x86)</li>
+<li>XALANC-570: Removal of compiler warnings from STLHelper.hpp</li>
+<li>XALANC-535: If an error/warning message contains not-displayable character for the local encoding , no message is shown at all</li>
+<li>XALANC-527: Compiling on Xerces-3.0</li>
+<li>XALANC-480: XML1.1 and Namespaces for XML1.1 support</li>
+<li>XALANC-478: Add support for XMLEntityResolver</li>
+<li>XALANC-432: Minor spelling problems in XalanMsg_en_US.xlf</li>
+<li>XALANC-430: "StylesheetExecutionContext::getVariable(name)" crahes if variable "name" was not found.</li>
+<li>XALANC-421: omit-xml-declaration ignored</li>
+<li>XALANC-416: Wrong access to out-of-scope xsl:variable not detected in certain circumstances</li>
+<li>XALANC-415: Encoding attribute is not returning properly in output XML header</li>
+<li>XALANC-413: Crash while using transform method on MacOSX</li>
+<li>XALANC-412: XalanEXSLTDateTime not threadsafe, crashing application</li>
+<li>XALANC-409: compilation error on g++ on SunOS 2.8</li>
+<li>XALANC-408: runConfigure help does not include new HP platform</li>
+<li>XALANC-407: XalanC output format is not suitable as a document entity</li>
+<li>XALANC-376: Result tree fragment attributes are created without proper namespace and local name </li>
+</ul>
+</s2>
+
+<anchor name="bugfix10"/>
+<s2 title="Bugs Fixed in Release 1.10">
+<p>The bugs fixed in the 1.10 release include:</p>
<ul>
<li>XALANC-572: Compile failure on SuSE80AMD_64b_GCC322 </li>
<li>XALANC-569: Compile-time assert on 32-bit Solaris and HPUX due to IEEE754 issue </li>
@@ -108,33 +233,44 @@
</ul>
</s2>
+
<anchor name="bugs"/>
-<s3 title="Bug reporting">
+<s2 title="Bug reporting">
<p>All known &xslt4c; bugs are listed in <resource-ref idref="jira"/>. For a list of open bugs with links to each bug
report, see <resource-ref idref="buglist"/>. If you find a new bug, please enter a XalanC bug report in this
database.</p>
-<note>Before you can enter your first bug report, you must submit your email address to JIRA and receive a password.</note>
-<p>We strongly encourage you write patches for problems you find and submit them to
- xalan-dev@xml.apache.org. We review the patches we receive to make sure they do not break something else, and (assuming they
- do not) include them in our next release. In the interest of fixing bugs, adding enhancements, and addressing outstanding design
- issues, we sincerely want (and need!) your active participation in the ongoing development of Xalan.</p>
-</s3>
-
-<anchor name="xml4c"/>
-&status-c;
-
-<anchor name="contact"/>
-<s3 title="Getting in Touch">
-<p>Your feedback is more than welcome. Offers of help are even more so! Perhaps you would like to contribute to the ongoing development, testing, or documentation of &xslt4c;.</p>
-<p>Please email your comments, questions, suggestions, bug reports, and offers to help to <human-resource-ref idref="xalandev"/>.</p>
-</s3>
-
-<anchor name="history"/>
-<s3 title="Cumulative history of software changes">
-<p>The following sections list the changes in each release since &xslt4c; version 0.40.0.</p>
-&history-c;
-</s3>
-
+<note>Before you can enter your first bug report,
+ you must submit your email address to
+ <jump href="https://issues.apache.org/jira">JIRA</jump>
+ and receive a password.
+</note>
+<p>We strongly encourage you write patches for problems you find and
+ submit them to JIRA and the
+ <jump href="mailto:dev@xalan.apache.org">xalan-dev</jump> mailing list.
+ We review the patches we receive to make sure they do not break something else, and (assuming they do not)
+ include them in our next release.
+ In the interest of fixing bugs, adding enhancements, and
+ addressing outstanding design issues, we sincerely want
+ (and need!) your active participation in the ongoing development of Xalan.
+</p>
</s2>
+<anchor name="to-do"/>
+<s2 title="To-do tasks for future Xalan-C/C++ releases">
+<p>Open bugs:</p>
+<ul>
+<li>The namespace axis does not return the default "xml" namespace.</li>
+<li>Does not support case-order and lang attributes in xsl:sort.</li>
+</ul>
+<p>Items to do:</p>
+<ul>
+<li>Add support for new specifications (XPath-20, XSLT-2.0)</li>
+<li>Add transcoding support using Xerces-C modules</li>
+<li>Add XSLT extension elements</li>
+<li>Add more EXSLT extension functions</li>
+<li>Add the EXSLT document extension function</li>
+<li>Add support for user-defined extension modules</li>
+<li>Add support for node-set to be declared as top-level XSLT parameter</li>
+</ul>
+</s2>
</s1>
Added: xalan/c/branches/GSoC-2012/xdocs/style/dtd/blocks.ent
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/style/dtd/blocks.ent?rev=1391665&view=auto
==============================================================================
--- xalan/c/branches/GSoC-2012/xdocs/style/dtd/blocks.ent (added)
+++ xalan/c/branches/GSoC-2012/xdocs/style/dtd/blocks.ent Fri Sep 28 21:26:05 2012
@@ -0,0 +1,40 @@
+<?xml encoding='US-ASCII'?>
+
+<!-- BLOCKS ENTITY -->
+<!ENTITY % blocks "p|note|ul|ol|gloss|table|source|anchor">
+
+<!-- import the external markup.ent dtd -->
+<!ENTITY % markupEntity SYSTEM "markup.ent">
+%markupEntity;
+
+<!ENTITY % content "(#PCDATA|%markup;|%links;)*">
+
+<!ELEMENT p %content;>
+<!ELEMENT note %content;>
+
+<!ELEMENT ul (li|ol|ul)+>
+<!ELEMENT ol (li|ol|ul)+>
+<!ELEMENT li %content;>
+
+<!ELEMENT gloss (label|item)+>
+<!ELEMENT label %content;>
+<!ELEMENT item %content;>
+
+<!ELEMENT source (#PCDATA)>
+
+<!ELEMENT table (tr)+>
+
+<!ELEMENT tr (tn|th|td)+>
+
+<!ELEMENT tn EMPTY>
+<!ATTLIST tn colspan CDATA "1"
+ rowspan CDATA "1">
+
+<!ELEMENT th %content;>
+<!ATTLIST th colspan CDATA "1"
+ rowspan CDATA "1">
+
+<!ELEMENT td %content;>
+<!ATTLIST td colspan CDATA "1"
+ rowspan CDATA "1">
+
\ No newline at end of file
Added: xalan/c/branches/GSoC-2012/xdocs/style/dtd/book.dtd
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/style/dtd/book.dtd?rev=1391665&view=auto
==============================================================================
--- xalan/c/branches/GSoC-2012/xdocs/style/dtd/book.dtd (added)
+++ xalan/c/branches/GSoC-2012/xdocs/style/dtd/book.dtd Fri Sep 28 21:26:05 2012
@@ -0,0 +1,56 @@
+<?xml encoding='US-ASCII'?>
+
+<!-- STYLEBOOK BOOK DTD -->
+
+<!-- import the external source-specific dtd -->
+<!ENTITY % externalEntity SYSTEM "../../sources/entities.ent">
+%externalEntity;
+
+<!ELEMENT book (resources?|document|hidden|faqs|changes|group|external|separator)+>
+<!ATTLIST book title CDATA #REQUIRED
+ copyright CDATA #IMPLIED>
+
+<!ELEMENT resources EMPTY>
+<!ATTLIST resources source CDATA #REQUIRED>
+
+<!ELEMENT document EMPTY>
+<!ATTLIST document id ID #REQUIRED
+ source CDATA #REQUIRED
+ label CDATA #REQUIRED>
+
+<!ELEMENT hidden EMPTY>
+<!ATTLIST hidden id ID #REQUIRED
+ source CDATA #REQUIRED>
+
+<!ELEMENT faqs EMPTY>
+<!ATTLIST faqs id ID #REQUIRED
+ source CDATA #REQUIRED
+ label CDATA #REQUIRED>
+
+<!ELEMENT changes EMPTY>
+<!ATTLIST changes id ID #REQUIRED
+ source CDATA #REQUIRED
+ label CDATA #REQUIRED>
+
+<!-- (entry) not supported in markup, cannot be tested -->
+<!-- (group) not to have entry children, only standard children -->
+<!-- <!ELEMENT group (entry)+> -->
+
+<!ELEMENT group (document|faqs|changes|external)*>
+<!ATTLIST group id ID #IMPLIED
+ label CDATA #REQUIRED>
+
+<!-- (entry) not supported in markup, cannot be tested
+<!ELEMENT entry EMPTY>
+<!ATTLIST entry id ID #REQUIRED
+ source CDATA #REQUIRED>
+-->
+
+<!ELEMENT external EMPTY>
+<!ATTLIST external label CDATA #REQUIRED
+ href CDATA #REQUIRED>
+
+<!ELEMENT separator EMPTY>
+
+<!-- CVS $Revision: 1.3 $ $Date: 1999/12/01 23:03:37 $ -->
+<!-- Revision by (shathaway@apache.org) 2011/09/01 -->
\ No newline at end of file
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xalan.apache.org
For additional commands, e-mail: commits-help@xalan.apache.org