That defeats the purpose of that Tomcat integration. The idea is that
the Cactus jars would be part of the common libraries of a Tomcat
installation so that each web application does not have to include the
cactus jars and setup in its own war ... The idea is to bring testing as
a "service" provided by the container, not the other way around.

-Vincent

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: 25 May 2002 23:39
> To: Tomcat Users List
> Cc: 'Tomcat Developers List'
> Subject: RE: [Proposal] Tomcat and Cactus (Repost)
> 
> I would prefer to see a self-contained WAR file ( or a set of
> self-contained wars ).
> 
> 
> 
> Costin
> 
> On Sat, 25 May 2002, Vincent Massol wrote:
> 
> > Thanks to speak your mind Costin. At least you answered. I would
have
> > liked more feedback from other committers.
> >
> > For the time being I'll prepare a "cactification" script for Tomcat
that
> > will be delivered with Cactus. BTW, is there any problem if we
create in
> > cactusland a specially packaged Tomcat version that is cactus-aware
?
> > I'm not sure yet we want to follow that route but if we wanted to do
> > this and put it in the cactus release directory, would you see any
> > problem ?
> >
> > I'll repost in 6 months ... :-)
> >
> > Thanks
> > -Vincent
> >
> > Sidenote: I believe Cactus could very effectively be used as a
> > regression testing tool for the Tomcat project. It has already
> > discovered problems in the past. I haven't looked at the Watchdog
> > project but it could be either a replacement or a complement to it.
You
> > should try it at some point. I would love to hear comments of what
you
> > don't like/do like. Quick start up guide for Tomcat is available
here :
> > http://jakarta.apache.org/cactus/1.4/howto_tomcat.html (needs only
10
> > minutes).
> >
> >
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > > Sent: 24 May 2002 19:41
> > > To: Tomcat Users List
> > > Cc: List Tomcat-Dev
> > > Subject: Re: [Proposal] Tomcat and Cactus (Repost)
> > >
> > > On Fri, 24 May 2002, Vincent Massol wrote:
> > >
> > > > I'm reposting in the secret hope that I got no response to this
> > email I
> > > > sent last week because no one saw it in the flood of Tomcat
emails !
> > If
> > > > I get no answer this time, I will understand that no one finds
this
> > of
> > > > interest and will try again in 6 months - 1 year :-)
> > >
> > > I think it would be a good idea :-), there is already far too much
> > going
> > > on, with all the new features and changes ( jmx, 4.1, jk2,
jasper2,
> > > coyote, etc ).
> > >
> > > Costin
> > >
> > >
> > > >
> > > > Thanks
> > > > -Vincent
> > > >
> > > > ----
> > > >
> > > > Hi Tomcat developers,
> > > >
> > > > This is a proposal to bring Jakarta Tomcat and Jakarta Cactus
> > > > (http://jakarta.apache.org/cactus) closer. I hope you'll like
it.
> > > >
> > > > (0) Rationale
> > > >
> > > > Jakarta Cactus is a unit testing framework for testing Servlet,
> > Taglibs
> > > > and Filters. Jakarta Tomcat is a Servlet engine (Servlet,
Taglibs,
> > > > Filters). They are both part of the Jakarta community. At the
> > moment,
> > > > there are no existing Servlet container that have an easy way to
> > unit
> > > > test Servlets. The idea is to bring this ease of use to Tomcat
by
> > making
> > > > it easy to use Cactus within Tomcat (in other words, add a unit
> > testing
> > > > service to Tomcat).
> > > >
> > > > (1) Scope of the proposal
> > > >
> > > > a) To bundle Cactus within Tomcat so that it provides a unique
ease
> > of
> > > > use for Tomcat users who wishes to test their servlet code
> > > > b) To make Cactus the official Tomcat test framework for end
users
> > > >
> > > > (1) From the point of view of Tomcat users
> > > >
> > > > By providing the bundling defined in point (2) below, Tomcat end
> > users
> > > > would only have to do the following to test their code (see
> > > > http://jakarta.apache.org/cactus/1.4/howto_tomcat.html, steps 4
to
> > 6) :
> > > >
> > > > a) Create Cactus test classes in their WEB-INF/classes directory
> > > > b) Open a browser and type the URL of the Cactus test runner,
> > passing
> > > > the name of the test class (see the link above for details)
> > > >
> > > > (2) Cactus bundling in Tomcat
> > > >
> > > > "Bundling" Cactus in Tomcat means (see steps 1 to 3 on the above
> > link) :
> > > >
> > > > a) Adding the following jars to common/lib : cactus.jar,
junit.jar,
> > > > httpclient.jar, aspectjrt.jar (total of 423 KB)
> > > > b) Adding the Cactus servlet test runner and redirector servlet
and
> > > > mappings in conf/web.xml
> > > >
> > > > (3) Versions
> > > >
> > > > The target Tomcat version for this proposal is 4.0 and greater.
The
> > > > Cactus one is 1.4 and greater (note that Cactus 1.4 is not
released
> > yet
> > > > and is still in CVS - It can be downloaded from the nightly
build).
> > > >
> > > > Comments, ideas ?
> > > >
> > > > Thank you
> > > > -Vincent (from the Cactus team)
> > > >
> > > >
> > > >
> > > > --
> > > > To unsubscribe, e-mail:   <mailto:tomcat-user-
> > > [EMAIL PROTECTED]>
> > > > For additional commands, e-mail: <mailto:tomcat-user-
> > > [EMAIL PROTECTED]>
> > > >
> > > >
> > >
> > >
> > > --
> > > To unsubscribe, e-mail:   <mailto:tomcat-dev-
> > > [EMAIL PROTECTED]>
> > > For additional commands, e-mail: <mailto:tomcat-dev-
> > > [EMAIL PROTECTED]>
> >
> >
> >
> > --
> > To unsubscribe, e-mail:   <mailto:tomcat-user-
> [EMAIL PROTECTED]>
> > For additional commands, e-mail: <mailto:tomcat-user-
> [EMAIL PROTECTED]>
> >
> >
> 
> 
> --
> To unsubscribe, e-mail:   <mailto:tomcat-dev-
> [EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:tomcat-dev-
> [EMAIL PROTECTED]>



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to