> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Scott McMullan > Sent: Thursday, July 17, 2003 7:36 PM > To: OXF Users > Subject: RE: XForms processing step destroys XForms data not > explicitly collected by the view > > why does the XForms processor (or other step?) "clobber" data in an XForms > instance document not explicitly collected by an XForms input widget on a > given screen? We may not need this question answered to implement a > multi-screen wizard now that you've provided an alternative, but something > in the future may require it, so if there is an answer, we'd love to know. >
To clarify my question above, in looking more closely at your wizard example: http://www.orbeon.com/oxf/examples/xforms-wizard-firstname you seem to be working around what I describe. For example, consider view step1-firstname.xml: <d:p>Step 1 of 3, enter your first name: <xforms:input ref="user/firstname"/> ... <xxforms:hidden ref="user/lastname"/> <xxforms:hidden ref="user/ssn"/> <xxforms:hidden ref="action"/> </d:p> and view step2-lastname.xml: <d:p>Step 2 of 3, enter your last name: <xforms:input ref="user/lastname"/> ... <xxforms:hidden ref="user/firstname"/> <xxforms:hidden ref="user/ssn"/> <xxforms:hidden ref="action"/> </d:p> Even though each wizard screen collects just a single element from the XForm, each screen has *all remaining* XForm elements present as hidden fields...? Is this to work around the situation I describe above? Thanks. -Scott UC Berkeley Center for Document Engineering _______________________________________________ oxf-users mailing list [EMAIL PROTECTED] http://mail.orbeon.com/mailman/listinfo/oxf-users
