On Apr 6, 2009, at 4:27 AM, Libelah wrote:
> i think there might be a Bug?! as i already wrote in
>
http://www.nabble.com/xforms-select-event-on-xforms%3Aitem-tt13390297.html> this topic i am trying to react to a checkbox being selected
> I am doing this now with the xforms-value-changed event
This time, it isn't a bug :). The issue is with the <xforms:select
appearance="full" ref="always">. The <xforms:select> works in a non-
destructive way: it only adds what you select and removes what you
unselect. In this case you had "0" in the node bound to the
<xforms:select>, but only one checkbox for "1". When you check that
box, the node value becomes "0 1", and then some of your XPath chokes
as it tried to convert that to an integer.
Unless you really need to have 0/1 in the instance, I'd set the node
to be of type xs:boolean and then use an <xforms:input>, which will be
rendered as a checkbox. The value in your instance will be true/false.
Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog:
http://www.orbeon.com/blog/Personal Blog:
http://avernet.blogspot.com/Twitter -
http://twitter.com/avernet--
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
Locked
