Author: jkuhnert
Date: Sun Apr 29 13:51:47 2007
New Revision: 533559

URL: http://svn.apache.org/viewvc?view=rev&rev=533559
Log:
Attempted to fix javadocs links.

Modified:
    tapestry/tapestry-test/trunk/src/site/apt/components.apt
    tapestry/tapestry-test/trunk/src/site/apt/easymock.apt
    tapestry/tapestry-test/trunk/src/site/apt/gettingstarted.apt

Modified: tapestry/tapestry-test/trunk/src/site/apt/components.apt
URL: 
http://svn.apache.org/viewvc/tapestry/tapestry-test/trunk/src/site/apt/components.apt?view=diff&rev=533559&r1=533558&r2=533559
==============================================================================
--- tapestry/tapestry-test/trunk/src/site/apt/components.apt (original)
+++ tapestry/tapestry-test/trunk/src/site/apt/components.apt Sun Apr 29 
13:51:47 2007
@@ -53,10 +53,10 @@
 
   The following sections will expand further on each part of the test used.
 
-* 
{{{/apidocs/org/apache/tapestry/BaseComponentTestCase.html}BaseComponentTestCase}}
+* 
{{{./apidocs/org/apache/tapestry/BaseComponentTestCase.html}BaseComponentTestCase}}
 
-  In almost all of the core Taptestry test cases 
{{{/apidocs/org/apache/tapestry/BaseComponentTestCase.html}BaseComponentTestCase}}
 is the actual test class extended. It provides
-  a number of additional conveniences not found in the basic 
{{{/apidocs/org/apache/tapestry/TestBase.html}TestBase}} class - such as being 
able to create a buffered
+  In almost all of the core Taptestry test cases 
{{{./apidocs/org/apache/tapestry/BaseComponentTestCase.html}BaseComponentTestCase}}
 is the actual test class extended. It provides
+  a number of additional conveniences not found in the basic 
{{{./apidocs/org/apache/tapestry/TestBase.html}TestBase}} class - such as being 
able to create a buffered
   
{{{http://tapestry.apache.org/tapestry4.1/apidocs/org/apache/tapestry/IMarkupWriter.html}IMarkupWriter}}
 instance that allows you to check the string produced from a component
   render instead of having to do mock calls for all of the method invocations 
on a mock 
{{{http://tapestry.apache.org/tapestry4.1/apidocs/org/apache/tapestry/IMarkupWriter.html}IMarkupWriter}}
   object.

Modified: tapestry/tapestry-test/trunk/src/site/apt/easymock.apt
URL: 
http://svn.apache.org/viewvc/tapestry/tapestry-test/trunk/src/site/apt/easymock.apt?view=diff&rev=533559&r1=533558&r2=533559
==============================================================================
--- tapestry/tapestry-test/trunk/src/site/apt/easymock.apt (original)
+++ tapestry/tapestry-test/trunk/src/site/apt/easymock.apt Sun Apr 29 13:51:47 
2007
@@ -12,7 +12,7 @@
   code to make testing feasible. The tapestry-test library provides a few 
conveniences to make managing mock objects a
   little easier in your own unit tests.
 
-  For example, if you were using {{{http://easymock.org}EasyMock}} without 
extending {{{/apidocs/org/apache/tapestry/TestBase.html}TestBase}} you
+  For example, if you were using {{{http://easymock.org}EasyMock}} without 
extending {{{./apidocs/org/apache/tapestry/TestBase.html}TestBase}} you
   might have to write a test looking something like this:
 
 
+-------------------------------------------------------------------------------------------------------------------------
@@ -53,10 +53,10 @@
 
+-------------------------------------------------------------------------------------------------------------------------
 
   In particular you want to note that we had to pass in each mock we created 
in the <<<replay(mw, cycle)>>> method of {{{http://easymock.org}EasyMock}}. This
-  can get a little unweildy / painfaul at times so 
{{{/apidocs/org/apache/tapestry/TestBase.html}TestBase}} has made this part 
easier by keeping track of your
+  can get a little unweildy / painfaul at times so 
{{{./apidocs/org/apache/tapestry/TestBase.html}TestBase}} has made this part 
easier by keeping track of your
   mock objects for you.
 
-  The same class above re-written to use the 
{{{/apidocs/org/apache/tapestry/TestBase.html}TestBase}} features would look 
more like:
+  The same class above re-written to use the 
{{{./apidocs/org/apache/tapestry/TestBase.html}TestBase}} features would look 
more like:
 
 
+-------------------------------------------------------------------------------------------------------------------------
 import org.apache.tapestry.IMarkupWriter;

Modified: tapestry/tapestry-test/trunk/src/site/apt/gettingstarted.apt
URL: 
http://svn.apache.org/viewvc/tapestry/tapestry-test/trunk/src/site/apt/gettingstarted.apt?view=diff&rev=533559&r1=533558&r2=533559
==============================================================================
--- tapestry/tapestry-test/trunk/src/site/apt/gettingstarted.apt (original)
+++ tapestry/tapestry-test/trunk/src/site/apt/gettingstarted.apt Sun Apr 29 
13:51:47 2007
@@ -8,7 +8,7 @@
 
 Simple Test
 
-  There's no better way to get going than by looking at real code. This 
example uses the {{{/apidocs/org/apache/tapestry/TestBase.html}TestBase}} class 
as
+  There's no better way to get going than by looking at real code. This 
example uses the {{{./apidocs/org/apache/tapestry/TestBase.html}TestBase}} 
class as
   the main class to extend from.
 
   This isn't a requirement with {{{http://testng.org}TestNG}} - but it does 
make some things a lot easier. <(such as managing
@@ -41,7 +41,7 @@
 * Assertions
 
   The previous example used a {{{http://testng.org}}} <<<assertEquals(actual, 
expected)>>> utiltity method to do equality checking. It is provided in the
-  {{{/apidocs/org/apache/tapestry/TestBase.html}TestBase}} class as a 
convenience, but you could do the same thing in your own tests with a static 
import of
+  {{{./apidocs/org/apache/tapestry/TestBase.html}TestBase}} class as a 
convenience, but you could do the same thing in your own tests with a static 
import of
   the {{{http://testng.org/javadocs/org/testng/Assert.html}Assert}} class like 
this:
 
 
+-------------------------------------------------------------------------------------------------------------------------


Reply via email to