vmassol     01/08/05 22:20:11

  Modified:    cactus/docs/framework/xdocs mockobjects.xml
  Log:
  updated links to mockobjects project to reflect new project web site
  
  Revision  Changes    Path
  1.4       +3 -3      jakarta-commons/cactus/docs/framework/xdocs/mockobjects.xml
  
  Index: mockobjects.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/cactus/docs/framework/xdocs/mockobjects.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- mockobjects.xml   2001/08/05 11:08:30     1.3
  +++ mockobjects.xml   2001/08/06 05:20:11     1.4
  @@ -45,7 +45,7 @@
           MO is a strategy to unit test java classes in general. As such
           it is also applicable to unit test server side code like Servlets,
           Filters, Taglibs, EJBs, ... See the original article
  -        <link href="http://www.sidewize.com/company/mockobjects.pdf";>
  +        <link href="http://mockobjects.sourceforge.net/endotesting.html";>
           "Endo-Testing : Unit Testing with Mock Objects"</link> for full details
           on MO. As such it is a challenger to Cactus but we'll see
           in the rest of this article that it is in fact complementary rather than
  @@ -416,7 +416,7 @@
         <p>
           <ul>
             <li>
  -            <link href="http://www.sidewize.com/company/mockobjects.pdf";>
  +            <link href="http://mockobjects.sourceforge.net/endotesting.html";>
               "Endo-Testing : Unit Testing with Mock Objects"</link> (PDF). 
               Describes the vision behind MO.
             </li>
  @@ -425,7 +425,7 @@
               Mock Object discussions on Wiki</link>.
             </li>
             <li>
  -            <link href="http://sourceforge.net/projects/mockobjects";>Mock Object
  +            <link href="http://mockobjects.sourceforge.net";>Mock Object
               project</link> on SourceForge. MO framework and some mock
               implementations.
             </li>
  
  
  

Reply via email to