Frank Wilson wrote: > > I eventually ended up with something like this, my main mistake was to try > and > run the "upload" (with sfShouldTerminate = false) and the "falconHelloworld" > > tasks in a Compound object. This meant that sometimes the jar would be "run" > before it was uploaded! > (Or "mysteriously" terminate if sfShouldTerminate = true for "upload"!) > > When I tried using a Sequence I ran into another pitfall when I tried to > put the "PasswordProvider" at the beginning. This will (if I remember > correctly) block the sequence > because the PasswordProvider does not "terminate". The moral is of course to > > understand the concept of lifecycles and the lifecycles of individual > component types! :)
The workflow stuff is tricky when you start thinking how you want to combine stuff you want to hang around with sequential things. One of my colleagues, Andrew Farrell, is adding constraint support, so you specify more vaguely what your constraints are, your requirements, and the runtime sorts things out for you without you worrying so much about ordering. > > I have managed to deploy some of the software we work on and I have even got > one of my colleagues to > also use Smartfrog! We managed to implement a little more configurability > this morning using the > information on passwords and properties you provided. > > We are starting to like Smartfrog quite a bit! :) If you like your testing, it's very good for automating bringing up stuff, running tests and tearing them down, which you can then do direct from your JUnit test run. ------------------------------------------------------------------------------ _______________________________________________ Smartfrog-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/smartfrog-users
