Laurent,
I'm using Netbeans and Ant almost exactly as Vincent describes. It works
wonderfully. I'd volunteer for the task of writing a manual for it, but it
is not necessary. Basically I have an ANT script that build's my test code,
deploys it to my local development server, and restarts the server. Since
Netbeans integrates with Ant, all I have to do is double click on the build
script. At that point, running the Cactus test is as easy as executing the
Test's main method.
In other words, to integrate with NetBeans, all you have to do is ensure
that your server is configured properly, has your test code on it, and is
started :)--No Netbeans work involved (though Ant *is*).
Cheers,
Nick
-----Original Message-----
From: Vincent Massol [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 30, 2001 5:49 AM
To: [EMAIL PROTECTED]
Subject: Re: Cactus and Netbeans
Hi Laurent,
I was going to suggest you use Ant for your build process when I read the
last sentencen saying that you're not using it yet ! :-)
On the projects I have been involved with, we use Ant as our "official"
build process. By "official" I mean that the application being developed
must be able to be built using Ant from scratch. It must also pass all unit
and functional tests running Ant. Ant is also used to deploy it. Then, in
order to increase productivity and let person use their favorite tools, we
then either leave the choice of the IDE on developers or choose one at the
beginning of the project. The idea is that you will be able to quickly run
your unit tests within your IDE and then from time to time you run the Ant
script to verify everything runs fine. Actually what we often do here is
even better : we install a dedicated machine that is in charge of doing
automated builds. We have written some simple Ant scripts which runs
automatically every few hours, get the code from the repository, build the
project, build the doc, run the unit tests, run the functional tests and
package the distribution.
Running Cactus unit tests in any IDE is not too hard. You need to be able to
start you application server from that IDE which is usually very simple as
they are all written in java ... For weblogic for example, look at the
sample Ant scripts provided in the distribution
(<root>/sample/build/build-test-weblogic-51.xml). Before running your tests,
you'll need to start your server this way (either in normal mode or debug
mode if you wish to debug the test case). Then you simply need to run your
test case (which has a main method).
There is no explicit NetBeans integration tutorial on the cactus web site
(I'm looking for someone who could provide one ... hint ... !) but you can
have a look at the JBuilder4 one which will look very similar to the
NetBeans one.
Tell me if you run in any problem and I'll help you.
Thanks
-Vincent
----- Original Message -----
From: "Laurent Duperval" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, July 30, 2001 1:34 PM
Subject: Re: Cactus and Netbeans
> On 30 Jul, Denis Krizanovic wrote:
> >
> >
> > Yes. What kinds of ways are you using it?
> >
>
> Well, we haven't yet. We're in the process of building servlets and want
to
> set up automatic testing for it. Some of us use Netbeans, some use
JBuilder,
> some use VAJ. Our servlets run in Weblogic 5.1.
>
> A couple of guys tried to get Cactus up and running on their machine
> (Windows/Forte 3.0 CE/Weblogic) but didn't manage to complete the task. I
> want to try to get it working on my Netbeans3.2/Linux/Weblogic combo,
enough
> so I can explain it to others. We aren't (yet) using ant to do our builds.
>
> L
>
> --
> Laurent Duperval <mailto:[EMAIL PROTECTED]>
>
> Have you ever imagined a world with no hypothetical situations?
>
>
>
