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

Well, perhaps unreachable in most cases, but what about a case like this?

<scxml initialstate="s1">
   <state id="s1">
      <invoke id="i" targettype="scxml">
         <content>
            <scxml initialstate="f1">
               <final id="f1">
                  <onexit>
                     <log expr="'Hello'"/>
                  </onexit>
               </final>
            </scxml>
         </content>
      </invoke>
      <transition event="i.Done" target="f2"/>
   </state>
   <final id="f2"/>
</scxml>

The analogy with something on the lines of

<?xml version="1.0"?>
<scxml initialstate="p">
   <parallel id="p">
      <final id="f1">
         <onexit>
            <log expr="'Hello'"/>
         </onexit>
      </final>
   </parallel >
   <transition event="p.Done" target="f2"/>
   <final id="f2"/>
</scxml>

where the <onexit> _should_ be executed, may be worth considering.

- Torbjörn

On 4/10/07, Serge Voloshenyuk <serge_voloshenyuk@yahoo.com> wrote:
> >But what about the <onexit> children of a <final> which is a child of
> <scxml>?
>
> I think it's unreachable code.
>
>
>  ________________________________
>  Don't get soaked. Take a quick peek at the forecast
>  with theYahoo! Search weather shortcut.
>
>