[jboss-osgi-commits] JBoss-OSGI SVN: r89761 - projects/jboss-osgi/trunk/docbook/en/modules.

[jboss-osgi-commits at lists.jboss.org]

Author: thomas.diesler at jboss.com
Date: 2009-06-03 15:50:06 -0400 (Wed, 03 Jun 2009)
New Revision: 89761

Modified:
   projects/jboss-osgi/trunk/docbook/en/modules/ch060-husky-testing.xml
Log:
link to husky API

Modified: projects/jboss-osgi/trunk/docbook/en/modules/ch060-husky-testing.xml
===================================================================
--- projects/jboss-osgi/trunk/docbook/en/modules/ch060-husky-testing.xml	2009-06-03 19:36:43 UTC (rev 89760)
+++ projects/jboss-osgi/trunk/docbook/en/modules/ch060-husky-testing.xml	2009-06-03 19:50:06 UTC (rev 89761)
@@ -64,27 +64,39 @@
     <para>Here is how it works </para>
     
     <orderedlist>
-      <listitem>A Bridge intercepts a test and determines the FQN of the test case and the test method from the call stack.
-      It then delegates the execution to the same (or another) test in and isolated test environment. 
-      An isolated test environment is one that does not have the same class loading space as the test itself.</listitem>
+      <listitem>A <ulink url="http://jbmuc.dyndns.org:8280/hudson/job/jbossosgi-jdk16/ws/jboss-osgi/husky/harness/target/apidocs/org/jboss/osgi/husky/Bridge.html">Bridge</ulink> 
+      intercepts a test and determines the FQN of the test case and the test method from the call stack. It then delegates the execution to the same 
+      (or another) test in and isolated test environment. An isolated test environment is one that does not have the same class loading space as 
+      the test itself.</listitem>
       
-      <listitem>A Bridge is associated with an Invoker. Invokers may be arbitarily complex. Local 'in proccess' 
-      invokers are possible just as well as remote invokers. </listitem>
+      <listitem>A Bridge is associated with an <ulink url="http://jbmuc.dyndns.org:8280/hudson/job/jbossosgi-jdk16/ws/jboss-osgi/husky/harness/target/apidocs/org/jboss/osgi/husky/Invoker.html">
+      Invoker</ulink>. Invokers may be arbitarily complex. Local 'in proccess' invokers are possible just as well as remote invokers. </listitem>
       
-      <listitem>The Invoker sends the Request to a Connector in the isolated test environment.</listitem>
+      <listitem>The Invoker sends the <ulink url="http://jbmuc.dyndns.org:8280/hudson/job/jbossosgi-jdk16/ws/jboss-osgi/husky/harness/target/apidocs/org/jboss/osgi/husky/Request.html">
+      Request</ulink> to a <ulink url="http://jbmuc.dyndns.org:8280/hudson/job/jbossosgi-jdk16/ws/jboss-osgi/husky/harness/target/apidocs/org/jboss/osgi/husky/runtime/Connector.html">
+      Connector</ulink> in the isolated test environment.</listitem>
       
-      <listitem>A Connector has associated PackageListeners that are responsible for processing test cases for their
-      respective test packages.</listitem>
+      <listitem>A Connector has associated <ulink url="http://jbmuc.dyndns.org:8280/hudson/job/jbossosgi-jdk16/ws/jboss-osgi/husky/harness/target/apidocs/org/jboss/osgi/husky/runtime/PackageListener.html">
+      PackageListeners</ulink> that are responsible for processing test cases for their respective test packages.</listitem>
       
-      <listitem>A PackageListeners delegates the Request to a test Runner, typicaly this would be a JUnit runner.</listitem>
+      <listitem>A PackageListeners delegates the Request to a test <ulink url="http://jbmuc.dyndns.org:8280/hudson/job/jbossosgi-jdk16/ws/jboss-osgi/husky/harness/target/apidocs/org/jboss/osgi/husky/runtime/Runner.html">
+      Runner</ulink>, typicaly this would be a <ulink url="http://jbmuc.dyndns.org:8280/hudson/job/jbossosgi-jdk16/ws/jboss-osgi/husky/harness/target/apidocs/org/jboss/osgi/husky/runtime/junit/JUnitRunner.html">
+      JUnitRunner</ulink>.</listitem>
       
-      <listitem>The Runner injects the Context and returns a Result, which the Connector returns to the Invoker.</listitem>
+      <listitem>The Runner injects the <ulink url="http://jbmuc.dyndns.org:8280/hudson/job/jbossosgi-jdk16/ws/jboss-osgi/husky/harness/target/apidocs/org/jboss/osgi/husky/Context.html">
+      Context</ulink> into the test case and returns a <ulink url="http://jbmuc.dyndns.org:8280/hudson/job/jbossosgi-jdk16/ws/jboss-osgi/husky/harness/target/apidocs/org/jboss/osgi/husky/Response.html">
+      Response</ulink>, which the Connector returns to the Invoker.</listitem>
       
-      <listitem>The Bridge finally translates potential Failures that may be contained in the Result, to test failures on the client side.</listitem>
+      <listitem>The Bridge finally translates potential <ulink url="http://jbmuc.dyndns.org:8280/hudson/job/jbossosgi-jdk16/ws/jboss-osgi/husky/harness/target/apidocs/org/jboss/osgi/husky/Failure.html">
+      Failures</ulink> that may be contained in the Result, to test failures on the client side.</listitem>
     </orderedlist>
     
-    <para>The JBoss OSGi <emphasis role="bold">jboss-osgi-husky.jar</emphasis> bundle registers the Connectors. The JMXConnector is always 
-    registered. The SocketConnector is registered when the appropriate configuration options are set. It then registers the Extender, 
+    <para>The JBoss OSGi <emphasis role="bold">jboss-osgi-husky.jar</emphasis> bundle registers the Connectors. 
+    The <ulink url="http://jbmuc.dyndns.org:8280/hudson/job/jbossosgi-jdk16/ws/jboss-osgi/husky/harness/target/apidocs/org/jboss/osgi/husky/runtime/osgi/JMXConnector.html">
+    JMXConnector</ulink> is always registered. 
+    The <ulink url="http://jbmuc.dyndns.org:8280/hudson/job/jbossosgi-jdk16/ws/jboss-osgi/husky/harness/target/apidocs/org/jboss/osgi/husky/runtime/osgi/SocketConnector.html">
+    SocketConnector</ulink> is registered when the appropriate configuration options are set. It then registers the 
+    <ulink url="http://jbmuc.dyndns.org:8280/hudson/job/jbossosgi-jdk16/ws/jboss-osgi/husky/harness/target/apidocs/org/jboss/osgi/husky/runtime/osgi/HuskyExtender.html">HuskyExtender</ulink>, 
     which is a <ulink url="http://www.osgi.org/javadoc/r4v41/org/osgi/framework/BundleListener.html">BundleListener</ulink> that inspects every
     incomming bundle for the <emphasis role="bold">Test-Package</emphasis> manifest header. The Extender creates a PackageListener
     for every package in the 'Test-Package' manifest header and registers them with the available Connectors.</para>