jakarta-cactus-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fred Loney" <lo...@spiritedsw.com>
Subject Re: Single test class for both local and remote
Date Wed, 05 Feb 2003 05:42:36 GMT
There might be some confusion about terminology. The EJB local/remote
distinction is orthogonal to the cactus client/server distinction. A
test case is always an EJB client. On the other hand, the test code will
necessarily differ depending on whether the local or remote EJB is
called. Thus the test code must differ but it is always an EJB client.
The question seems to imply that the test code is the same but it need
not always be an EJB client.

Fred Loney

----- Original Message -----
From: "Tim McNerney" <mcnerney@navis.com>
To: <cactus-user@jakarta.apache.org>
Sent: Monday, February 03, 2003 4:00 PM
Subject: Single test class for both local and remote

> I want to build a test which works both locally (on the client side)
> remotely (on the server side). This is basically testing the local and
> remote interfaces of an EJB. Since much of the code would be the same
> for both, I'd like to keep it in one class. Let's say I'm using
> (extending) a ServletTestCase for the server side test. Is there some
> way for me to tell my test class not to connect to the test on the
> server side but simply run the test locally?
> And I'm making any sense?
> --Tim
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-user-help@jakarta.apache.org

View raw message