Page: http://wiki.cocoondev.org/Wiki.jsp?page=DocumentationTracksProject , version: 23 on Sun Jun 29 21:06:16 2003 by LarryLansing
- ! Track: Forms handling - ** ''please complete - what tracks/documents to study for this?'' + ! Track: Form Handling and Validation + + As with the database track, there are multiple approaches to choose from. + + # FormValidatorAction -- A fairly simple approach to form validation. Requires little or no custom Java code. Could be bad for complex multi-part forms. + ## [Official docs|http://cocoon.apache.org/2.1/userdocs/xsp/logicsheet-forms.html] + ## [FormValidationUsingCocoon] -- wiki docs for the action + ## [XSPFormValidator] -- wiki docs for the companion logicsheet + ## [SimpleFormTransformer] -- This page needs to be written, since the official docs do not adequately describe this transform. + # XMLForm -- A powerful (but complex) approach to form validation. Requires extensive Java code to be written for each form. Good for complicated multi-page form wizards, but overkill for simpler forms. + ## [Official docs|http://cocoon.apache.org/2.1/userdocs/concepts/xmlform.html] + ## [XMLForm wizard|http://cocoon.apache.org/2.1/howto/xmlform-wizard/howto-xmlform-wizard.html] + # [Woody] -- A new approach to form validation that does not seem to require Java code to be written. Only documented in the wiki. + # [Precept] -- Another new approach to form validation, still in very early development. It seems that no documentation exists, except for a README file in the cocoon/samples/precept/ directory. Page: http://wiki.cocoondev.org/Wiki.jsp?page=ErrorHandling , version: 7 on Sun Jun 29 21:09:57 2003 by MarkLeicester - {{{ - <map:pipeline> + {{{<map:pipeline> ? +++ - {{{ - <map:handle-errors> + {{{<map:handle-errors> ? +++ - {{{ - <map:pipeline> + {{{<map:pipeline> ? +++ - The following code goes after the <map:match /> section(s) in your pipeline(s). (I found the example in the sitemap in the "sub" directory under the default Cocoon installation.) ? ^^^^ ^^^ + The following code goes after the {{<map:match />}}; section(s) in your pipeline(s). (I found the example in the sitemap in the "sub" directory under the default Cocoon installation.) ? ^^^ ^^^ + !Error Handling in Cocoon 2.1 + Changes made by Sylvain Wallez are outlined and debated in this [thread|http://marc.theaimsgroup.com/?t=104923297900008&r=1&w=2]. The first message includes details about how backwards compatibility with Cocoon 2.0.x is preserved. + + -- [MarkLeicester] + Page: http://wiki.cocoondev.org/Wiki.jsp?page=LarryLansing , version: 38 on Sun Jun 29 21:09:56 2003 by LarryLansing + !!Form Validation Techniques -- moved to [DocumentationTracksProject] under "Form Handling and Validation] - !!Form Validation Techniques - - # FormValidatorAction -- Fairly simple. Requires little or no custom Java code. Could be bad for complex multi-part forms. - ## [Official docs|http://cocoon.apache.org/2.1/userdocs/xsp/logicsheet-forms.html] - ## [FormValidationUsingCocoon] -- wiki docs for the action - ## [XSPFormValidator] -- wiki docs for the companion logicsheet - ## [SimpleFormTransformer] -- This page needs to be written, since the official docs do not adequately describe this transform. - # XMLForm -- A powerful (but complex) approach to form validation. Requires extensive Java code to be written for each form. Good for complicated multi-page form wizards, but overkill for simpler forms. - ## [Official docs|http://cocoon.apache.org/2.1/userdocs/concepts/xmlform.html] - ## [XMLForm wizard|http://cocoon.apache.org/2.1/howto/xmlform-wizard/howto-xmlform-wizard.html] - # [Woody] -- A new approach to form validation that does not seem to require Java code to be written. Only documented in the wiki. - # [Precept] -- Another new approach to form validation, still in very early development. It seems that no documentation exists, except for a README file in the cocoon/samples/precept/ directory.
