Hi Vincent, I've had a look to the Cargo branch, but haven't noticed much update for the cargo stuff. A HEAD branch would be more of help. The three steps users currently have to carry out are relatively simple enough for them. I prefer to keep the existing cargo tasks unless you or other people have some ideas in mind to modify or change them. I'm still new to these :) I think how Cargo can be integrated into Cactus would depend on how stable Cargo API is. I guess if JSR88 is done for Cargo then there will not many changes expected after that for the deployment API, similarly with JSR77. Therefore, in my opitions an early plan for the Cargo API would be good, if peole in Cargo refactor the API as an anticiapation for compatibility with these standards.
Thanks Xuan -----Original Message----- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Monday, 4 July 2005 5:25 PM To: 'Cactus Developers List' Subject: RE: Cactus Task Xuan, I forgot to ask if you've had a look at the CARGO branch that I mentioned in an earlier email? It was relatively advanced and should provide help to you. You could this branch and merge it into a newer branch if you wanted. What I'd like is for you to start a design discussion from a user point of view. As a user what would I have to change from how I currently use Cactus? If you look into the CARGO branch you'll see that in the first incarnation, the way users would have to use Cactus would be: 1/ create a war 2/ cactify the war 3/ use a cargo task to configure/start the container 4/ use junit to start the cactus tests 5/ use a cargo task to stop the container It looks a bit "heavy" on users as currently they only have to do: 1/ create a war 2/ cactify the war 3/ use the cactus task to configure/start/stop container and execute the tests However, if we do keep the <cactus> task, we MUST make it completely transparent WRT cargo as we don't want to deliver a new version of Cactus whenever Cargo changes and we do want users to be able to benefit from any change in Cargo. What do you think of all this? Thanks -Vincent > -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: lundi 4 juillet 2005 09:18 > To: 'Cactus Developers List' > Subject: RE: Cactus Task > > Hi Xuan, > > > -----Original Message----- > > From: Xuan Nguyen [mailto:[EMAIL PROTECTED] > > Sent: samedi 2 juillet 2005 14:47 > > To: 'Cactus Developers List' > > Subject: Cactus Task > > > > Hi Vincent, > > If you have time, could you explain the the way Cactus Task deploys > > a > war > > file (I use the cargo_17_branch). > > I can create a branch for you from HEAD if you want so you have the > latest files. Let me know. Remember that the longer something stays on > a branch the harder it is to merge it back later on... ;-) > > > I can see the sequence Cactus > > Task->ContainerRunner->GenericContainer, startup two threads (Hooks) > > Task->ContainerRunner->and > > load the container class from the resource bundle the starts it up > > but I miss out the place where the war file is moved to webapp > > folder. > > This is done in the container implementation. For example for Tomcat > you'll find this in the prepare() methods in > jakarta- > cactus\integration\ant\src\java\org\apache\cactus\integration\ant\co > ntainer\tomcat\AbstractCatalinaContainer.java > > [snip] > > Thanks > -Vincent > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
