Orbeon Forms community mailing list

xforms-value-changed issue

Classic

List

Threaded

3 messages Options

Park, Michael

xforms-value-changed issue

Hi Erik,

We’ve discussed some of the issues related to the xforms-value-chaged event - http://www.nabble.com/Re%3A-xforms-value-changed-bug---p14405166.html.

However, should the following be happening?

My app uses a select1 with xforms-value-changed to insert 1 of 3 child node choices into a parent node. Ultimately, I PUT to Exist. However, when I GET from Exist an xforms-value-changed event is fired as the form is populated. This unexpectedly fires the xforms-value-changed event that I want coupled with the select1.

Thanks,

Mike

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

Re: xforms-value-changed issue

Mike,

Yes, it's a similar thing: handling of xforms-value-changed upon
instance replacement is not defined by the XForms specification.
Everybody agrees that something should happen in that case, but
exactly what is not yet defined by XForms. In Orbeon Forms, we have
taken the option of sending xforms-value-changed for all controls
bound to nodes of the replaced instance, as we think it's better to
fire too many events rather than to miss events.

At this point, the rule of thumb is to consider that xforms-value-
change may fire too often.

Again, this is not ideal, and we should do better in the future.

-Erik

On Jan 4, 2008, at 5:27 AM, Park, Michael wrote:

> Hi Erik,
>
> We’ve discussed some of the issues related to the xforms-value-
> chaged event - http://www.nabble.com/Re%3A-xforms-value-changed-bug---p14405166.html
> .
>
> However, should the following be happening?
>
> My app uses a select1 with xforms-value-changed to insert 1 of 3
> child node choices into a parent node. Ultimately, I PUT to Exist.
> However, when I GET from Exist an xforms-value-changed event is
> fired as the form is populated. This unexpectedly fires the xforms-
> value-changed event that I want coupled with the select1.
>
> Thanks,
> Mike
>
>
> --
> 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

--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.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

Park, Michael

RE: xforms-value-changed issue

Erik,

I'm really stuck trying to get the behavior I need with the
xforms-value-changed acting that way. Do you have any suggestions?

After I store my data in exist I can get the main instance data fine but
I need a way to get the temporary instance data populated again for the
select1 controls. Below is an example of what I'm doing.

http://riker.services.brown.edu:8080/repo/mods/test.xhtml

Thanks,
Mike

-----Original Message-----
From: Erik Bruchez [mailto:[hidden email]]
Sent: Friday, January 04, 2008 7:15 AM
To: [hidden email]
Subject: Re: [ops-users] xforms-value-changed issue

Mike,

Yes, it's a similar thing: handling of xforms-value-changed upon
instance replacement is not defined by the XForms specification.
Everybody agrees that something should happen in that case, but
exactly what is not yet defined by XForms. In Orbeon Forms, we have
taken the option of sending xforms-value-changed for all controls
bound to nodes of the replaced instance, as we think it's better to
fire too many events rather than to miss events.

At this point, the rule of thumb is to consider that xforms-value-
change may fire too often.

Again, this is not ideal, and we should do better in the future.

-Erik

On Jan 4, 2008, at 5:27 AM, Park, Michael wrote:

> Hi Erik,
>
> We've discussed some of the issues related to the xforms-value-
> chaged event -
http://www.nabble.com/Re%3A-xforms-value-changed-bug---p14405166.html

> .
>
> However, should the following be happening?
>
> My app uses a select1 with xforms-value-changed to insert 1 of 3
> child node choices into a parent node. Ultimately, I PUT to Exist.
> However, when I GET from Exist an xforms-value-changed event is
> fired as the form is populated. This unexpectedly fires the xforms-
> value-changed event that I want coupled with the select1.
>
> Thanks,
> Mike
>
>
> --
> 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