Orbeon Forms community mailing list - Re: Re: Dispatch with @delay firing multiple times

Re: Re: Dispatch with @delay firing multiple times

Posted by Erik Bruchez on
URL: https://discuss.orbeon.com/Dispatch-with-delay-firing-multiple-times-tp3649476p3932060.html

On the validation issue: the way things work at present is that
properties (MIPs) have a default value:

* required: false
* valid: true (depends on a series of conditions, including "required")
* relevant: true
* readonly: false

The resulting value of a property on a given node when multiple binds
touch that node is the result of a boolean combination:

* required: or
* valid: and
* relevant: and
* readonly: or

In other words the order of binds doesn't matter for a given property,
and a bind does not simply override another one,

I am guessing that this was different in 3.8, and that the change
occurred somewhere along the way to 3.9, following some discussions at
the XForms working group, as well as some work done with XPath
dependencies in the PE version.

I have updated the compatibility notes for 3.9 and added some
documentation on this:

http://wiki.orbeon.com/forms/doc/developer-guide/xforms-mips?pli=1#TOC-Multiple-binds-on-a-given-node

-Erik

On Fri, Oct 21, 2011 at 1:22 PM, Dan Kereliuk <[hidden email]> wrote:

> We're still in the process of upgrading. Right now we're testing on our
> development server and it appears to be running fine. However, we've had to
> change large chunks of our code to work around some of the changed behavior
> between 3.9 and 3.8.
>
> The first problem was with redirect responses being returned from the server
> after a POST request. GET requests worked, but POST would just show a blank
> page instead of redirecting. We've worked around this by returning an xml
> response which would be read and force a redirect indirectly from the client
> instead.
>
> Next, there seems to be a change to how bind statements work. For example,
> for the following:
> <xf:bind nodeset="instance('form')//*" required="true()">
> <xf:bind nodeset="instance('form')/some-node" required="false()">
>
> In 3.8, 'some-node' would *not* be required, because the second bind
> overrides the first. In 3.9, 'some-node' would be required, seemingly
> ignoring the second bind.
>
> --
> View this message in context: http://orbeon-forms-ops-users.24843.n4.nabble.com/Dispatch-with-delay-firing-multiple-times-tp3649476p3926675.html
> Sent from the Orbeon Forms (ops-users) mailing list archive at Nabble.com.
>
>
> --
> 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
> OW2 mailing lists service home page: http://www.ow2.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
OW2 mailing lists service home page: http://www.ow2.org/wws