You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cactus-dev@jakarta.apache.org by vm...@apache.org on 2003/10/23 16:36:51 UTC

cvs commit: jakarta-cactus/documentation/docs/xdocs/writing howto_testcase_jsp.xml

vmassol     2003/10/23 07:36:51

  Modified:    documentation/docs/xdocs/participating Tag: CACTUS_15_BRANCH
                        todo.xml howto_build.xml
               documentation/docs/xdocs Tag: CACTUS_15_BRANCH downloads.xml
                        changes.xml sitemap.xml mock_vs_cactus.xml
                        how_it_works.xml cactusname.xml faq.xml goals.xml
                        changes_archive.xml testedon.xml
               documentation/docs/xdocs/integration/ant Tag:
                        CACTUS_15_BRANCH howto_ant_primer.xml
               documentation/docs/xdocs/integration Tag: CACTUS_15_BRANCH
                        howto_config.xml
               documentation/docs/xdocs/writing Tag: CACTUS_15_BRANCH
                        howto_testcase_jsp.xml
  Log:
  Merged from HEAD as these changes will  be released in Cactus 1.5 beta2.
  
  Revision  Changes    Path
  No                   revision
  No                   revision
  1.36.2.2  +14 -6     jakarta-cactus/documentation/docs/xdocs/participating/todo.xml
  
  Index: todo.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-cactus/documentation/docs/xdocs/participating/todo.xml,v
  retrieving revision 1.36.2.1
  retrieving revision 1.36.2.2
  diff -u -r1.36.2.1 -r1.36.2.2
  --- todo.xml	9 Aug 2003 14:21:09 -0000	1.36.2.1
  +++ todo.xml	23 Oct 2003 14:36:50 -0000	1.36.2.2
  @@ -57,6 +57,9 @@
           Improve the documentation CheckSitemap Ant task to check external URLs
           (when online).
         </action>
  +      <action>
  +        Document the new features for Cactus logging.
  +      </action>
       </category>
   
       <category title="Build Process">
  @@ -66,6 +69,10 @@
           negates this nice feature...
         </action>
         <action>
  +        Add an automated Maven build (using codehaus). See
  +        http://wiki.codehaus.org/general/CodehausBuildmeister.
  +      </action>
  +      <action>
           Prevent the sample jetty project from building if the J2EE API
           is 1.2.
         </action>
  @@ -75,7 +82,7 @@
           zips). Same as what is on 
           http://dev.eclipse.org/viewcvs/indextech.cgi/~checkout~/org.eclipse.ajdt/download.html.
         </action>
  -      <action assigned-to="Jason Van Zyl">
  +      <action assigned-to="Julien Dubois, Vincent Massol">
           Move Cactus to Maven.
         </action>
         <action>
  @@ -89,16 +96,16 @@
       
       <category title="Design/Code">
         <action>
  +        Cleanly separate what is public API from what isn't. Also
  +        use the final keyword to improve future extensibility.
  +      </action>
  +      <action>
           Modify the Eclipse plugin to use the new Ant integration.
         </action>
         <action>
           Enhance the <code>runservertests</code> task to accept nested
           <code>&lt;containerset&gt;</code> elements.
         </action>
  -      <action assigned-to="Hudson Wong, Vincent Massol">
  -        Add an EJB sample application to demonstrate how to perform EJB
  -        unit testing.
  -      </action>
         <action assigned-to="Jason Robertson, Vincent Massol">
           Add test case for form-based authentication.
         </action>
  @@ -116,7 +123,8 @@
           Potentially replace access to instance variables of redirectors by 
           method calls. For example, replace "request.xxx()" by 
           "getHttpServletRequest().xxx()". Deprecate the direct access. Needs
  -        to be discussed on cactus-dev.
  +        to be discussed on cactus-dev. Also, deprecate XXXTestCase in favor
  +        of test suites.
         </action>
         <action>
           Add support for multi-concurrent Cactus tests. This involves storing
  
  
  
  1.10.2.1  +7 -16     jakarta-cactus/documentation/docs/xdocs/participating/howto_build.xml
  
  Index: howto_build.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-cactus/documentation/docs/xdocs/participating/howto_build.xml,v
  retrieving revision 1.10
  retrieving revision 1.10.2.1
  diff -u -r1.10 -r1.10.2.1
  --- howto_build.xml	29 Jun 2003 11:13:56 -0000	1.10
  +++ howto_build.xml	23 Oct 2003 14:36:50 -0000	1.10.2.1
  @@ -63,7 +63,7 @@
       <section title="Prerequisites">
         <p>
           To build Cactus from source, you'll need to have
  -        <link href="ext:ant">Ant</link> 1.5.1 (or later)
  +        <link href="ext:ant">Ant</link> 1.5.3 (or later)
           installed. Please make sure that the distribution also includes the JAR
           containing the optional tasks (<code>optional.jar</code>). In addition,
           please add an XSLT processor (like
  @@ -95,7 +95,7 @@
               <td nowrap="true">
                 <link href="ext:commons_logging">aspectjrt.jar</link>
               </td>
  -            <td nowrap="true">1.0.6 or later</td>
  +            <td nowrap="true">1.1.1 or later</td>
               <td>
                 The AspectJ runtime.
               </td>
  @@ -104,25 +104,16 @@
               <td nowrap="true">
                 <link href="ext:aspectj">aspectjtools.jar</link>
               </td>
  -            <td nowrap="true">1.0.6 or later</td>
  +            <td nowrap="true">1.1.0 or later</td>
               <td>
                 The AspectJ compiler and other tools.
               </td>
             </tr>
             <tr>
  -            <td><link href="ext:aspectj">aspectj-ant.jar</link></td>
  -            <td nowrap="true">1.0.6 or later</td>
  -            <td>
  -              The AspectJ Ant tasks.<br/>
  -              <em>Since version 1.1 of AspectJ, the Ant tasks are included
  -              in <code>aspectjtools.jar</code>.</em>
  -            </td>
  -          </tr>
  -          <tr>
               <td nowrap="true">
                 <link href="ext:commons_httpclient">commons-httpclient.jar</link>
               </td>
  -            <td nowrap="true">2.0 beta 1 or later</td>
  +            <td nowrap="true">2.0 rc1 or later</td>
               <td>
                 Jakarta Commons HttpClient.
               </td>
  @@ -131,7 +122,7 @@
               <td nowrap="true">
                 <link href="ext:commons_logging">commons-logging.jar</link>
               </td>
  -            <td nowrap="true">1.0 or later</td>
  +            <td nowrap="true">1.0.3 or later</td>
               <td>
                 Jakarta Commons Logging.
               </td>
  @@ -140,7 +131,7 @@
               <td nowrap="true">
                 <link href="ext:junit">junit.jar</link>
               </td>
  -            <td nowrap="true">3.7 or later</td>
  +            <td nowrap="true">3.8.1 or later</td>
               <td>
                 The JUnit framework.<br/>
                 <em>This JAR file must be placed in the <code>lib</code>
  @@ -283,7 +274,7 @@
               <td nowrap="true">
                 <link href="ext:taglibs_standard">standard.jar</link>
               </td>
  -            <td nowrap="true">1.0 or later</td>
  +            <td nowrap="true">1.0</td>
               <td>
                 Jakarta Standard Taglib. Required for compiling and running the
                 servlet sample test suite on J2EE 1.3.
  
  
  
  No                   revision
  No                   revision
  1.10.2.2  +12 -3     jakarta-cactus/documentation/docs/xdocs/downloads.xml
  
  Index: downloads.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-cactus/documentation/docs/xdocs/downloads.xml,v
  retrieving revision 1.10.2.1
  retrieving revision 1.10.2.2
  diff -u -r1.10.2.1 -r1.10.2.2
  --- downloads.xml	9 Aug 2003 14:34:13 -0000	1.10.2.1
  +++ downloads.xml	23 Oct 2003 14:36:50 -0000	1.10.2.2
  @@ -112,9 +112,18 @@
   
       <section title="Releases">
   
  -      <p>
  -        Click <link href="ext:cactus_release">here</link> for Cactus releases.
  -      </p>
  +      <ul>
  +        <li>
  +          <link href="ext:cactus_release_bin">Cactus binary releases</link>.
  +        </li>
  +        <li>
  +          <link href="ext:cactus_release_src">Cactus source releases</link>.
  +        </li>
  +      </ul>
  +      <note>
  +        For older Cactus releases (&lt;= 1.4.1), click 
  +        <link href="ext:cactus_release_old">here</link>.
  +      </note>
   
         <note>
           For older Cactus releases (&lt;= 1.4.1), click 
  
  
  
  1.120.2.7 +29 -0     jakarta-cactus/documentation/docs/xdocs/changes.xml
  
  Index: changes.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-cactus/documentation/docs/xdocs/changes.xml,v
  retrieving revision 1.120.2.6
  retrieving revision 1.120.2.7
  diff -u -r1.120.2.6 -r1.120.2.7
  --- changes.xml	7 Sep 2003 20:17:10 -0000	1.120.2.6
  +++ changes.xml	23 Oct 2003 14:36:50 -0000	1.120.2.7
  @@ -68,6 +68,35 @@
         </devs>
   
         <release version="1.5-rc1" date="in CVS">
  +        <action dev="VMA" type="fix" fixes-bug="23604" due-to="Norbert Pabis" due-to-email="npabis@astercity.net">
  +          The Cactus Ant integration now reports the HTTP error code when it 
  +          fails to start the container and timeouts. It was previously doing 
  +          this but only in debug mode.
  +        </action>
  +        <action dev="VMA" type="update">
  +          Update the version of Commons HttpClient in the Cactus distribution to 
  +          1.0 rc2.
  +        </action>
  +        <action dev="VMA" type="fix">
  +          Fixed and improved logging. It now works with Log4j, JDK 1.4 logging
  +          and Commons Simple log. Check the sample servlet application for an
  +          example of how to set up Cactus logging.
  +        </action>
  +        <action dev="VMA" type="add">
  +          Added new optional <code>cactus.logging.config</code> Cactus 
  +          property. If specified Cactus will load the properties file pointed
  +          by this property and will set each property as a system property.
  +        </action>
  +        <action dev="VMA" type="update">
  +          Updated to use AspectJ 1.1.1. When you upgrade to Cactus 1.5-rc1
  +          make sure you update your <code>aspectjrt.jar</code> to version
  +          1.1.1 (the jar is provided in the Cactus distribution).
  +        </action>
  +        <action dev="VMA" type="add">
  +          Added an EJB sample application to demonstrate how to perform EJB
  +          unit testing with Cactus and how to automate it with the 
  +          Cactus/Ant integration.
  +        </action>
           <action dev="VMA" type="fix" due-to="Alexander Ananiev" due-to-email="alexander@myarch.com">
             When using the new <code>ServletTestSuite</code> wrapper around pure
             JUnit test cases, the <code>setUp()</code> and 
  
  
  
  1.54.2.4  +7 -2      jakarta-cactus/documentation/docs/xdocs/sitemap.xml
  
  Index: sitemap.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-cactus/documentation/docs/xdocs/sitemap.xml,v
  retrieving revision 1.54.2.3
  retrieving revision 1.54.2.4
  diff -u -r1.54.2.3 -r1.54.2.4
  --- sitemap.xml	29 Aug 2003 14:16:57 -0000	1.54.2.3
  +++ sitemap.xml	23 Oct 2003 14:36:50 -0000	1.54.2.4
  @@ -398,12 +398,14 @@
     <external id="book_javatools" url="http://www.amazon.com/exec/obidos/ASIN/047120708X/"/>
     <external id="bug_database" url="http://jakarta.apache.org/site/bugs.html"/>
     <external id="bug_database_cactus_open" url="http://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;product=Cactus"/>
  +  <external id="c2_mock_object" url="http://c2.com/cgi/wiki?MockObject"/>
     <external id="c2_vma" url="http://c2.com/cgi/wiki?VincentMassol"/>
     <external id="c2_who_uses_cactus" url="http://c2.com/cgi/wiki?WhoUsesCactus"/>
     <external id="cactus_dutronc_lyrics" url="http://www.muriset.com/paroles/les_cactus.htm"/>
     <external id="cactus_dutronc_midi" url="http://www.muriset.com/musique/les_cactus.mid"/>
     <external id="cactus_nightly" url="http://cvs.apache.org/builds/jakarta-cactus/nightly"/>
  -  <external id="cactus_release" url="http://www.apache.org/dist/jakarta/cactus"/>
  +  <external id="cactus_release_bin" url="http://jakarta.apache.org/site/binindex.cgi"/>
  +  <external id="cactus_release_src" url="http://jakarta.apache.org/site/sourceindex.cgi"/>
     <external id="cactus_release_old" url="http://jakarta.apache.org/builds/jakarta-cactus/release"/>
     <external id="cactus_viewcvs" url="http://cvs.apache.org/viewcvs/jakarta-cactus/"/>
     <external id="checkstyle" url="http://checkstyle.sf.net"/>
  @@ -416,7 +418,8 @@
     <external id="commons_logging" url="http://jakarta.apache.org/commons/logging.html"/>
     <external id="cruisecontrol" url="http://cruisecontrol.sourceforge.net/"/>
     <external id="cvs" url="http://jakarta.apache.org/site/cvsindex.html"/>
  -  <external id="eclipse" url="http://www.eclipse.org"/>  
  +  <external id="easymock" url="http://easymock.org"/>
  +  <external id="eclipse" url="http://www.eclipse.org"/>
     <external id="eblox" url="http://www.eblox.com"/>
     <external id="gump" url="http://jakarta.apache.org/gump/"/>
     <external id="gump_cactus_doc" url="http://cvs.apache.org/builds/gump/latest/jakarta-cactus-documentation.html"/>
  @@ -446,7 +449,9 @@
     <external id="korean" url="http://jakarta.apache-korea.org/cactus/index.html"/>
     <external id="maven" url="http://maven.apache.org"/>
     <external id="maven_cactus" url="http://maven.apache.org/reference/plugins/cactus"/>
  +  <external id="mockmaker" url="http://mockmaker.sourceforge.net/"/>
     <external id="mockobjects" url="http://www.mockobjects.com"/>
  +  <external id="mockobjects_endotesting" url="http://www.mockobjects.com/wiki/MocksObjectsPaper?action=AttachFile&amp;do=get&amp;target=mockobjects.pdf"/>
     <external id="nekohtml" url="http://www.apache.org/~andyc/neko/doc/html/"/>
     <external id="octo" url="http://www.octo.com"/>
     <external id="opensource" url="http://www.opensource.org/"/>
  
  
  
  1.4.4.1   +18 -18    jakarta-cactus/documentation/docs/xdocs/mock_vs_cactus.xml
  
  Index: mock_vs_cactus.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-cactus/documentation/docs/xdocs/mock_vs_cactus.xml,v
  retrieving revision 1.4
  retrieving revision 1.4.4.1
  diff -u -r1.4 -r1.4.4.1
  --- mock_vs_cactus.xml	18 Jan 2003 00:08:32 -0000	1.4
  +++ mock_vs_cactus.xml	23 Oct 2003 14:36:50 -0000	1.4.4.1
  @@ -12,6 +12,12 @@
     <body>
   
       <section title="Mock Objects vs In-Container testing">
  +      <note><strong>
  +        This article was written about 2 years ago and is starting to
  +        be a bit old. The general content is still valid but several
  +        details are no longer true as the frameworks (be it Cactus or
  +        the mock objects frameworks) have evolved since then.
  +      </strong></note>
         <note>
           Throughout this article, we'll use the abbreviations MO for Mock
           Objects and IC for In-Container strategy.
  @@ -52,7 +58,7 @@
           The main goal of MO is to unit test a method in isolation of other
           domain objects. Thus, the MO approach is to fake domain objects
           by using simulated copies instead of the real objects (be careful
  -        MO does not implement any logic in it's fake objects, that would be
  +        MO does not implement any logic in its fake objects, that would be
           "stubbing". All behaviours of mock objects are controlled by the unit
           test itself). This enables to
           finely unit test the method with no environment
  @@ -417,35 +423,29 @@
         <p>
           <ul>
             <li>
  -            <link href="http://mockobjects.sourceforge.net/endotesting.html">
  +            <link href="ext:mockobjects_endotesting">
               "Endo-Testing: Unit Testing with Mock Objects"</link> (PDF).
               Describes the vision behind MO.
             </li>
             <li>
  -            <link href="http://c2.com/ppr/wiki/RecentChanges/MockObject.html">
  -            Mock Object discussions on Wiki</link>.
  +            <link href="ext:c2_mock_object">Mock Object discussions on 
  +            Wiki</link>.
             </li>
             <li>
  -            <link href="http://mockobjects.sourceforge.net">Mock Object
  -            project</link> on SourceForge. MO framework and some mock
  -            implementations.
  +            <link href="ext:mockobjects">Mock Object project</link> on 
  +            SourceForge. MO framework and some static mock implementations.
  +            Also supports runtime mocks using Dynamic Proxies.
             </li>
             <li>
  -            <link
  -            href="http://www.xpdeveloper.com/cgi-bin/wiki.cgi?MockMaker">Mock
  -            Maker</link>. Generates build time MO implementations for the
  -            SourceForge Mock Objects project. Generation is done from
  -            interfaces.
  +            <link href="ext:mockmaker">MockMaker</link>. Generates build 
  +            time MO implementations for the SourceForge Mock Objects project.
  +            Generation is done from interfaces or classes.
             </li>
             <li>
  -            <link href="http://tammofreese.de/easymock/">Easy Mock</link>.
  -            Uses dynamic proxies (JDK 1.3) to provide runtime
  +            <link href="ext:easymock">Easy Mock</link>.
  +            Uses Dynamic Proxies (JDK 1.3) to provide runtime
               mock implementations, thus eliminating the need for generating/
               writing the mock implementations.
  -          </li>
  -          <li>
  -            <link href="http://www.xpdeveloper.com">xpdeveloper.com</link> web
  -            site and it's Extreme Tuesday Club (Xtc) ...
             </li>
           </ul>
         </p>
  
  
  
  1.7.4.1   +2 -2      jakarta-cactus/documentation/docs/xdocs/how_it_works.xml
  
  Index: how_it_works.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-cactus/documentation/docs/xdocs/how_it_works.xml,v
  retrieving revision 1.7
  retrieving revision 1.7.4.1
  diff -u -r1.7 -r1.7.4.1
  --- how_it_works.xml	18 Jan 2003 00:08:32 -0000	1.7
  +++ how_it_works.xml	23 Oct 2003 14:36:50 -0000	1.7.4.1
  @@ -116,9 +116,9 @@
           </li>
           <li>
             If an exception has been raised, the Redirector proxy returns the
  -          information about the exception (it's name, class, stack trace) back
  +          information about the exception (its name, class, stack trace) back
             to the client side. Information about the exception will then be
  -          printed by JUnit in it's Test Runner console.
  +          printed by JUnit in its Test Runner console.
           </li>
           <li>
             If no exception occurred, the <code>YYYTestCase.runTest()</code>
  
  
  
  1.7.2.1   +1 -1      jakarta-cactus/documentation/docs/xdocs/cactusname.xml
  
  Index: cactusname.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-cactus/documentation/docs/xdocs/cactusname.xml,v
  retrieving revision 1.7
  retrieving revision 1.7.2.1
  diff -u -r1.7 -r1.7.2.1
  --- cactusname.xml	12 Jul 2003 21:32:17 -0000	1.7
  +++ cactusname.xml	23 Oct 2003 14:36:50 -0000	1.7.2.1
  @@ -65,7 +65,7 @@
           <li>
             A Cactus is full of spines. Visually you can imagine that a piece of
             code that has gone through this rigourous and comprehensive testing
  -          has had all it's bug revealed ! ...
  +          has had all its bug revealed ! ...
           </li>
           <li>
             We can imagine a motto like "Tested on Apache-Cactus" !
  
  
  
  1.15.2.2  +26 -0     jakarta-cactus/documentation/docs/xdocs/faq.xml
  
  Index: faq.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-cactus/documentation/docs/xdocs/faq.xml,v
  retrieving revision 1.15.2.1
  retrieving revision 1.15.2.2
  diff -u -r1.15.2.1 -r1.15.2.2
  --- faq.xml	9 Aug 2003 14:34:46 -0000	1.15.2.1
  +++ faq.xml	23 Oct 2003 14:36:50 -0000	1.15.2.2
  @@ -58,6 +58,10 @@
             <jump anchor="faq11">What version of Eclipse do I need for the 
             Eclipse plugin?</jump>
           </li>
  +        <li>
  +          <jump anchor="faq12">Why do I get an HttpClient NoSuchMethodError when 
  +          running Cactus tests with JBoss 3.x?</jump>
  +        </li>
         </ul>
       </section>
   
  @@ -491,6 +495,28 @@
           It has not yet been tested with Eclipse 3.0.
         </p>      	
   
  +	</section>
  +
  +    <anchor id="faq12"/>
  +    <section title="Why do I get an HttpClient NoSuchMethodError when running Cactus tests with JBoss 3.x?">
  +
  +      <section title="Question">
  +        <p>
  +          When running my Cactus tests with JBoss 3.x, I get:
  +        </p>
  +<source><![CDATA[           
  +java.lang.NoSuchMethodError: 
  +  org.apache.commons.httpclient.methods.GetMethod.setRequestHeader(
  +  Ljava/lang/String;Ljava/lang/String;)V at [...]
  +]]></source>
  +      </section>
  +      <section title="Solution">
  +        <p>
  +          JBoss 3.x bundles an old version of HttpClient and Cactus requires a
  +          newer version. Just replace the HttpClient version in JBoss by the
  +          one provided by Cactus.
  +        </p>
  +      </section>
   	</section>
   
     </body>
  
  
  
  1.12.2.1  +1 -1      jakarta-cactus/documentation/docs/xdocs/goals.xml
  
  Index: goals.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-cactus/documentation/docs/xdocs/goals.xml,v
  retrieving revision 1.12
  retrieving revision 1.12.2.1
  diff -u -r1.12 -r1.12.2.1
  --- goals.xml	13 Jul 2003 10:42:42 -0000	1.12
  +++ goals.xml	23 Oct 2003 14:36:50 -0000	1.12.2.1
  @@ -96,7 +96,7 @@
               ensuring that the code behaves ok. Indeed, as the components will
               rely more and more on the container's services, the confidence that
               the tests will run well when deployed will decrease and the need
  -            for a solution that ensures the code will run correctly in it's
  +            for a solution that ensures the code will run correctly in its
               environment will increase,
             </li>
             <li>
  
  
  
  1.1.2.1   +1 -1      jakarta-cactus/documentation/docs/xdocs/changes_archive.xml
  
  Index: changes_archive.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-cactus/documentation/docs/xdocs/changes_archive.xml,v
  retrieving revision 1.1
  retrieving revision 1.1.2.1
  diff -u -r1.1 -r1.1.2.1
  --- changes_archive.xml	13 Jul 2003 10:32:08 -0000	1.1
  +++ changes_archive.xml	23 Oct 2003 14:36:50 -0000	1.1.2.1
  @@ -525,7 +525,7 @@
         </action>
         <action dev="VMA" type="add">
           Added a new target called <code>deploy-site</code> that automatically
  -        deploy the generated web site to it's home page on the Jakarta server.
  +        deploy the generated web site to its home page on the Jakarta server.
           This will be very useful when integrated with GUMP nightly builds so
           that the web site is always up to date.
         </action>
  
  
  
  1.38.2.3  +3 -2      jakarta-cactus/documentation/docs/xdocs/testedon.xml
  
  Index: testedon.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-cactus/documentation/docs/xdocs/testedon.xml,v
  retrieving revision 1.38.2.2
  retrieving revision 1.38.2.3
  diff -u -r1.38.2.2 -r1.38.2.3
  --- testedon.xml	10 Aug 2003 14:00:54 -0000	1.38.2.2
  +++ testedon.xml	23 Oct 2003 14:36:50 -0000	1.38.2.3
  @@ -111,8 +111,9 @@
               <td>1.6.0b, 2.0.1, 2.0.2</td>
               <td>1.2, 1.3</td>
               <td>
  -              Does <strong>not</strong> work under JDK version 1.4 or later
  -              but works with JDK 1.3.1.
  +              Make sure you put the <code>tools.jar</code> corresponding to
  +              the JDK you are using in <code>ORION_HOME</code> (i.e the place
  +              where you installed Orion).
               </td>
             </tr>
             <tr>
  
  
  
  No                   revision
  No                   revision
  1.3.4.1   +1 -1      jakarta-cactus/documentation/docs/xdocs/integration/ant/howto_ant_primer.xml
  
  Index: howto_ant_primer.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-cactus/documentation/docs/xdocs/integration/ant/howto_ant_primer.xml,v
  retrieving revision 1.3
  retrieving revision 1.3.4.1
  diff -u -r1.3 -r1.3.4.1
  --- howto_ant_primer.xml	25 Apr 2003 13:54:32 -0000	1.3
  +++ howto_ant_primer.xml	23 Oct 2003 14:36:50 -0000	1.3.4.1
  @@ -893,7 +893,7 @@
               you need to deliver a jar file. We also include a manifest file
               in the jar, with version information. We copy the manifest to the
               output directory in order to replace the <code>@version@</code>
  -            token with it's value.
  +            token with its value.
             </p>
   
             <p>
  
  
  
  No                   revision
  No                   revision
  1.1.2.1   +1 -1      jakarta-cactus/documentation/docs/xdocs/integration/howto_config.xml
  
  Index: howto_config.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-cactus/documentation/docs/xdocs/integration/howto_config.xml,v
  retrieving revision 1.1
  retrieving revision 1.1.2.1
  diff -u -r1.1 -r1.1.2.1
  --- howto_config.xml	6 May 2003 16:11:09 -0000	1.1
  +++ howto_config.xml	23 Oct 2003 14:36:51 -0000	1.1.2.1
  @@ -288,7 +288,7 @@
             copy the <code>jspRedirector.jsp</code> file (found in the
             <code>sample/web</code> directory where you unpacked your
             Cactus distribution) in a directory in your webapp and you need to
  -          put it's relative path in the mapping defined above (here we
  +          put its relative path in the mapping defined above (here we
             have put it in the webapp root.
           </note>
   
  
  
  
  No                   revision
  No                   revision
  1.5.4.1   +1 -1      jakarta-cactus/documentation/docs/xdocs/writing/howto_testcase_jsp.xml
  
  Index: howto_testcase_jsp.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-cactus/documentation/docs/xdocs/writing/howto_testcase_jsp.xml,v
  retrieving revision 1.5
  retrieving revision 1.5.4.1
  diff -u -r1.5 -r1.5.4.1
  --- howto_testcase_jsp.xml	28 Jan 2003 15:48:18 -0000	1.5
  +++ howto_testcase_jsp.xml	23 Oct 2003 14:36:51 -0000	1.5.4.1
  @@ -475,7 +475,7 @@
                   this object (the old out object is saved) to capture all of the 
                   response writing that goes on in the body of the tag. After the 
                   tag's body has been evaluated, the tag itself has a chance to 
  -                do something with the result of the evaluation in it's 
  +                do something with the result of the evaluation in its 
                   <code>doAfterBody()</code> method. After the tag has completed 
                   its execution, the container restores the old out object with
                   a call to <code>pageContext.popBody()</code>.
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org