cvs commit: jakarta-commons/cactus/docs/framework/xdocs todo.xml

[vmassol]

vmassol     01/07/04 07:35:23

  Modified:    cactus/docs/framework/xdocs todo.xml
  Log:
  updated volunteers
  
  Revision  Changes    Path
  1.32      +3 -3      jakarta-commons/cactus/docs/framework/xdocs/todo.xml
  
  Index: todo.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/cactus/docs/framework/xdocs/todo.xml,v
  retrieving revision 1.31
  retrieving revision 1.32
  diff -u -r1.31 -r1.32
  --- todo.xml  2001/07/03 09:01:44     1.31
  +++ todo.xml  2001/07/04 14:35:18     1.32
  @@ -39,7 +39,7 @@
         <action>
           Add a tutorial for building Cactus from the source distribution.
         </action>
  -      <action>
  +      <action assigned-to="Hudson Wong">
           Add a tutorial that explains how to unit test EJBs in the current
           version of Cactus.
         </action>
  @@ -47,7 +47,7 @@
           Write a tutorial that explains how to unit test Tag libraries (only
           taglets that extend TagSupport for the moment).
         </action>
  -      <action>
  +      <action assigned-to="C�dric Chabanois, Kunal Vaishnav">
           Write a Cactus integration tutorial for JBuilder 4/5 that explains how
           to run Cactus tests within JBuilder4/5.
         </action>
  @@ -187,7 +187,7 @@
           Mock objects). Now we need to think on how we could bring the benefits
           of both approach together and whether it is feasible on not.
         </action>
  -      <action>
  +      <action assigned-to="Vincent Massol, Alex Fern&aacute;ndez">
           When we want to unit test classes written for the Struts framework
           (for example), we can use Cactus to provide access to all Servlet API
           implicit objects. However, there is still a need to get access to