This is the action used to validate Request parameters.
The validation rules are either embedded within the form
<session:form name="info_form">
<session:action>next_page</session:action>
<session:content>
<session:inputxml name="name" type="text" context="trackdemo" path="/user/name"/>
</session:content>
<session:validate>
<root>
<parameter name="name" type="string" nullable="no"/>
<constraint-set name="form_a_set">
<validate name="name"/>
</constraint-set>
</root>
</session:validate>
</session:form>
or described via the external xml file referenced
through the "src" attribute
(the format is defined in AbstractValidatorAction).
Then the constraint-set to be used has to be identified
through the "constraint-set" element
<session:form name="info_form>
<session:action>next_page</session:action>
<session:content>
<session:inputxml name="name" type="text" context="trackdemo" path="/user/name"/>
</session:content>
<session:validate src="descriptor.xml">
<constraint-set name="form_a_set"/>
</session:validate>
</session:form>
Since the validation rules are contained within the form document
they are read and supplied by the SessionTransformer.
So this action has to be used in conjunction with the SessionTransformer.
The "next_page" pipeline might look like this:
<map:match pattern="next_page">
<map:act type="session-form">
<map:generate src="next_page.xml"/>
<map:transform type="session"/>
<map:transform src="simple2html.xsl"/>
<map:serialize/>
</map:act>
<map:generate src="first_page.xml"/>
<map:transform type="session"/>
<map:transform src="simple2html.xsl"/>
<map:serialize/>
</map:match>
where "session-form" is configured as SessionFormAction
See Also: org.apache.cocoon.acting.FormValidatorAction
See Also: org.apache.cocoon.acting.AbstractValidatorAction
author:
Guido Casper
author:
Christian Haul
version:
$Id: SessionFormAction.java 433543 2006-08-22 06:22:54Z crossley $ | 