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 cm...@apache.org on 2003/01/01 21:00:42 UTC

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

cmlenz      2003/01/01 12:00:42

  Modified:    documentation/docs/xdocs howto_runner.xml
  Log:
  - Cosmetic changes
  
  Revision  Changes    Path
  1.6       +53 -40    jakarta-cactus/documentation/docs/xdocs/howto_runner.xml
  
  Index: howto_runner.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-cactus/documentation/docs/xdocs/howto_runner.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- howto_runner.xml	26 Dec 2002 15:32:15 -0000	1.5
  +++ howto_runner.xml	1 Jan 2003 20:00:42 -0000	1.6
  @@ -110,7 +110,9 @@
   [...]
   <servlet>
       <servlet-name>ServletTestRunner</servlet-name>
  -    <servlet-class>org.apache.cactus.server.runner.ServletTestRunner</servlet-class>
  +    <servlet-class>
  +        org.apache.cactus.server.runner.ServletTestRunner
  +    </servlet-class>
   </servlet>
   [...]
   <servlet-mapping>
  @@ -177,31 +179,35 @@
   
         </s2>
   
  -    </s1>
  +      <s2 title="Enabling Server-Side XSLT Transformations">
   
  -    <s1 title="Enabling Server-Side XSLT Transformations">
  -      <p>
  -        In the previous section, the XSLT transformation was performed on the 
  -        client. This requires a browser capable of doing XSLT transformations 
  -        in a standards-compliant manner, and requires adding the location of 
  -        the stylesheet as a request parameter.
  -      </p>
  -      <p>
  -        Since Cactus 1.5, the ServletTestRunner can also perform the 
  -        transformation on the server-side. To enable that feature, make sure
  -        that a JAXP compliant XSLT processor (such as 
  -        <link href="http://xml.apache.org/xalan-j/">Xalan</link>) is available
  -        to the web-application.
  -      </p>
  -      <p>
  -        In addition, the location of the XSLT stylesheet needs to specified as
  -        initialization parameter of the ServletTestRunner. For example:
  -      </p>
  -	<source><![CDATA[
  +        <p>
  +          In the previous section, the XSLT transformation was performed on the 
  +          client. This requires a browser capable of doing XSLT transformations 
  +          in a standards-compliant manner, and requires adding the location of 
  +          the stylesheet as a request parameter.
  +        </p>
  +
  +        <p>
  +          Since Cactus 1.5, the ServletTestRunner can also perform the 
  +          transformation on the server-side. To enable that feature, make sure
  +          that a JAXP compliant XSLT processor (such as 
  +          <link href="http://xml.apache.org/xalan-j/">Xalan</link>) is available
  +          to the web-application.
  +        </p>
  +
  +        <p>
  +          In addition, the location of the XSLT stylesheet needs to specified as
  +          initialization parameter of the ServletTestRunner. For example:
  +        </p>
  +
  +    <source><![CDATA[
   [...]
   <servlet>
       <servlet-name>ServletTestRunner</servlet-name>
  -    <servlet-class>org.apache.cactus.server.runner.ServletTestRunner</servlet-class>
  +    <servlet-class>
  +        org.apache.cactus.server.runner.ServletTestRunner
  +    </servlet-class>
       <init-param>
           <param-name>xsl-stylesheet</param-name>
           <param-value>styles/cactus-report.xsl</param-value>
  @@ -209,26 +215,33 @@
   </servlet>
   [...]
   ]]></source>
  -      <p>
  -        The specified path is relative to the root of the web-application. Of 
  -        course, the stylesheet needs to exist at that location. In contrast to
  -        client-side transformations, the stylesheet may be placed somewhere
  -        inside the <code>WEB-INF</code> directory, because clients do not need
  -        to access it directly.
  -      </p>
  -      <p>
  -        If all of the above is correctly set up, you can enable the actual
  -        transformation by including a <code>transform</code> parameter with
  -        the request (the value of the parameter does not matter). For example
  -      </p>
  -	<source><![CDATA[
  +
  +        <p>
  +          The specified path is relative to the root of the web-application. Of 
  +          course, the stylesheet needs to exist at that location. In contrast to
  +          client-side transformations, the stylesheet may be placed somewhere
  +          inside the <code>WEB-INF</code> directory, because clients do not need
  +          to access it directly.
  +        </p>
  +
  +        <p>
  +          If all of the above is correctly set up, you can enable the actual
  +          transformation by including a <code>transform</code> parameter with
  +          the request (the value of the parameter does not matter). For example
  +        </p>
  +
  +    <source><![CDATA[
   http://server:port/mywebapp/ServletTestRunner?suite=mytestcase&transform=yes
   ]]></source>
  -      <note>
  -        The stylesheet specified as initialization parameter is loaded when the
  -        ServletTestRunner gets initialized. Changes to the stylesheet will not 
  -        get picked up until the web-application is reloaded.
  -      </note>
  +
  +        <note>
  +          The stylesheet specified as initialization parameter is loaded when 
  +          the ServletTestRunner gets initialized. Changes to the stylesheet will
  +          not get picked up until the web-application is reloaded.
  +        </note>
  +
  +      </s2>
  +
       </s1>
   
     </body>
  
  
  

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>