W3C home > Mailing lists > Public > www-forms@w3.org > March 2006

Context consuming actions

From: John Boyer <boyerj@ca.ibm.com>
Date: Fri, 31 Mar 2006 11:38:15 -0800
To: www-forms@w3.org
Cc: w3c-forms@w3.org
Message-ID: <OF3CFFD9F7.97C0D177-ON88257142.0069DEF4-88257142.006BDF9A@ca.ibm.com>
We have been assuming up to now that if an action consumes the context
node, then any subsequent action requiring an XPath evaluation should
fail with an exception.
We've been using binding exception as the most reasonable exception,
but because this exact case is not called out in the spec, it seems 
to ask the community about it...

How are other XForms implementers handling this case? 

To be specific, suppose you have an action sequence that 
performs a delete action followed by a setvalue.  However,
let the delete destroy a node that either is or is an ancestor of
the context node for the action sequence.

What happens when the setvalue runs?

<trigger ref="/some/node">
   <label>Don't press me</label>
   <action ev:event="DOMActivate">
         <delete nodeset="." at="1"/>
         <setvalue ref="." value=" 'oops' "/>

John M. Boyer, Ph.D.
Senior Product Architect/Research Scientist
Co-Chair, W3C XForms Working Group
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@ca.ibm.com  http://www.ibm.com/software/

Blog: http://www.ibm.com/developerworks/blogs/boyer/index.jsp
Received on Friday, 31 March 2006 19:38:44 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:36:17 UTC