[CCXML] Reg execution of subsequent elements after an event is encountered for current element in <transition>

> Hi,
>
> I have a doubt regarding the continuation of processing of  
> subsequent elements in a <transition>, after one of the elements has  
> encountered an error.
>
> Example:
> <transition event=”connection.connected”>
>     <log expr=”’In transition for connection.connected event’”/>
>     <dialogstart src=”BAD_ECMA_EXPR” />
>     <assign name=”state0” expr=”’dialog_Active’”/
> >                                  //assume state0 is the state  
> variable
> </transition>
>
> In this case, evaluation of “src” attribute for <dialogstart> leads  
> to an error.semantic event. Once the interpreter posts this event,  
> should it continue to execute the next element <assign> in the  
> transition?
>
> I felt that the paragraph describing the “continue / do not  
> continue” part for event handling in the CCXML specification was a  
> bit ambiguous. (Section 9.1 Overview – event handling). As per my  
> understanding, the interpreter should not execute the next element  
> in situations like (a) if the evaluation of an attribute of the  
> current element fails or (b) if the interpreter fails in any of its  
> internal processing related to the current element.
>
> The above given snippet is an example of (a).  An example of  
> situation (b) could be say, if <accept> tag is encountered when the  
> connection state is not ALERTING (ex: in a transition for  
> connection.connected) – This may lead to interpreter posting  
> error.connection.wrongstate event
>
> I think it may be more clearly described in the specification as to,  
> under which all conditions shall the interpreter continue to execute  
> subsequent elements. Is it that the interpreter can continue to  
> execute next element if it is able to process all attributes of the  
> current element without error and perform the necessary actions to  
> request the platform to realize the required operation?
>
> Thanks
> Rajesh

> Once selected, an object representing the event being processed is  
> created at transition scope, and the elements inside the  
> <transition> are executed in document order. If an ECMAScript  
> evaluation error occurs during the execution of an element within a  
> <transition>, error.semantic MUST be raised for that element, and  
> successive elements within that <transition> MUST NOT be executed;  
> Note that while an element that references an invalid connection,  
> dialog, or conference identifier also causes the platform to raise  
> error.semantic, these scenarios MUST NOT terminate execution of the  
> <transition> in which that element is contained.
>

> Rajesh:
>
> This is being tracked as ISSUE-614. We will be reviewing this item  
> on the ccxml conference call today.
>
>
> RJ
>
> ---
> RJ Auburn
> CTO, Voxeo Corporation
> Chair, Editor and Chair, CCXML, VBWG, W3C
>
> On Jul 2, 2009, at 9:25 AM, Rajesh N wrote:
>
>> Hi,
>>
>> I have a doubt regarding the continuation of processing of  
>> subsequent elements in a <transition>, after one of the elements  
>> has encountered an error.
>>
>> Example:
>> <transition event=”connection.connected”>
>>    <log expr=”’In transition for connection.connected event’”/>
>>    <dialogstart src=”BAD_ECMA_EXPR” />
>>    <assign name=”state0” expr=”’dialog_Active’”/
>> >                                  //assume state0 is the state  
>> variable
>> </transition>
>>
>> In this case, evaluation of “src” attribute for <dialogstart> leads  
>> to an error.semantic event. Once the interpreter posts this event,  
>> should it continue to execute the next element <assign> in the  
>> transition?
>>
>> I felt that the paragraph describing the “continue / do not  
>> continue” part for event handling in the CCXML specification was a  
>> bit ambiguous. (Section 9.1 Overview – event handling). As per my  
>> understanding, the interpreter should not execute the next element  
>> in situations like (a) if the evaluation of an attribute of the  
>> current element fails or (b) if the interpreter fails in any of its  
>> internal processing related to the current element.
>>
>> The above given snippet is an example of (a).  An example of  
>> situation (b) could be say, if <accept> tag is encountered when the  
>> connection state is not ALERTING (ex: in a transition for  
>> connection.connected) – This may lead to interpreter posting  
>> error.connection.wrongstate event
>>
>> I think it may be more clearly described in the specification as  
>> to, under which all conditions shall the interpreter continue to  
>> execute subsequent elements. Is it that the interpreter can  
>> continue to execute next element if it is able to process all  
>> attributes of the current element without error and perform the  
>> necessary actions to request the platform to realize the required  
>> operation?
>>
>> Thanks
>> Rajesh
>
>
>
>