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/11/10 00:49:23 UTC
[jira] Created: (BEEHIVE-71) documentation for settings in netui-config.xml
documentation for settings in netui-config.xml
----------------------------------------------
Key: BEEHIVE-71
URL: http://nagoya.apache.org/jira/browse/BEEHIVE-71
Project: Beehive
Type: Task
Components: Documentation
Versions: V1Beta
Reporter: Rich Feit
Assigned to: Steve Hanson
The netui-config.xml file, which lives in WEB-INF, contains webapp-wide configuration settings for NetUI. Here are some short blurbs -- we can talk more about the details of these, but I wanted to get this in here for tracking.
1) Action interceptors. <pageflow-action-interceptors>. If you want to be notified before every action that's run in the webapp, you configure one of these. A simple example of this is monitoring infrastructure that keeps track of a count of actions raised -- you can register an interceptor that runs the counting code before going to any action. A more complex example is an interceptor that *redirects* you to another page flow before allowing you to go to the current one; for instance, it might take you to a nested page flow that asks you to fill out a "satisfaction survey" before sending you to the destination page flow.
2) Handlers. <pageflow-handlers>. These settings let you override base framework behavior. A good example is the LoginHandler. By default, we use standard Servlet APIs to see if you're logged in, and we use some server-specific APIs to actually log you in when login() is called inside a page flow. If you want to replace this behavior with your own login scheme (which may look at a User database table for login information), you can provide your own LoginHandler that defines methods like login() and isUserInRole().
3) PageFlow Config. <pageflow-config>. This is just the place for settings that configure the page flow runtime across the webapp. If you want to disable file-upload, for instance, you set the multipart-handler to "none". There will be more settings here soon.
--
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-71) documentation for settings in netui-config.xml
Posted by "Nathan Jantz (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-71?page=all ]
Nathan Jantz closed BEEHIVE-71:
-------------------------------
Assign To: Nathan Jantz (was: Rich Feit)
Verified in 1.0m1-rc2.
> documentation for settings in netui-config.xml
> ----------------------------------------------
>
> Key: BEEHIVE-71
> URL: http://issues.apache.org/jira/browse/BEEHIVE-71
> Project: Beehive
> Type: Task
> Components: Documentation
> Versions: V1Beta
> Reporter: Rich Feit
> Assignee: Nathan Jantz
> Priority: Minor
> Fix For: V1Beta
>
> The netui-config.xml file, which lives in WEB-INF, contains webapp-wide configuration settings for NetUI. Here are some short blurbs -- we can talk more about the details of these, but I wanted to get this in here for tracking.
> 1) Action interceptors. <pageflow-action-interceptors>. If you want to be notified before every action that's run in the webapp, you configure one of these. A simple example of this is monitoring infrastructure that keeps track of a count of actions raised -- you can register an interceptor that runs the counting code before going to any action. A more complex example is an interceptor that *redirects* you to another page flow before allowing you to go to the current one; for instance, it might take you to a nested page flow that asks you to fill out a "satisfaction survey" before sending you to the destination page flow.
> 2) Handlers. <pageflow-handlers>. These settings let you override base framework behavior. A good example is the LoginHandler. By default, we use standard Servlet APIs to see if you're logged in, and we use some server-specific APIs to actually log you in when login() is called inside a page flow. If you want to replace this behavior with your own login scheme (which may look at a User database table for login information), you can provide your own LoginHandler that defines methods like login() and isUserInRole().
> 3) PageFlow Config. <pageflow-config>. This is just the place for settings that configure the page flow runtime across the webapp. If you want to disable file-upload, for instance, you set the multipart-handler to "none". There will be more settings here soon.
--
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-71) documentation for settings in netui-config.xml
Posted by "Steve Hanson (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-71?page=history ]
Steve Hanson resolved BEEHIVE-71:
---------------------------------
Assign To: Rich Feit (was: Steve Hanson)
Resolution: Fixed
Fix Version: V1Beta
There is now a full topic on netui-config.xml
See it live at:
http://incubator.apache.org/beehive/v1beta/pageflow/config/netui-config.html
> documentation for settings in netui-config.xml
> ----------------------------------------------
>
> Key: BEEHIVE-71
> URL: http://issues.apache.org/jira/browse/BEEHIVE-71
> Project: Beehive
> Type: Task
> Components: Documentation
> Versions: V1Beta
> Reporter: Rich Feit
> Assignee: Rich Feit
> Priority: Minor
> Fix For: V1Beta
>
> The netui-config.xml file, which lives in WEB-INF, contains webapp-wide configuration settings for NetUI. Here are some short blurbs -- we can talk more about the details of these, but I wanted to get this in here for tracking.
> 1) Action interceptors. <pageflow-action-interceptors>. If you want to be notified before every action that's run in the webapp, you configure one of these. A simple example of this is monitoring infrastructure that keeps track of a count of actions raised -- you can register an interceptor that runs the counting code before going to any action. A more complex example is an interceptor that *redirects* you to another page flow before allowing you to go to the current one; for instance, it might take you to a nested page flow that asks you to fill out a "satisfaction survey" before sending you to the destination page flow.
> 2) Handlers. <pageflow-handlers>. These settings let you override base framework behavior. A good example is the LoginHandler. By default, we use standard Servlet APIs to see if you're logged in, and we use some server-specific APIs to actually log you in when login() is called inside a page flow. If you want to replace this behavior with your own login scheme (which may look at a User database table for login information), you can provide your own LoginHandler that defines methods like login() and isUserInRole().
> 3) PageFlow Config. <pageflow-config>. This is just the place for settings that configure the page flow runtime across the webapp. If you want to disable file-upload, for instance, you set the multipart-handler to "none". There will be more settings here soon.
--
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