These tests are for the one way invocations.  The OnewayInvokerServer is the class that runs
the remoting server.  It uses the TestServerInvocationHandler as its handler, which will
keep up with the previous calls that have been made to it.

The OnewayInvokerClientTest has two tests; one to check client side one way calls
(meaning that invocation is handed off to a worker pool in the client and then processed
from there) and one to check server side one way calls (meaning that the caller's thread
will actually be the one making the network call so at least knows made it to the server
side, at which time the invocation will be handed off to a worker pool on the server side).

Since neither of the one way calls actually know for sure that the server processed the
invocation, the OnewayInvokerClientTest will follow up its one way call to get the parameter
it previously passed in the one way call.  Will then assert that the response value returned
from the handler is the one it passed in the oneway call.

The OnewayInvokerTestCase is a simple driver class, which uses the distributed test framework
to start both the OnewayInvokerServer and the OnewayInvokerClientTest, let the tests run, then
collect the results from teh OnewayInvokerClientTest.  The reason this is needed is that JUnit
does not have a way to start and control two java tests instance, so have to use this
driver class for automated test runs.