RE: cactus in testing web services?

[Darren Hartford <dh...@ghsinc.com>]

Hi shivan,
I've started the road of using Junit for Webservice testing as Webservices are usually accessed outside of their container. Cactus is absolutely great for in-container testing, while Junit is ideal for outside-container testing.  As an example for a service-oriented architecture:

EJB/JBoss backend system with exposed WebService interfaces and two different Swing clients, a Windows .NET client, and a seperate webserver:

Cactus test EJB - test performance internally to VM, following business rules, etc.

Junit test WebService - kind of a 'real-world' functional test of what an external system will see and perform with the webservices.

Then, build the clients to the webservices. If the client is a Servlet that talks to the Webservices (the client runs in a container of some sort), then you may want to do a cactus-test on the client.

Hope this helps!  
-D

p.s. to help toot Vincent's horn, check out his presentation on strategies for testing:
http://www.pivolis.com/pdf/Unit_Testing_J2EE_V1.1.pdf
Specifically, slide 10 and 11 may help.


-----Original Message-----
From: Vincent Massol [mailto:vmassol@pivolis.com]
Sent: Monday, December 29, 2003 5:59 AM
To: 'Cactus Users List'
Subject: RE: cactus in testing web services?


Hi Shivan,

Cactus can be used to unit test (i.e. test at the level of the code
methods) any code that uses the Servlet API, JSP/Taglib API, Filter API
or EJB API. Thus the answer to your question is probably "yes"! :-)

Now, tell us what do you wish to test and we'll be able to tell you if
Cactus is the right tool or not.

Thanks
-Vincent

> -----Original Message-----
> From: shivan [mailto:bhutkar@comcast.net]
> Sent: 29 December 2003 04:37
> To: Cactus Users List
> Subject: cactus in testing web services?
> 
> Hi,
> i am new to cactus. Is anyone using it in web services testing?
>