Re: Sequence dies alone

Xavier Grehant wrote:
> Hi - I don't know if it's a bug or a feature, but apparently,
> terminating a Sequence normally or abnormally does not terminate its
> children. I loose track of them because they're cut off the
> ProcessCompound but their stuff (e.g the Xen VM their children
> components are supposed to shutdown on termination) stays, whereas it
> doesn't stay under a terminated Compound.

as usual, file a bugrep against us on http://jira.smartfrog.org ; this 
is not intentional.

I've been working with the Workflow stuff recently, trying to get them 
to behave as intended. As you'd expect, with no tests, they arent that 
reliable, especially in the complex lifecycles that havent been explored 
well. There also appear to be common defects in the termination code, 
where stuff designed to start one component after another finishes, also 
seems to kick in at shutdown.

For example. the Delay component starts its child when terminated, 
http://jira.smartfrog.org/jira/browse/SFOS-3

Again, it is bad shutdown handling.

File the defect, ideally with some test cases.

I'm slowly adding test cases to the workflow components to try and lock 
down their behaviour. If you look at 
testharness/testcases/org/smartfrog/test/system/workflow you can see the 
minimal coverage we have right now -the delay and repeat stuff only went 
in last week. We need more tests, and stable workflow components.

Note that I'm also working on an interesting little workflow-related 
component, TestCompound, in services/assertions. This component will, 
when finished

  -deploy something, optionally with an expected failure to deploy, 
and/or an expected self-termination within a given time
  -deploy a test component that is expected to terminate cleanly within 
a specified time
  -undeploy everything

this will let you test-deploy failing configurations, and deploy 
successful configurations against which you run a set of tests. This 
will let us move away from running junit under ant as the test 
methodology, and instead run a sequence of test deployments.Of course, 
for it to work, we need the workflow bits all functional, which is why 
I've been finding bugs there, writing tests, and fixing them. More help 
is welcome.

-steve


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV