Xforms required=true() bug?

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Xforms required=true() bug?

Robert Leftwich
It seems that in some circumstances the required=true() is being ignored. For
example, on the BizDoc NG example the occupation is specified as :

   <xforms:bind nodeset="claim:occupation" required="true()"/>

but the UI accepts an empty entry w/o error. Also, an empty Children's first
name is accepted. Bindings using a multi-level xpath expression such as the
Claimant's name (<xforms:bind nodeset="claim:name-info/claim:last-name"
required="true()"/>) are processed correctly.

Is this a bug or have I missed something?

Robert





--
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
Reply | Threaded
Open this post in threaded view
|

Re: Xforms required=true() bug?

Robert Leftwich
I wrote:
> It seems that in some circumstances the required=true() is being
> ignored. For example, on the BizDoc NG example the occupation is
> specified as :

I neglected to mention that this is using the 3.0b3 version from the ObjectWeb
site (or the on-line examples at Orbeon.com, for that matter).

Robert




--
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
Reply | Threaded
Open this post in threaded view
|

Re: Xforms required=true() bug?

Erik Bruchez
Administrator
In reply to this post by Robert Leftwich
Robert Leftwich wrote:
 > It seems that in some circumstances the required=true() is being
 > ignored. For example, on the BizDoc NG example the occupation is
 > specified as :
 >
 >   <xforms:bind nodeset="claim:occupation" required="true()"/>
 >
 > but the UI accepts an empty entry w/o error. Also, an empty Children's
 > first name is accepted. Bindings using a multi-level xpath expression
 > such as the Claimant's name (<xforms:bind
 > nodeset="claim:name-info/claim:last-name" required="true()"/>) are
 > processed correctly.
 >
 > Is this a bug or have I missed something?

Yes, this is a known bug. See my recent reply in another thread about
valid vs. required, as well as this bug:

http://forge.objectweb.org/tracker/index.php?func=detail&aid=303871&group_id=168&atid=350207

Note that in spite of this bug, you won't be able to submit the XForms
instance if a required field is missing (as mandated by the
spec). AFAIK the bug is just that the UI does not reflect that the
field is required.

-Erik




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