You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xalan.apache.org by dl...@apache.org on 2001/02/13 16:55:24 UTC
cvs commit: xml-xalan/c/xdocs/sources/xalan getstarted.xml samples.xml usagepatterns.xml
dleslie 01/02/13 07:55:24
Modified: c/xdocs/sources entities.ent xalan.xml
c/xdocs/sources/xalan getstarted.xml samples.xml
usagepatterns.xml
Log:
Updates in progress for Xalan-C 1.1.
Revision Changes Path
1.14 +7 -7 xml-xalan/c/xdocs/sources/entities.ent
Index: entities.ent
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/entities.ent,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- entities.ent 2001/02/09 15:08:02 1.13
+++ entities.ent 2001/02/13 15:55:21 1.14
@@ -1,13 +1,13 @@
<?xml encoding="US-ASCII"?>
<!ENTITY xslt4c "Xalan-C++">
-<!ENTITY xslt4c-dist "Xalan-C_1_2">
-<!ENTITY xslt4c-current "Xalan-C++ version 1.2">
+<!ENTITY xslt4c-dist "Xalan-C_1_1">
+<!ENTITY xslt4c-current "Xalan-C++ version 1.1">
<!ENTITY xslt4c-windlls "DOMSupport.dll, PlatformSupport.dll, XalanDOM.dll, XercesParserLiaison.dll, XMLSupport.dll, XPath.dll, XSLT.dll, XalanTransformer.dll">
-<!ENTITY xslt4c-linuxlib "libxalan-c1_2.so">
-<!ENTITY xslt4c-aixlib "libxalan-c1_2.a">
-<!ENTITY xslt4c-hplib "libxalan-c1_2.sl">
-<!ENTITY xslt4c-solarislib "libxalan-c1_2.xxxx">
+<!ENTITY xslt4c-linuxlib "libxalan-c1_1.so">
+<!ENTITY xslt4c-aixlib "libxalan-c1_1.a">
+<!ENTITY xslt4c-hplib "libxalan-c1_1.sl">
+<!ENTITY xslt4c-solarislib "libxalan-c1_1.so">
<!ENTITY xml4c "Xerces-C++">
<!ENTITY xml4c-used "Xerces-C++ version 1.4.0">
<!ENTITY xml4c-windll "xerces-c_1_4.dll">
@@ -15,7 +15,7 @@
<!ENTITY xml4c-linuxlib "libxerces-c1_4.so">
<!ENTITY xml4c-aixlib "libxerces-c1_4.a">
<!ENTITY xml4c-hplib "libxerces-c1_4.sl">
-<!ENTITY xml4c-solarislib "libxerces-c1_4.xxxx">
+<!ENTITY xml4c-solarislib "libxerces-c1_4.so">
<!ENTITY xslt4j "Xalan-Java">
<!ENTITY icu-used "International Components for Unicode(ICU) 1.6 source files">
<!ENTITY icu-windlls "icui18n.dll, icuuc.dll">
1.6 +1 -1 xml-xalan/c/xdocs/sources/xalan.xml
Index: xalan.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- xalan.xml 2000/09/12 13:35:09 1.5
+++ xalan.xml 2001/02/13 15:55:21 1.6
@@ -67,7 +67,7 @@
<separator/>
<document id="index"
- label="Xalan-C++ 1.0"
+ label="Xalan-C++ 1.1"
source="xalan/index.xml"/>
<separator/>
1.23 +6 -6 xml-xalan/c/xdocs/sources/xalan/getstarted.xml
Index: getstarted.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/getstarted.xml,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- getstarted.xml 2001/02/12 22:04:03 1.22
+++ getstarted.xml 2001/02/13 15:55:23 1.23
@@ -4,7 +4,7 @@
<s1 title="Getting Started with Xalan-C++">
<ul>
<li><link anchor="download">Downloading what you need</link></li>
-<li><link anchor="path">Setting up the system path</link></li>
+<li><link anchor="path">Setting up the path/library path</link></li>
<li><link anchor="samples">Trying out the samples</link></li>
<li><link anchor="commandline">Performing your own transformations from the command line</link></li>
<li><link anchor="apps">Setting up your own XSLT applications</link></li>
@@ -79,12 +79,12 @@
<p>For the requirements for rebuilding &xslt4c;, see the <link idref="readme" anchor="build">Build notes</link>.</p>
</s3>
</s2><anchor name="path"/>
-<s2 title="Setting up the path">
+<s2 title="Setting up the path/library path">
<p>For the Xalan-C++ Windows32 distribution, place xml-xalan\c\Build\Win32\VC6\Release on the path.</p>
-<p>For the Xalan-C++ Linux distribution, place xml-xalan/c/bin and xml-xalan/c/lib on the shared library path (LD_LIBRARY_PATH for Red Hat Linux 6.1), or copy &xslt4c-linuxlib; to /usr/lib.</p>
-<p>For the Xalan-C++ AIX distribution, place xml-xalan/c/bin and xml-xalan/c/lib on the load library path (LIBPATH), or copy &xslt4c-aixlib; to /usr/lib.</p>
-<p>For the Xalan-C++ HP-UX 11 distribution, place xml-xalan/c/bin and xml-xalan/c/lib on the shared library path (SHLIB_PATH), or copy &xslt4c-aixlib; to /usr/lib.</p>
-<p>For the Xalan-C++ Solaris distribution, place xml-xalan/c/bin and xml-xalan/c/lib on the shared library path (LD_LIBRARY_PATH), or copy &xslt4c-solarislib; to /usr/lib.</p>
+<p>For the Xalan-C++ Linux distribution, place xml-xalan/c/bin on the path (PATH) and xml-xalan/c/lib on the shared library path (LD_LIBRARY_PATH for Red Hat Linux 6.1), or copy &xslt4c-linuxlib; to /usr/lib.</p>
+<p>For the Xalan-C++ AIX distribution, place xml-xalan/c/bin on the path (PATH) and xml-xalan/c/lib on the load library path (LIBPATH), or copy &xslt4c-aixlib; to /usr/lib.</p>
+<p>For the Xalan-C++ HP-UX 11 distribution, place xml-xalan/c/bin on the path (PATH) and xml-xalan/c/lib on the shared library path (SHLIB_PATH), or copy &xslt4c-aixlib; to /usr/lib.</p>
+<p>For the Xalan-C++ Solaris distribution, place xml-xalan/c/bin on the path (PATH) and xml-xalan/c/lib on the shared library path (LD_LIBRARY_PATH), or copy &xslt4c-solarislib; to /usr/lib.</p>
<p>If you do your own Xalan, ICU, and Xerces builds, be sure to include the directories that contain the libraries and the TextXSLT executable on your path.</p>
</s2><anchor name="samples"/>
<s2 title="Trying out the samples">
1.22 +10 -6 xml-xalan/c/xdocs/sources/xalan/samples.xml
Index: samples.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/samples.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- samples.xml 2001/02/12 22:04:03 1.21
+++ samples.xml 2001/02/13 15:55:23 1.22
@@ -243,15 +243,18 @@
<p>To build (or rebuild) the Apache module, follow the instructions in <link idref="readme" anchor="win32">Steps for doing a Windows
build</link> or <link idref="readme" anchor="unix">Steps for doing a UNIX build</link>. For UNIX platforms, you do the build with<br/>
<code>make ApacheModuleXSLT</code>.</p>
- <s3 title="Seting up and using ApacheModuleXSLT">
+ <s3 title="Setting up and using ApacheModuleXSLT">
<p>To use ApacheModuleXSLT, do the following:</p>
<ol>
+ <li>(UNIX only) Be sure the Xalan and Xerces libraries are on your library path (you can accomplish this by copying them to
+ /usr/lib; see <link idref="getstarted" anchor="path">Setting up the path/library path</link>), and copy the Apache module to
+ /usr/lib/apache.<br/><br/></li>
<li>Add LoadModule and (UNIX only) AddModule entries to the Apache configuration file: httpd.conf.<br/><br/>
Windows: <code>LoadModule mod_xslt xml-xalan\c\Build\Win32\VC6\Release\ApacheModuleXSLT.dll</code><br/><br/>
UNIX: <code>AddModule mod_xslt.c</code><br/>
and<br/>
- <code>LoadModule mod_xslt usr/lib/mod_xslt.<ref>xx</ref></code><br/><br/>
- where <ref>xx</ref> is the appropriate library suffix for the UNIX platform.<br/><br/></li>
+ <code>LoadModule mod_xslt usr/lib/apache/mod_xslt.<ref>xx</ref></code><br/><br/>
+ where <ref>xx</ref> is the appropriate library suffix for the UNIX platform ("so" or "a").<br/><br/></li>
<li>Add a <Location> entry to httpd.conf that indicates where xml/xsl file pairs are to be found, and what target file extensions
to recognize. We suggest the following:<br/><br/>
<code><Location /xslt></code><br/>
@@ -261,19 +264,20 @@
This <Location> element instructs the module to respond to requests for <ref>xxx</ref>.html and <ref>xxx</ref>.txt files in the
in the xslt subdirectory (under the document root; see next item) by applying the <ref>xxx</ref>.xsl stylesheet to <ref>xxx</ref>.xml
(both in that directory) and returning the transformation result to the browser.<br/><br/>
+ For example, a request for foo.html instructs the module to apply foo.xsl to foo.xml and return the result.<br/><br/>
Note: It is up to the stylesheet to apply the appropriate xsl:output method to the output. Whether the user specifies html or txt is, of
itself, immaterial.<br/><br/></li>
<li>Put xml/xsl file pairs in the <Location> subdirectory (xslt in the example)) under the document root directory specified in httpd.conf by the
DocumentRoot and <Directory> settings. Alternatively, you can modify these settings to point to xml-xalan/c/samples/ApacheModuleXSLT,
- which includes an xslt subdirectory with xml/xsl file pairs.<br/><br/></li>
+ which includes an xslt subdirectory with xml/xsl file pairs (foo.xml/xsl, apachemod.xml/xsl).<br/><br/></li>
<li>Start the Apache server.<br/><br/></li>
<li>From a Web browser, call the module with a URL as follows:<br/>
<code>http://<ref>serverName</ref>/xslt/<ref>xxx</ref>.html</code><br/>
where <ref>serverName</ref> is the Apache server (such as www.myServer.com) and <ref>xxx</ref> is the name of an xml/xsl pair of files
(such as foo.xml and foo.xsl) in the xslt subdirectory under the DocumentRoot directory.<br/><br/>
For example,<br/>
- <code>http://www.myServer.com/xslt/foo.html</code><br/>
- instructs ApacheModuleXSLT to apply the foo.xsl stylesheet to the foo.xml XML document (both files in the xslt directory under the
+ <code>http://www.myServer.com/xslt/apachemod.html</code><br/>
+ instructs ApacheModuleXSLT to apply the apachemod.xsl stylesheet to the apachemod.xml XML document (both files in the xslt directory under the
Apache DocumentRoot directory) and return the transformation result to the browser.</li>
</ol>
</s3>
1.17 +5 -11 xml-xalan/c/xdocs/sources/xalan/usagepatterns.xml
Index: usagepatterns.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/usagepatterns.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- usagepatterns.xml 2001/02/12 21:43:50 1.16
+++ usagepatterns.xml 2001/02/13 15:55:23 1.17
@@ -83,12 +83,12 @@
<note>As we expand the functionality of the XalanTransformer, we will revise the remainder of this chapter and the samples to indicate
how to take advantage of the API it provides.</note>
<ul>
- <li><link anchor="cpp">Basic XalanTransformer pattern with the C++ API</link></li>
+ <li><link anchor="cpp">Basic usage pattern with the XalanTransformer C++ API</link></li>
<li><link anchor="cppvar">Variations with the XalanTransformer C++ API</link></li>
- <li><link anchor="c">Basic pattern with the XalanTransformer C API</link></li>
+ <li><link anchor="capi">Basic usage pattern with the XalanTransformer C API</link></li>
<li><link anchor="cvar">Variations with the XalanTransformer C API</link></li>
</ul><anchor name="cpp"/>
-<s3 title="Basic XalanTransformer patten with C++ API">
+<s3 title="Basic usage patten with XalanTransformer C++ API">
<p>Using XalanTransformer and the C++ API, you can perform one or more transformations as follows:</p>
<ol>
<li>Include the XalanTransformer header file.<br/>
@@ -136,8 +136,8 @@
const XSLTInputSource& xslStylesheet,
const XSLTResultTarget& transformResult);</source>
-</s3><anchor name="c"/>
-<s3 title="Basic XalanTransformer pattern with the C API">
+</s3><anchor name="capi"/>
+<s3 title="Basic XalanTransformer usage pattern with the C API">
<p>We also include a simple C interface for using the XalanTransformer class. See XalanTransformer/XalanCAPI.h in the source tree.
The <link idref="samples" anchor="apachemodulexslt">ApacheModuleXSLT</link> sample illustrates the use of this C API.</p>
<p>Basic strategy:</p>
@@ -164,12 +164,6 @@
</s3><anchor name="cvar"/>
<s3 title="Variations with the XalanTransformer C API">
<p>The C API supports basically the same options as the C++ API.</p>
-<p>Transform from files to a character array:</p>
-<source>int
-XalanTransformToData(const char* xmlInFile,
- const char* xslFile,
- const char** transformOutput,
- XalanHandle xalan);</source>
<p>Transform from files to a character array:</p>
<source>int
XalanTransformToData(const char* xmlInFile,