You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@avalon.apache.org by ha...@apache.org on 2002/04/26 07:41:16 UTC
cvs commit: jakarta-avalon-excalibur/altrmi/src/xdocs tests.xml book.xml transports.xml
hammant 02/04/25 22:41:16
Modified: altrmi/src/xdocs book.xml transports.xml
Added: altrmi/src/xdocs tests.xml
Log:
new docs for running of tests
Revision Changes Path
1.6 +1 -0 jakarta-avalon-excalibur/altrmi/src/xdocs/book.xml
Index: book.xml
===================================================================
RCS file: /home/cvs/jakarta-avalon-excalibur/altrmi/src/xdocs/book.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- book.xml 8 Apr 2002 20:24:57 -0000 1.5
+++ book.xml 26 Apr 2002 05:41:16 -0000 1.6
@@ -24,6 +24,7 @@
<menu-item label="Client usage" href="client-usage.html"/>
<menu-item label="Pingers" href="pingers.html"/>
<menu-item label="Connection Listeners" href="connection-listeners.html"/>
+ <menu-item label="Tests" href="tests.html"/>
</menu>
</book>
1.3 +6 -6 jakarta-avalon-excalibur/altrmi/src/xdocs/transports.xml
Index: transports.xml
===================================================================
RCS file: /home/cvs/jakarta-avalon-excalibur/altrmi/src/xdocs/transports.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- transports.xml 3 Apr 2002 21:46:33 -0000 1.2
+++ transports.xml 26 Apr 2002 05:41:16 -0000 1.3
@@ -40,6 +40,11 @@
</p>
</s2>
</s1>
+ <s1 title="JNDI">
+ <p>
+ Blah
+ </p>
+ </s1>
<s1 title="Future Transports">
<p>
<ul>
@@ -55,11 +60,6 @@
</ul>
</p>
</s1>
- <s1 title="JNDI">
- <p>
- Blah
- </p>
- </s1>
<s1 title="Speed">
<p>
Counting the number of 'void testSpeed()' invocations in 10 seconds,
@@ -125,7 +125,7 @@
<footer>
<legal>
Copyright (c) @year@ The Jakarta Apache Project All rights reserved.
- $Revision: 1.2 $ $Date: 2002/04/03 21:46:33 $
+ $Revision: 1.3 $ $Date: 2002/04/26 05:41:16 $
</legal>
</footer>
</document>
1.1 jakarta-avalon-excalibur/altrmi/src/xdocs/tests.xml
Index: tests.xml
===================================================================
<?xml version="1.0"?>
<!DOCTYPE document SYSTEM "dtd/document-v10.dtd">
<document>
<header>
<title>Excalibur AltRMI / Tests</title>
<authors>
<person name="Paul Hammant" email="Paul_Hammant@yahoo.com"/>
</authors>
</header>
<body>
<s1 title="Introduction">
<p>
There are a number of examples that come with AltRMI. They are only present in the source
download or the CVS depot, so we will assume that you have one or the other of these.
</p>
</s1>
<s1 title="Tests using AltRMI">
<p>
The tests all run under Ant control. Some tests are client and server, others are in a
single VM. You may need two command shells for the client/server tests.
</p>
<p>
The majority of the tests transfer a primary interface, TestInterface, between server and
client. It has a number of methods that test the passing of primatives and objects as
parameters and return types. Apart from this testing of features, the speed of the transport
type is tested. This is simply the counting of as many repetetive invocations of the same
method in ten seconds as possible. It is used for an statistically incorrect comparison of
transports.
</p>
<s2 title="ObjectStream Over Plain Sockets">
<p>
The ObjectStream over plain sockets tests are launched from a build file called socketa.xml.
You need two command shells. In the first
launch <strong>ant -buildfile socketa.xml server</strong>, and in the second <strong>ant
-buildfile socketa.xml client</strong>
</p>
</s2>
<s2 title="CustomStream Over Plain Sockets">
<p>
The CustomStream over plain sockets tests are launched from a build file called socketb.xml.
You need two command shells. In the first
launch <strong>ant -buildfile socketb.xml server</strong>, and in the second <strong>ant
-buildfile socketb.xml client</strong>
</p>
</s2>
<s2 title="CustomStream Over Plain Sockets, using callback handlers">
<p>
The CustomStream over plain sockets tests are launched from a build file called socketc.xml.
You need two command shells. In the first
launch <strong>ant -buildfile socketc.xml server</strong>, and in the second <strong>ant
-buildfile socketc.xml client</strong>. The callback capable layer is not used to its
fullest capacity, in that no callbacks ae setup. This is most useful for a comparative
speed test.
</p>
</s2>
<s2 title="RMI">
<p>
The RMI tests are launched from a build file called rmi.xml.
You need two command shells. In the first
launch <strong>ant -buildfile rmi.xml server</strong>, and in the second <strong>ant
-buildfile rmi.xml client</strong>.
</p>
</s2>
<s2 title="Piped">
<p>
The Piped tests are launched from a build file called piped.xml.
You need a single shell. To test the piped transport with generated
proxies already in the client's classloader,
launch <strong>ant -buildfile piped.xml clientclasses</strong>. To test the piped
transport with generated proxies retrieved from the server by the client,
launch <strong>ant -buildfile piped.xml serverclasses</strong>. To test the piped
transport with generated proxies generated on demand by the server for the client,
launch <strong>ant -buildfile piped.xml dynamicclasses</strong>.
</p>
</s2>
<s2 title="Direct">
<p>
The Direct tests are launched from a build file called direct.xml.
You need a single shell. To test the direct connection of client and server
launch <strong>ant -buildfile direct.xml direct</strong>. To test the direct
connection of client and server with marshalling of communications
launch <strong>ant -buildfile direct.xml direct-marshalled</strong>.
</p>
</s2>
</s1>
<s1 title="Tests not using AltRMI">
<p>
These tests are used for a speed comparison of native Java techniques. This type of testing
is possible because AltRMI uses normal Java interfaces. All are run from the proxies.xml Ant
script in a single command shell.
</p>
<s2 title="Dynamic Proxy">
<p>
This test uses dynamically generated proxies, which are normally used when you want to
do implemetation hiding. To test, launch
<strong>ant -buildfile proxies.xml dynamic-proxy</strong>.
</p>
</s2>
<s2 title="Coded Proxy">
<p>
This test uses human crafted proxy. To test, launch
<strong>ant -buildfile proxies.xml coded-proxy</strong>.
</p>
</s2>
<s2 title="Non Proxy">
<p>
This test directly wires the server to the clint via TestInterface. To test, launch
<strong>ant -buildfile proxies.xml un-proxy</strong>. This, of course, is the fastest
possible connection of client and server.
</p>
</s2>
</s1>
</body>
<footer>
<legal>
Copyright (c) @year@ The Jakarta Apache Project All rights reserved.
$Revision: 1.1 $ $Date: 2002/04/26 05:41:16 $
</legal>
</footer>
</document>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>