Orbeon Forms community mailing list

Using this > oxf.xforms.server.events.plain-value-change property

Classic

List

Threaded

2 messages Options

Hoi Chong

Using this > oxf.xforms.server.events.plain-value-change property

Hi,
According to the Orbeon Wiki,

XForms 1.1 specifies that upon xforms-value-changed, all MIP events must
be dispatched as well. This behavior is usually not desired and can have
a negative performance impact. Setting the following property to true
removes that behavior:

<property as="xs:boolean"
name="oxf.xforms.server.events.plain-value-change" value="true"/>

In this case, xforms-value-changed does not automatically cause MIP
events to be sent. They will be sent only if needed, that is if they
have changed.

Is this property still there?

I am using an Orbeon nightly download from Dec 19th 2009.

In the past, we notice that xforms-value-changed will not be trigger
when we set a field value to the same value.
Eg: An input field has an existing value of "English", we do a setvalue
to update it to "English".
The input field value is not changed, so xforms-value-changed did not
get triggered.

Our forms are design with this behavior in mind, but the recent Orbeon
nightly download do not follow the same behavior pattern.

Thanks.

--
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

Erik Bruchez

Re: Using this > oxf.xforms.server.events.plain-value-change property

Administrator

This has now changed quite a bit on the master branch (which produces
the main nightly builds). This is what we implement now:

http://wiki.orbeon.com/forms/doc/developer-guide/xforms-refresh-events#TOC-Proposal

This proposal is being discussed by the XForms Working Group at W3C.

-Erik

On Thu, Dec 31, 2009 at 1:24 AM, Hoi Chong <[hidden email]> wrote:

> Hi,
> According to the Orbeon Wiki,
>
> XForms 1.1 specifies that upon xforms-value-changed, all MIP events must be
> dispatched as well. This behavior is usually not desired and can have a
> negative performance impact. Setting the following property to true removes
> that behavior:
>
> <property as="xs:boolean" name="oxf.xforms.server.events.plain-value-change"
> value="true"/>
>
> In this case, xforms-value-changed does not automatically cause MIP events
> to be sent. They will be sent only if needed, that is if they have changed.
>
>
>
> Is this property still there?
>
> I am using an Orbeon nightly download from Dec 19th 2009.
>
> In the past, we notice that xforms-value-changed will not be trigger when we
> set a field value to the same value.
> Eg: An input field has an existing value of "English", we do a setvalue to
> update it to "English".
> The input field value is not changed, so xforms-value-changed did not get
> triggered.
>
> Our forms are design with this behavior in mind, but the recent Orbeon
> nightly download do not follow the same behavior pattern.
>
> Thanks.
>
>
> --
> 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