You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xerces.apache.org by bo...@apache.org on 2010/04/21 17:03:56 UTC

svn commit: r936341 - in /xerces/c/trunk/doc: build.xml migration.xml migration_archive.xml

Author: borisk
Date: Wed Apr 21 15:03:56 2010
New Revision: 936341

URL: http://svn.apache.org/viewvc?rev=936341&view=rev
Log:
Documentation updates for 3.1.1.

Modified:
    xerces/c/trunk/doc/build.xml
    xerces/c/trunk/doc/migration.xml
    xerces/c/trunk/doc/migration_archive.xml

Modified: xerces/c/trunk/doc/build.xml
URL: http://svn.apache.org/viewvc/xerces/c/trunk/doc/build.xml?rev=936341&r1=936340&r2=936341&view=diff
==============================================================================
--- xerces/c/trunk/doc/build.xml (original)
+++ xerces/c/trunk/doc/build.xml Wed Apr 21 15:03:56 2010
@@ -291,22 +291,25 @@
             directory:</p>
 
 <source>
-(For VC7.1) projects\Win32\VC7.1\xerces-all\xerces-all.sln
-(For VC8)   projects\Win32\VC8\xerces-all\xerces-all.sln
-(For VC9)   projects\Win32\VC9\xerces-all\xerces-all.sln
+(For VC7.1)  projects\Win32\VC7.1\xerces-all\xerces-all.sln
+(For VC8.0)  projects\Win32\VC8\xerces-all\xerces-all.sln
+(For VC9.0)  projects\Win32\VC9\xerces-all\xerces-all.sln
+(For VC10.0) projects\Win32\VC10\xerces-all\xerces-all.sln
 </source>
 
             <p>Once you have the solution open, you need to build the
                project named <code>XercesLib</code>. You can select
-               Debug/Release, Static/DLL, and, for VC8 and VC9, 32/64 bit
-               builds using the Configuration Manager dialog. You
-               can also select whether the &XercesCName; library
+               Debug/Release, Static/DLL, and, for VC8, VC9, and VC10,
+               32/64 bit builds using the Configuration Manager dialog.
+               You can also select whether the &XercesCName; library
                should use ICU for transcoding.</p>
 
             <p>When building your own applications you need to make sure
                that you are linking your application with the
-               &XercesC3WindowsLib;.lib library (or Debug/Static version of it)
-               and also that the associated DLL is somewhere in the
+               &XercesC3WindowsLib;.lib (Release) and/or
+               &XercesC3WindowsLib;D.lib (Debug)
+               libraries (or the static versions of them)
+               and also that the associated DLLs are somewhere in the
                executable/DLL search path (<code>PATH</code>).</p>
 
             <note>If you are linking your application to the static
@@ -316,8 +319,7 @@
                   to turn off the DLL import/export mechanism.</note>
 
             <p>If you would also like to build tests and/or samples, inside
-               the solution files mentioned above (<code>xerces-all.dsw</code>
-               or <code>xerces-all.sln</code>), you'll find several other
+               the solution files mentioned above, you'll find several other
                projects which are for the tests and samples. Select all
                the tests/samples that you would like to build and then
                right click on the selection. Choose "Build (selection

Modified: xerces/c/trunk/doc/migration.xml
URL: http://svn.apache.org/viewvc/xerces/c/trunk/doc/migration.xml?rev=936341&r1=936340&r2=936341&view=diff
==============================================================================
--- xerces/c/trunk/doc/migration.xml (original)
+++ xerces/c/trunk/doc/migration.xml Wed Apr 21 15:03:56 2010
@@ -21,69 +21,14 @@
 <s1 title="Migration">
     <s2 title="Migration Archive">
 
-       <p>For migration information on earlier versions of &XercesCName; 2
+       <p>For migration information on earlier versions of &XercesCName;
           please refer to <link idref="migrate-archive-&XercesC3Series;">Migration Archive</link>.</p>
 
     </s2>
 
-    <s2 title="Migrating from &XercesCName; 3.0.0 to &XercesCName; &XercesC3Version;">
-      <p>The following section is a discussion of the technical differences between
-      &XercesCName; 3.0.0 and &XercesCName; &XercesC3Version;.</p>
-
-      <p>Topics discussed are:</p>
-      <ul>
-        <li><link anchor="NewFeatures300">New features in &XercesCName; &XercesC3Version;</link></li>
-        <li><link anchor="API300">Public API Changes</link></li>
-      </ul>
-
-    <anchor name="NewFeatures300"/>
-    <s3 title="New features in &XercesCName; &XercesC3Version;">
-      <ul>
-    <li>Working multi-import support. The support for handling multiple import
-        declarations with the same target namespaces has been improved and
-        thoroughly tested. Furthermore, the same logic was extended to
-        loadGrammar and the schemaLocation attributes so that you can load
-        several schemas with the same namespace and/or "add" more declarations
-        with the schemaLocation attributes. To enable this feature, set the
-        XMLUni::fgXercesHandleMultipleImports feature/parameter to true.
-        Starting with this release all the tests and examples have multi-import
-        support enabled by default.</li>
-
-    <li>New property, XMLUni::fgXercesLowWaterMark, allows to configure the
-        parser buffer low water mark. In particular, setting this value to 0
-        disables data caching in the parser which can be useful if you want
-        the SAX events to be dispatched as soon as the data is available.</li>
-
-    <li>DOMLSParser::parseWithContext implementation. In particular, this
-        functionality allows one to parse a document fragment with missing
-        namespace declarations as long as the context document provides them.</li>
-
-    <li>Improved performance and reduced memory footprint when validating with
-        large maxOccurs values. If available, the SSE2 instructions are used to
-        further speedup this case.</li>
-
-    <li>Improved scalability of the XML Schema identity checking (key, keyref,
-        and unique).</li>
-
-    <li>Multiple XML Schema conformance fixes.</li>
-
-    <li>More robust external library detection (libcurl and ICU). In particular,
-        the build system no longer tries to inject any additional paths such as
-        /usr or /usr/local.</li>
-
-    <li>Compilation of the ICU message loader resources no longer depends on
-        the ICU implementation details.</li>
-      </ul>
-    </s3>
-
-    <anchor name="API300"/>
-    <s3 title="Public API Changes">
-
-        <p>&XercesCName; &XercesC3Version; is a minor release and does
-           not include any public API changes that would preclude
-           applications using the previous version of &XercesCName; from
-           building successfully with this version.</p>
-    </s3>
+    <s2 title="Migrating from &XercesCName; 3.1.0 to &XercesCName; &XercesC3Version;">
+      <p>&XercesCName; &XercesC3Version; is a bugfix-only release and is
+         binary-compatible with &XercesCName; 3.1.0.</p>
     </s2>
 
 </s1>

Modified: xerces/c/trunk/doc/migration_archive.xml
URL: http://svn.apache.org/viewvc/xerces/c/trunk/doc/migration_archive.xml?rev=936341&r1=936340&r2=936341&view=diff
==============================================================================
--- xerces/c/trunk/doc/migration_archive.xml (original)
+++ xerces/c/trunk/doc/migration_archive.xml Wed Apr 21 15:03:56 2010
@@ -21,6 +21,8 @@
 <s1 title="Migration Archive">
     <s2 title="Migrating to earlier Releases">
       <ul>
+        <li><link anchor="Migrateto310">Migrating from &XercesCName; 3.0.1 to 3.1.0</link></li>
+        <li><link anchor="Migrateto301">Migrating from &XercesCName; 3.0.0 to 3.0.1</link></li>
 	<li><link anchor="Migrateto300">Migrating from &XercesCName; 2.8.0 to 3.0.0</link></li>
         <li><link anchor="Migrateto280">Migrating from &XercesCName; 2.7.0 to 2.8.0</link></li>
         <li><link anchor="Migrateto270">Migrating from &XercesCName; 2.6.0 to 2.7.0</link></li>
@@ -38,6 +40,73 @@
       </ul>
     </s2>
 
+    <anchor name="Migrateto310"/>
+    <s2 title="Migrating from &XercesCName; 3.0.1 to &XercesCName; 3.1.0">
+      <p>The following section is a discussion of the technical differences between
+      &XercesCName; 3.0.1 and &XercesCName; 3.1.0.</p>
+
+      <p>Topics discussed are:</p>
+      <ul>
+        <li><link anchor="NewFeatures310">New features in &XercesCName; 3.1.0</link></li>
+        <li><link anchor="API310">Public API Changes</link></li>
+      </ul>
+
+    <anchor name="NewFeatures310"/>
+    <s3 title="New features in &XercesCName; 3.1.0">
+      <ul>
+    <li>Working multi-import support. The support for handling multiple import
+        declarations with the same target namespaces has been improved and
+        thoroughly tested. Furthermore, the same logic was extended to
+        loadGrammar and the schemaLocation attributes so that you can load
+        several schemas with the same namespace and/or "add" more declarations
+        with the schemaLocation attributes. To enable this feature, set the
+        XMLUni::fgXercesHandleMultipleImports feature/parameter to true.
+        Starting with this release all the tests and examples have multi-import
+        support enabled by default.</li>
+
+    <li>New property, XMLUni::fgXercesLowWaterMark, allows to configure the
+        parser buffer low water mark. In particular, setting this value to 0
+        disables data caching in the parser which can be useful if you want
+        the SAX events to be dispatched as soon as the data is available.</li>
+
+    <li>DOMLSParser::parseWithContext implementation. In particular, this
+        functionality allows one to parse a document fragment with missing
+        namespace declarations as long as the context document provides them.</li>
+
+    <li>Improved performance and reduced memory footprint when validating with
+        large maxOccurs values. If available, the SSE2 instructions are used to
+        further speedup this case.</li>
+
+    <li>Improved scalability of the XML Schema identity checking (key, keyref,
+        and unique).</li>
+
+    <li>Multiple XML Schema conformance fixes.</li>
+
+    <li>More robust external library detection (libcurl and ICU). In particular,
+        the build system no longer tries to inject any additional paths such as
+        /usr or /usr/local.</li>
+
+    <li>Compilation of the ICU message loader resources no longer depends on
+        the ICU implementation details.</li>
+      </ul>
+    </s3>
+
+    <anchor name="API310"/>
+    <s3 title="Public API Changes">
+
+        <p>&XercesCName; 3.1.0 is a minor release and does
+           not include any public API changes that would preclude
+           applications using the previous version of &XercesCName; from
+           building successfully with this version.</p>
+    </s3>
+    </s2>
+
+    <anchor name="Migrateto301"/>
+    <s2 title="Migrating from &XercesCName; 3.0.0 to &XercesCName; 3.0.1">
+      <p>&XercesCName; 3.0.1 is a bugfix-only release and is
+         binary-compatible with &XercesCName; 3.0.0.</p>
+    </s2>
+
     <anchor name="Migrateto300"/>
     <s2 title="Migrating from &XercesCName; 2.8.0 to &XercesCName; 3.0.0">
       <p>The following section is a discussion of the technical differences between



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xerces.apache.org
For additional commands, e-mail: commits-help@xerces.apache.org