Hi everyone, Thank Vincent for the suggestion in the last post. I have decided to keep the Cactus tasks. From the user's side, running cactus test remains with 3 steps (start container/cactify/config+start+stop). So my plan is rather straight forward: Modifying Cactus Task so it: 1.call the cargo ant task to set the war/ear in configuration, start the container up. 2.start the test (junit) 3. call the cargo ant task to shutdown the container
The start/config/shutdown will be modified through containerset task. I suspect about an absolute transparent integration (unless someone can convince me this :). In my opinion, we need to pass argument like containerid, port, action, etc...into Cargo side and hence a change on these attributes from Cargo side will have impact on Cactus. I would be appreciate for having ideas from your guys on this soon Thanks Xuan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
