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 2004/12/02 19:44:24 UTC
[jira] Created: (BEEHIVE-111) Page Flow Overview - outdated information on ValidatorPlugIn support
Page Flow Overview - outdated information on ValidatorPlugIn support
--------------------------------------------------------------------
Key: BEEHIVE-111
URL: http://nagoya.apache.org/jira/browse/BEEHIVE-111
Project: Beehive
Type: Bug
Versions: V1Alpha
Reporter: Rich Feit
Assigned to: Steve Hanson
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://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (BEEHIVE-111) Page Flow Overview - outdated information on ValidatorPlugIn support
Posted by "Julie Zhuo (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-111?page=all ]
Julie Zhuo closed BEEHIVE-111:
------------------------------
Assign To: Julie Zhuo (was: Rich Feit)
Verified with m1rc2 distribution. It no longer have the validatorPlugin as example. It describes the struts merge feature in stead.
> Page Flow Overview - outdated information on ValidatorPlugIn support
> --------------------------------------------------------------------
>
> Key: BEEHIVE-111
> URL: http://issues.apache.org/jira/browse/BEEHIVE-111
> Project: Beehive
> Type: Bug
> Versions: V1Alpha
> Reporter: Rich Feit
> Assignee: Julie Zhuo
>
> 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
[jira] Resolved: (BEEHIVE-111) Page Flow Overview - outdated information on ValidatorPlugIn support
Posted by "Steve Hanson (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-111?page=history ]
Steve Hanson resolved BEEHIVE-111:
----------------------------------
Assign To: Rich Feit (was: Steve Hanson)
Resolution: Fixed
I added the following text:
"
You can also use the Struts merge feature to read configuration data from a pure Struts app into your Page Flow apps configuration files. Ordinarily, your Page Flow's configuration files are generated entirely from your application's JAVA source files (specifically from the metadata annotations that decorate your JAVA source code). But, in cases where you want to integrate a Struts module into your application, you can specify that the configuration files be generated from both the JAVA source files and the Struts module's configuration files, allowing you to change or add any tag in the generated configuration file. For example, suppose you want to override the default request-scoping for an action form to session-scoping. To do this, you simply create a Struts configuration file that overrides the appropriate parts of the Page Flow's configuration file, and then refer to this override file from within the Page Flow's JAVA source file using a special annotation. In particular, you would specify the override file to state that such-and-such and action form should have session-scope rather then request-scope (so that the action form can now be shared with the Struts app).
"
> Page Flow Overview - outdated information on ValidatorPlugIn support
> --------------------------------------------------------------------
>
> Key: BEEHIVE-111
> URL: http://issues.apache.org/jira/browse/BEEHIVE-111
> Project: Beehive
> Type: Bug
> Versions: V1Alpha
> Reporter: Rich Feit
> Assignee: Rich Feit
>
> 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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira