dleslie     02/02/01 11:10:15

  Modified:    java/xdocs/sources/xalan index.xml
  Log:
  Editorial cleanup for 2.3.
  
  Revision  Changes    Path
  1.45      +3 -4      xml-xalan/java/xdocs/sources/xalan/index.xml
  
  Index: index.xml
  ===================================================================
  RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/index.xml,v
  retrieving revision 1.44
  retrieving revision 1.45
  diff -u -r1.44 -r1.45
  --- index.xml 1 Feb 2002 17:11:08 -0000       1.44
  +++ index.xml 1 Feb 2002 19:10:14 -0000       1.45
  @@ -72,10 +72,9 @@
        <note>&xslt4j; version 1 is no longer supported and no longer available 
from xml.apache.org.</note>
     </s2>
     <s2 title="How about this release?">
  -  <p>&xslt4j-current; works with &xml4j; version 2, and the distribution 
includes xercesImpl.jar from &xml4j-used;. For the time being, &xslt4j; 
  -  maintains backwards compatiblity with &xml4j; version 1.</p>
  -  <p>Support for the &xslt4j; release 1 API, which predates the design of 
the <resource-ref idref="jaxp11"/>JAXP 1.1/<link idref="trax">TrAX
  -  </link> interfaces, has been dropped.</p>
  +  <p>&xslt4j-current; works with &xml4j; version 2, and the distribution 
includes xercesImpl.jar from &xml4j-used;. &xslt4j-current; is also
  +  compatible with &xml4j; version 1.</p>
  +  <p>Support for the &xslt4j; release 1 API, which predates the design of 
the JAXP 1.1/TrAX interfaces, has been dropped.</p>
     <p>The &xslt4j; implementation is in xalan.jar. The SAX, DOM, and JAVAX 
interfaces are in xml-apis.jar. These interfaces are shared by a 
     number of tools (&xslt4j;, &xml4j;, etc.), so placing them in a separate 
JAR simplifies coordination and reduces risk of duplication. 
     <em>Be sure to put both JAR files (and xercesImpl.jar or another JAXP 
1.1-compliant XML parser) on your classpath!</em></p>
  
  
  

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

Reply via email to