Hi, I
have 2 textboxes in a form; one is bound to integer datatype and the other to
date datatype. When you load the form, these fields are empty and it is not
mandatory that they should be filled in. But with ops3.6 nightly build, it
works as if we can’t submit the form without filling these fields. ie, it
works as if they are mandatory fields. How can we achieve a behavior such that 1)
The form can be submitted leaving these fields blank
and 2)
If the field is filled in, it should be bound to the
corresponding datatype. Else, the alert icon should be shown. Thanks
in advance Jency -- 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 |
Hi Jency,
> I have 2 textboxes in a form; one is bound to integer datatype and the > other to date datatype. When you load the form, these fields are empty > and it is not mandatory that they should be filled in. But with ops3.6 > nightly build, it works as if we can’t submit the form without filling > these fields. ie, it works as if they are mandatory fields. How can we > achieve a behavior such that > > > > 1) The form can be submitted leaving these fields blank and > > 2) If the field is filled in, it should be bound to the > corresponding datatype. Else, the alert icon should be shown. "Support for XForms 1.1 types allowing empty content". So it may be sufficient to bind the instance element to xforms:date instead of xs:date. HTH florian [1] http://www.orbeon.com/ops/doc/home-changes-36#d21e44 -- 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 |
Administrator
|
That's right: an empty xs:integer or xs:date is not valid, which is
why XForms introduces the xforms:integer and xforms:date types (and more). -Erik On Dec 4, 2007, at 7:22 AM, Florian Schmitt wrote: > Hi Jency, > >> I have 2 textboxes in a form; one is bound to integer datatype and >> the other to date datatype. When you load the form, these fields >> are empty and it is not mandatory that they should be filled in. >> But with ops3.6 nightly build, it works as if we can’t submit the >> form without filling these fields. ie, it works as if they are >> mandatory fields. How can we achieve a behavior such that >> 1) The form can be submitted leaving these fields blank and >> 2) If the field is filled in, it should be bound to the >> corresponding datatype. Else, the alert icon should be shown. > > Maybe the "new" xforms datatypes can be useful: [1], the fourth > heading "Support for XForms 1.1 types allowing empty content". So > it may be sufficient to bind the instance element to xforms:date > instead of xs:date. > > HTH > florian > > [1] http://www.orbeon.com/ops/doc/home-changes-36#d21e44 > > > > -- > 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 |
In reply to this post by Jency Thomas
Thank you.... It helped
-----Original Message----- From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez Sent: Thursday, December 06, 2007 6:43 AM To: [hidden email] Subject: Re: [ops-users] binding instance to datatype That's right: an empty xs:integer or xs:date is not valid, which is why XForms introduces the xforms:integer and xforms:date types (and more). -Erik On Dec 4, 2007, at 7:22 AM, Florian Schmitt wrote: > Hi Jency, > >> I have 2 textboxes in a form; one is bound to integer datatype and >> the other to date datatype. When you load the form, these fields >> are empty and it is not mandatory that they should be filled in. >> But with ops3.6 nightly build, it works as if we can't submit the >> form without filling these fields. ie, it works as if they are >> mandatory fields. How can we achieve a behavior such that >> 1) The form can be submitted leaving these fields blank and >> 2) If the field is filled in, it should be bound to the >> corresponding datatype. Else, the alert icon should be shown. > > Maybe the "new" xforms datatypes can be useful: [1], the fourth > heading "Support for XForms 1.1 types allowing empty content". So > it may be sufficient to bind the instance element to xforms:date > instead of xs:date. > > HTH > florian > > [1] http://www.orbeon.com/ops/doc/home-changes-36#d21e44 > > > > -- > 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 |
Free forum by Nabble | Edit this page |