dleslie 2002/09/12 12:06:15 Modified: c/xdocs/sources/xalan faq.xml usagepatterns.xml Log: Updates from Dave Bertoni. Revision Changes Path 1.31 +11 -2 xml-xalan/c/xdocs/sources/xalan/faq.xml Index: faq.xml =================================================================== RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/faq.xml,v retrieving revision 1.30 retrieving revision 1.31 diff -u -r1.30 -r1.31 --- faq.xml 12 Sep 2002 16:19:31 -0000 1.30 +++ faq.xml 12 Sep 2002 19:06:15 -0000 1.31 @@ -18,7 +18,7 @@ <a><p>For generic questions about XSL stylesheets and transformations, use the <jump href="http://www.mulberrytech.com/xsl/xsl-list/";>XSL-List -- Open Forum on XSL</jump> hosted by Mulberry Technologies. There is an archive that can be searched as well. Specific questions about &xslt4c; can be asked on the Xalan-dev list. Please review this document and the archives before posting new questions.</p> -<p>For specific questions on &xslt4c;, see [EMAIL PROTECTED] on <jump href="http://archive.covalent.net/";>http://archive.covalent.net/</jump>.</p> +<p>For specific questions on &xslt4c;, see [EMAIL PROTECTED] and [EMAIL PROTECTED] on <jump href="http://archive.covalent.net/";>http://archive.covalent.net/</jump>. To subscribe to these mailing lists, see <jump href="http://xml.apache.org/mail.html";>Mailing Lists</jump>.</p> </a> </faq> @@ -39,7 +39,16 @@ <q>I have encountered problem executing the &xslt4c; sample applications after rebuilding them under Win32 Environment (Windows NT 4.0, SP3). When I tried to execute the sample, I receive the error message "Debug Assertion Failed! ... Expression: _BLOCK_TYPE_IS_VALID(pHead->nBlockUse)".</q> -<a><p>You may be mixing debug and release versions of executables and libraries. In other words, if you are compiling the sample for debug, then you should link with the debug version of the &xslt4c; and &xml4c; libraries and run with the debug version of the dynamic link libraries.</p><anchor name="build"/><p/></a> +<a><p>You may be mixing debug and release versions of executables and libraries. In other words, if you are compiling the sample for debug, then you should link with the debug version of the &xslt4c; and &xml4c; libraries and run with the debug version of the dynamic link libraries.</p> +<p>You must also make sure your application is linking with the Debug multithreaded DLL run-time library or the Multithreaded DLL run-time library. To check this setting do the following in Visual C++:</p> +<ol> + <li>Select Settings from the Project menu.<br/><br/></li> + <li>Click the C/C++ tab.<br/><br/></li> + <li>In the Category drop-down list, select Code Generation.<br/><br/></li> + <li>In the Use run-time library drop-down list, select Multithreaded DLL for the Win32 Release configuration, or select Debug Multithreaded DLL for the Win32 Debug configuration.</li> +</ol> +<p>Once you have changed this setting, you must rebuild your project.</p> +<anchor name="build"/><p/></a> </faq> <faq title="Building on Windows"> 1.37 +12 -7 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.36 retrieving revision 1.37 diff -u -r1.36 -r1.37 --- usagepatterns.xml 11 Sep 2002 18:03:53 -0000 1.36 +++ usagepatterns.xml 12 Sep 2002 19:06:15 -0000 1.37 @@ -92,15 +92,15 @@ #include <XalanTransformer/XalanTransformer.hpp> ...</source> </s3> - <s3 title="2. Initialize Xerces and Xalan"> + <s3 title="2. Initialize Xerces and Xalan."> <p>Use the static initializers to initialize the &xslt4c; and &xml4c; platforms. You must initialize &xml4c; once per process. You may initialize and terminate &xslt4c; multiple times, but this is not recommended: it is inefficient and is not thread safe.</p> <source>XMLPlatformUtils::Initialize(); XalanTransformer::initialize();</source> </s3> - <s3 title="3.Create a XalanTransformer"> + <s3 title="3. Create a XalanTransformer."> <source>XalanTransformer theXalanTransformer;</source> </s3> - <s3 title="4. Perform each transformation"> + <s3 title="4. Perform each transformation."> <p>You can explicitly instantiate <jump href="apidocs/class_xsltinputsource.html">XSLTInputSource</jump> objects for the XML source document and XSL stylesheet, and an <jump href="apidocs/class_xsltresulttarget.html">XSLTResultTarget</jump> object for the output, and then call <jump href="apidocs/class_xalantransformer.html">XalanTransformer</jump> transform() with those objects as parameters. For example:</p> <source>XSLTInputSource xmlIn("foo.xml"); XSLTInputSource xslIn("foo.xsl"); @@ -130,11 +130,16 @@ </ul> <note>Each transform() method returns an integer code, 0 for success. If an error occurs, you can use the getLastError() method to return a pointer to the error message.</note> </s3> -<s3 title="5. Shut down Xalan and (optionally) Xerces"> +<s3 title="5. Shut down Xalan."> +<p>When you shut down Xalan, you may also want to shut down Xerces and ICU support (if enabled). Keep the following considerations in mind:</p> +<ul> +<li>Once you have shut down Xerces, you can no longer make Xalan or Xerces calls in the current process.<br/><br/></li> +<li>Shut down ICU support if you have enabled it (see <link anchor="icusupport">enabling ICU support</link>) and if the application is exiting or no longer requires the ICU. The <code>XMLPlatformUtils::Terminate()</code> call does nothing if ICU support has not been enabled.</li> +</ul> <p>Use the static terminators.</p> <source>XalanTransformer::terminate(); -XMLPlatformUtils::Terminate();</source> - <note>Once you have shut down Xerces, you can no longer make Xalan or Xerces calls in the current process.</note> +XMLPlatformUtils::Terminate(); +XalanTransformer::ICUCleanUp();</source> </s3></s2><anchor name="stylepi"/> <s2 title="Using a stylesheet processing instruction"> <p>If you want to use the stylesheet referred to by a stylesheet processing instruction in the XMl document, simply call transform() without the second XSLTInputSource argument. For example:</p> @@ -328,7 +333,7 @@ <br/><em>Important</em> For Windows, be sure to install the ICU on the same drive and at the same level as &xslt4c; and &xml4c;.<br/><br/></li> <li>Set the ICU_DATA environment variable as indicated in the readme.html.</li> - </ol> + </ol><anchor name="icusupport"/> <s3 title="Enabling ICU support for encoding"> <p>If you want to enable ICU support for encoding, you must integrate ICU with your &xml4c; build. &xml4c; uses ICU for input encoding. See
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
