Re: allowing <onentry> and <onexit> inside <final>

Really <final>'s <onexit> relates to parent state.
But it can be helpful in case of multiple <final>s.
Otherwise parent <onexit> can be very intricate.

Apropos the same argument can be applied to attribute "task".
Using only <log> in case of <parallel> can essentially complicate programmer's life.

I mean in both case user will have to use complex <if cond=""> statements with In() predicates.

In case of <scxml> parent for <final> I don't see any difference between <onentry> and <onexit>. Because single action which can be between them is sending "Done" message to external invoker. But real sending must be done after action execution.
So in this case <onentry>and<onexit> doesn't have any semantic  distinction.

<parallel> state can't have <final> as child. See  http://lists.w3.org/Archives/Public/www-voice/2007AprJun/0008.html 

       
---------------------------------
We won't tell. Get more on shows you hate to love
(and love to hate): Yahoo! TV's Guilty Pleasures list.