jakarta-cactus-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vincent Massol" <vmas...@pivolis.com>
Subject RE: ant integration and starting/stoping container w/ ant tasks
Date Sat, 21 Aug 2004 08:09:48 GMT
Hi Jeff,

> -----Original Message-----
> From: news [mailto:news@sea.gmane.org] On Behalf Of Jeff Barrett
> Sent: vendredi 20 août 2004 03:35
> To: cactus-user@jakarta.apache.org
> Subject: ant integration and starting/stoping container w/ ant tasks
> I'm having a conceptual problem here, or at least I think I am.  The
> tasks I seem to need to automate testing with cactus and ant (e.g.
> <cactus> or <runservertests>) require me to specify what tasks to call
> to start and stop the server.  I have one task that starts the server,
> but it just calls a java ant task.  Let's call it weblogic-start.

If you're using WL you may be able to use the existing <weblogic7x> nested

> These other tasks could certainly call weblogic-start no problem.  But,
> as far as I understand it, the thread of control wouldn't return from
> the call to weblogic-start since it hangs around as long as the server
> is running.  Control would never return to the <cactus> or
> <runservertests> tasks so that they could then run the tests.

Then you would run it inside a <parallel> Ant task! Something like:

  <antcall target="weblogic-start"/>
    <wait ...>
    [Do whatever you need to do here]

> Assuming I'm right about this, I'm guessing I would need the ant task
> that starts the server to call some script that will start the server
> but detach control from it.  Any ideas how to do that?  I'm working on a
> windows machine -- is there some way I can maybe startup weblogic as a
> windows service from an ant task?

That would be way too complex compared to the sequential task.


View raw message