----- Original Message -----
From: "Denis Krizanovic" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, July 23, 2001 12:09 AM
Subject: RE: [Cactus v2 - VOTE] Extension to web.xml mechanism
>
> I see, yet -another- management misunderstanding. : )
>
> To repeat what I think I'm understanding from your statement, is that it's
> common cactus practice to war up all your tests and deploy them to the
same
> application as your application under test?
>
Not exactly ... An application is actually called a webapp and is
conveniently deployed as a war file. So one war file per application.
However, what I was suggesting is that your build system (using Ant maybe)
should generate either a test war (only used for testing purposes) and a
production war to be deployed on your production platform.
> I didn't realise that it was possible to have multiple war's in the same
> application.
>
> wow - all of a sudden I realise how powerful something like this might be.
>
Well, the main advantage of Cactus is that it really test your code where it
is supposed to run (i.e. in your container) as opposed to performing
simulation tests in a Mock-Object style. On the other hand MO style tests
are complementary (see
http://jakarta.apache.org/commons/cactus/mockobjects.html). The version 2.0
of Cactus will let you write tests in either style.
> thanks.
>
> ___
> dk-
-Vincent
