mrglavas    2004/02/20 10:27:42

  Modified:    java/docs faq-general.xml faq-xs.xml
  Log:
  Fixed some typos. Also we should be using link instead of jump

  for internal references.
  
  Revision  Changes    Path
  1.41      +5 -5      xml-xerces/java/docs/faq-general.xml
  
  Index: faq-general.xml
  ===================================================================
  RCS file: /home/cvs/xml-xerces/java/docs/faq-general.xml,v
  retrieving revision 1.40
  retrieving revision 1.41
  diff -u -r1.40 -r1.41
  --- faq-general.xml   20 Feb 2004 16:38:01 -0000      1.40
  +++ faq-general.xml   20 Feb 2004 18:27:42 -0000      1.41
  @@ -43,10 +43,10 @@
    </q>
    <a>
       <p>
  -Xerces uses the <code>ObjectFactory</code> class to load some classes dynamically, 
e.g. the parser configuration. The <code>ObjectFactory</code> finds the specified 
implementation class by querying the system property, reading 
<code>META-INF/services/factoryId</code> file or using a fallback classname. After the 
implementation is found, the <code>ObjectFactory</code> tries to load the file using 
the context classloader and if it is null, the <code>ObjectFactory</code> uses system 
classloader. 
  +Xerces uses the <code>ObjectFactory</code> class to load some classes dynamically, 
e.g. the parser configuration. The <code>ObjectFactory</code> finds the specified 
implementation class by querying the system property, reading 
<code>META-INF/services/factoryId</code> file or using a fallback classname. After the 
implementation is found, the <code>ObjectFactory</code> tries to load the file using 
the context classloader and if it is null, the <code>ObjectFactory</code> uses the 
system classloader. 
   </p>
   <p>
  -If you run Xerces in the environment, such as WAS, that has multiple classloaders 
you might get ClassCastExceptions thrown from Xerces because different classloaders 
might get involved in loading Xerces classes. For example, ClassCastExceptions may 
occur when utility EAR classes that use Xerces load Xerces classes from WAR modules. 
  +If you run Xerces in an environment, such as WAS, that has multiple classloaders 
you may get ClassCastExceptions thrown from Xerces because different classloaders 
might get involved in loading Xerces classes. For example, ClassCastExceptions may 
occur when utility EAR classes that use Xerces load Xerces classes from WAR modules. 
   </p>
   <p>
   We suggest you read <jump 
href="http://www-106.ibm.com/developerworks/websphere/library/techarticles/0310_searle/searle.html";>"Avoiding
 ClassCastExceptions..."</jump> article which explains a workaround for this problem. 
  @@ -56,7 +56,7 @@
     </a>
    </faq>
    <faq title="Xerces HTML, XHTML, and XML Serializers">
  -   <q>What can I use instead of Xerces HTML, XHTML, or XML serializers?
  +   <q>What can I use instead of Xerces' HTML, XHTML, or XML serializers?
    </q>
    <a>
   <p>
  @@ -89,9 +89,9 @@
   
   <p>
   
  -You can find more details about the future of Xerces serializers in the <jump 
href="http://marc.theaimsgroup.com/?l=xalan-dev&amp;m=107593381313807&amp;w=2";>archives</jump>.
  +You can find more details about the future of Xerces' serializers in the <jump 
href="http://marc.theaimsgroup.com/?l=xalan-dev&amp;m=107593381313807&amp;w=2";>archives</jump>.
   </p>
  -<note>The HTML and XHTML serializers (<code>org.apache.xml.serialize</code>) have 
been <code>deprecated</code> in Xerces 2.6.2 release. We might deprecate 
<code>XMLSerializer</code> in the future release.</note>
  +<note>The HTML and XHTML serializers (<code>org.apache.xml.serialize</code>) have 
been <code>deprecated</code> in the Xerces 2.6.2 release. We might deprecate 
<code>XMLSerializer</code> in a future release.</note>
     </a>
    </faq>
    <faq title="Obtaining smaller jars">
  
  
  
  1.12      +4 -4      xml-xerces/java/docs/faq-xs.xml
  
  Index: faq-xs.xml
  ===================================================================
  RCS file: /home/cvs/xml-xerces/java/docs/faq-xs.xml,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- faq-xs.xml        20 Feb 2004 16:55:04 -0000      1.11
  +++ faq-xs.xml        20 Feb 2004 18:27:42 -0000      1.12
  @@ -60,11 +60,11 @@
        Xerces implements the <jump 
href="http://www.w3.org/Submission/2004/SUBM-xmlschema-api-20040122/";>XML Schema 
API</jump> specification that defines an API for accessing and querying the post 
schema validation infoset (PSVI) as defined in <jump 
href='http://www.w3.org/TR/xmlschema-1/#PSVI_contributions'>
          Contributions to the post-schema-validation infoset (Appendix C.2)</jump>. 
             This API also defines interfaces for loading XML schema documents. 
  -</p>
  -<p>For more information please refer to the <jump 
href="api.html#xml-schema-api-documentation">interfaces</jump>.
  - 
         </p>
  -<note>The Xerces 2.6.2 release fixes a documentation bug in the <jump 
href="http://www.w3.org/Submission/2004/SUBM-xmlschema-api-20040122/";>XML Schema 
API</jump>. In particular in the XSModel interface the order of the parameters in 
getTypeDefinition, getNotationDeclaration, getModelGroupDefinition, 
getElementDeclaration, getAttributeDeclaration, getAttributeGroup methods have been 
changes from (String namespace, String name) to (String name, String namespace). 
  +      <p>For more information please refer to the 
  +         <link idref='api' anchor='xml-schema-api-documentation'>interfaces</link>.
  +      </p>
  +<note>The Xerces 2.6.2 release fixes a documentation bug in the <jump 
href="http://www.w3.org/Submission/2004/SUBM-xmlschema-api-20040122/";>XML Schema 
API</jump>. In particular in the XSModel interface the order of the parameters in 
getTypeDefinition, getNotationDeclaration, getModelGroupDefinition, 
getElementDeclaration, getAttributeDeclaration, getAttributeGroup methods have been 
changed from (String namespace, String name) to (String name, String namespace). 
   </note>
       </a>
     </faq>
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to