Hello guys,
as the Spec is not very clear about this i'd like to hear how Orbeon implements a submission/@replace="instance" or to be more precise what actually happens directly after it. The Spec defines the following event sequence for a submit: - xforms-submit - xforms-submit-done or xforms-submit-error (4.6.9) This implies that the MIP events 'xforms-valid', 'xforms-invalid', 'xforms-enabled', xforms-disabled' ... are not fired after an instance has been replaced by a submit. But this poses a serious problem in use cases where you have e.g. @relevant constraints defined on your data cause these won't be updated by the replace="instance" and therefore nodes becoming enabled or disabled won't be shown/hidden as appropriate. IMO this is inconsistent with the 'normal' behavior. Why do i ask this here and not on the official XForms list? Well, i heard from customers using different XForms engines at the same time and that other vendors have choosen to fire these events. I just like to hear how the Orbeon team thinks about this cause we'd like to become interoperable with other implementations. Thanks, Joern -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
Joern,
Although I have not assigned actions to these events, but I tend to only use the instance option within submission and all my relevant binds are updated without a problem. Hope this helps to answer your question Ryan Puddephatt Software Engineer TFX Group - IT UK 1 Michaelson Square Livingston West Lothian Scotand EH54 7DP * [hidden email] ( 01506 407 110 7 01506 407 108 >-----Original Message----- >From: [hidden email] [mailto:[hidden email]] >Sent: 15 April 2006 21:47 >To: [hidden email] >Subject: [ops-users] replace="instance" and MIP events > >Hello guys, > >as the Spec is not very clear about this i'd like to hear how Orbeon >implements a submission/@replace="instance" or to be more precise what >actually happens directly after it. > >The Spec defines the following event sequence for a submit: >- xforms-submit >- xforms-submit-done or xforms-submit-error (4.6.9) > >This implies that the MIP events 'xforms-valid', 'xforms-invalid', >'xforms-enabled', xforms-disabled' ... are not fired after an instance >has been replaced by a submit. > >But this poses a serious problem in use cases where you have e.g. >@relevant constraints defined on your data cause these won't be updated >by the replace="instance" and therefore nodes becoming enabled or >disabled won't be shown/hidden as appropriate. IMO this is inconsistent >with the 'normal' behavior. > >Why do i ask this here and not on the official XForms list? Well, i >heard from customers using different XForms engines at the same time and >that other vendors have choosen to fire these events. I just like to >hear how the Orbeon team thinks about this cause we'd like to become >interoperable with other implementations. > >Thanks, > > >Joern > -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
Administrator
|
In reply to this post by Joern Turner-5
Joern,
The spec says this: http://www.w3.org/TR/xforms/slice11.html#submit-event "Once the XML instance data has been replaced, the rebuild, recalculate, revalidate and refresh operations are performed on the model, without dispatching events to invoke those four operations. Submit processing then concludes after dispatching xforms-submit-done." So this appears to be pretty clear, and to ensure that all the MIPs are recomputed and that the events are be fired, since they are fired upon refresh. Where I see a gap in the spec regards repeat indexes though. -Erik Joern Turner wrote: > Hello guys, > > as the Spec is not very clear about this i'd like to hear how Orbeon > implements a submission/@replace="instance" or to be more precise what > actually happens directly after it. > > The Spec defines the following event sequence for a submit: > - xforms-submit > - xforms-submit-done or xforms-submit-error (4.6.9) > > This implies that the MIP events 'xforms-valid', 'xforms-invalid', > 'xforms-enabled', xforms-disabled' ... are not fired after an instance > has been replaced by a submit. > > But this poses a serious problem in use cases where you have e.g. > @relevant constraints defined on your data cause these won't be updated > by the replace="instance" and therefore nodes becoming enabled or > disabled won't be shown/hidden as appropriate. IMO this is inconsistent > with the 'normal' behavior. > > Why do i ask this here and not on the official XForms list? Well, i > heard from customers using different XForms engines at the same time and > that other vendors have choosen to fire these events. I just like to > hear how the Orbeon team thinks about this cause we'd like to become > interoperable with other implementations. > > Thanks, > > > Joern -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
Erik Bruchez wrote:
> Joern, > > The spec says this: > > http://www.w3.org/TR/xforms/slice11.html#submit-event > > "Once the XML instance data has been replaced, the rebuild, > recalculate, revalidate and refresh operations are performed on the > model, without dispatching events to invoke those four > operations. Submit processing then concludes after dispatching > xforms-submit-done." > > So this appears to be pretty clear, and to ensure that all the MIPs > are recomputed and that the events are be fired, since they are fired > upon refresh. thanks for pointing me to that. Must have missed it somehow. Of course this is pretty clear. Thanks Joern > > Where I see a gap in the spec regards repeat indexes though. > > -Erik > > Joern Turner wrote: > > Hello guys, > > > > as the Spec is not very clear about this i'd like to hear how Orbeon > > implements a submission/@replace="instance" or to be more precise what > > actually happens directly after it. > > > > The Spec defines the following event sequence for a submit: > > - xforms-submit > > - xforms-submit-done or xforms-submit-error (4.6.9) > > > > This implies that the MIP events 'xforms-valid', 'xforms-invalid', > > 'xforms-enabled', xforms-disabled' ... are not fired after an instance > > has been replaced by a submit. > > > > But this poses a serious problem in use cases where you have e.g. > > @relevant constraints defined on your data cause these won't be updated > > by the replace="instance" and therefore nodes becoming enabled or > > disabled won't be shown/hidden as appropriate. IMO this is inconsistent > > with the 'normal' behavior. > > > > Why do i ask this here and not on the official XForms list? Well, i > > heard from customers using different XForms engines at the same time and > > that other vendors have choosen to fire these events. I just like to > > hear how the Orbeon team thinks about this cause we'd like to become > > interoperable with other implementations. > > > > Thanks, > > > > > > Joern > > > > ------------------------------------------------------------------------ > > > -- > You receive this message as a subscriber of the [hidden email] mailing list. > To unsubscribe: mailto:[hidden email] > For general help: mailto:[hidden email]?subject=help > ObjectWeb mailing lists service home page: http://www.objectweb.org/wws -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
Free forum by Nabble | Edit this page |