You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Rich Feit (JIRA)" <be...@incubator.apache.org> on 2005/06/14 06:48:56 UTC
[jira] Closed: (BEEHIVE-110) Page Flow Overview - outdated information on ValidatorPlugIn support
[ http://issues.apache.org/jira/browse/BEEHIVE-110?page=all ]
Rich Feit closed BEEHIVE-110:
-----------------------------
Fix Version: V1
Resolution: Fixed
Assign To: (was: Rich Feit)
Ahh... infrastructure must have fixed this for us.
> Page Flow Overview - outdated information on ValidatorPlugIn support
> --------------------------------------------------------------------
>
> Key: BEEHIVE-110
> URL: http://issues.apache.org/jira/browse/BEEHIVE-110
> Project: Beehive
> Type: Bug
> Versions: V1Alpha
> Reporter: Rich Feit
> Fix For: V1
>
> At http://incubator.apache.org/beehive/pageflow/pageflow_overview.html, under the section titled "Struts Integration", there is a paragraph about Struts Merge, which uses the ValidatorPlugIn as an example:
> "You can use many advanced Struts features within a Page Flow, for example, the StrutsValidatorPlugIn, which allows you to declare validation rules inside an XML file. Page Flows do not directly support the plug-in, but you can refer your data to a Struts app that does support the plug-in by using the Struts merge feature of Page Flows."
> We've just added direct support, through annotations, for declarative validation via ValidatorPlugIn, so we should use another example here. A decent alternative would be simply changing the scope of an action form from request to session (which involves merging a scope="session" attribute onto an <action> element).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira