vmassol     2002/09/08 12:13:12

  Modified:    documentation/docs/xdocs Tag: CACTUS_14_BRANCH todo.xml
  Log:
  updated todo (backport from HEAD in order to update the web site)
  
  Revision  Changes    Path
  No                   revision
  
  
  No                   revision
  
  
  1.17.2.4  +32 -22    jakarta-cactus/documentation/docs/xdocs/todo.xml
  
  Index: todo.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-cactus/documentation/docs/xdocs/todo.xml,v
  retrieving revision 1.17.2.3
  retrieving revision 1.17.2.4
  diff -u -r1.17.2.3 -r1.17.2.4
  --- todo.xml  25 Aug 2002 15:59:24 -0000      1.17.2.3
  +++ todo.xml  8 Sep 2002 19:13:11 -0000       1.17.2.4
  @@ -33,6 +33,17 @@
   
       <category title="Documentation">
         <action>
  +        Update web site for new <code>begin()</code> and <code>end()</code>
  +        methods.
  +      </action>
  +      <action>
  +        Add documentation for the new Initializer feature.
  +      </action>
  +      <action>
  +        Add documentation for a new way to start Cactus tests by using the
  +        Jetty Initializer.
  +      </action>
  +      <action>
           Add a tutorial for building Cactus from the source distribution.
         </action>
         <action>
  @@ -66,28 +77,29 @@
   
       <category title="Design/Code">
         <action>
  +        Add support for Servlet API 2.4 (and test with Tomcat 5). 
  +      </action>
  +      <action>
  +        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.
  +      </action>
  +      <action>
  +             Remove HttpURLConnection and replace it by the one we have submitted
  +             to the HttpClient project.
  +      </action>
  +      <action>
           Improve the ServletTestRunner. Move stylesheet definition to web.xml
           and provide support for XSLT performed inside ServletTestRunner.
         </action>
         <action>
  -        Write a JMS Redirector/Client to test Message Driven Beans.
  +        Continue the JMS Redirector/Client to test Message Driven Beans.
         </action>
         <action assigned-to="Peter Wong, Jason Robertson, Vincent Massol">
           Add support for Form-based authentication.
         </action>
         <action>
  -        Add methods that are called before and after each test, but on the
  -        client side (i.e. before the <code>beginXXX()</code> and
  -        <code>endXXX()</code> methods). They
  -        would act the same way as <code>setUp()</code> and
  -        <code>tearDown()</code> but on the client side. They could be
  -        named <code>init()</code> and <code>destroy()</code>, or maybe we
  -        should rather rename the existing <code>setUp()</code> and
  -        <code>tearDown()</code> and have something consistent like :
  -        <code>setUpClient()</code>, <code>setUpServer()</code>,
  -        <code>tearDownClient()</code> and <code>tearDownServer()</code> ?
  -      </action>
  -      <action>
           Provide support for generating Session cookies and URL Sessions
           (URL rewriting). A description of the mechanism has been
           posted in thread "How does cactus simulate a session" on the
  @@ -108,10 +120,7 @@
         </action>
         <action assigned-to="Hudson Wong, Vincent Massol">
           Add an EJB sample application to demonstrate how to perform EJB
  -        unit testing (the tutorial that explains the process will be part
  -        of Cactus 1.2 but the inclusion of the sample will be delivered
  -        in a subsequent release as it involves some changes in the build
  -        process).
  +        unit testing.
         </action>
       </category>
   
  @@ -124,9 +133,11 @@
           Ideas to explore ...
         </p>
         <action>
  -        Create a new package <code>org.apache.cactus.extensions</code> for
  -        putting extensions to Cactus Test Cases. The first extension
  -        would be an extension that runs a bunch of test at the same time,
  +             Bundling of JUnitEE.
  +      </action>
  +      <action>
  +        Potentially create a Cactus extension
  +        that runs a bunch of test at the same time,
           thus spawing several threads in the container in order to discover
           bugs [Note: We would have to correct the name under which Cactus test
           results are stored in the application context so that it is unique
  @@ -143,8 +154,7 @@
           automatically generating test cases from methods to test, ...
         </action>
         <action>
  -        Integration to Netbeans in general and especially integration with the
  -        Netbeans XTest module.
  +        Integration to Eclipse.
         </action>
         <action assigned-to="Vincent Massol">
           Evaluate the use of AspectJ for writing Cactus test cases.
  
  
  

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

Reply via email to