You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beehive.apache.org by ri...@apache.org on 2005/08/26 01:38:20 UTC
svn commit: r240157 -
/beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/glossary.xml
Author: rich
Date: Thu Aug 25 16:38:01 2005
New Revision: 240157
URL: http://svn.apache.org/viewcvs?rev=240157&view=rev
Log:
Some fixes/edits/additions to NetUI-related entries in he Glossary.
Modified:
beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/glossary.xml
Modified: beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/glossary.xml
URL: http://svn.apache.org/viewcvs/beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/glossary.xml?rev=240157&r1=240156&r2=240157&view=diff
==============================================================================
--- beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/glossary.xml (original)
+++ beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/glossary.xml Thu Aug 25 16:38:01 2005
@@ -32,18 +32,26 @@
</section>
<section id="glossaryNetUI">
<title>Glossary: NetUI</title>
- <dl id="page_flow">
- <dt><strong>Page Flow</strong></dt>
+ <dl id="pageFlow">
+ <dt><strong>page flow</strong></dt>
<dd>
- A Page Flow consists of one JPF Controller file and one or more JSP pages. A Page Flow is a web
- application module. A whole web application consists of one or more Page Flows.
+ A page flow consists of one <a href="#pageFlowController">controller</a> class and one or more pages,
+ all associated with a single directory path. A web project can contain many page flows.
</dd>
</dl>
- <dl id="controller_file">
- <dt><strong>Page Flow Controller</strong></dt>
+ <dl id="pageFlowController">
+ <dt><strong>page flow controller</strong></dt>
<dd>
- The Controller class is a Java class that handles the data processing tasks in a <a href="#page_flow">Page Flow</a>.
- Controller classes contain the action methods and configuration information (encoded as metadata annotations) for a Page Flow web application.
+ A controller class is a Java class that defines actions, exception handlers, state, etc. related to a
+ <a href="#pageFlow">page flow</a>. Configuration information is defined through annotations on methods,
+ fields, and the class itself.
+ </dd>
+ </dl>
+ <dl id="sharedFlow">
+ <dt><strong>shared flow</strong></dt>
+ <dd>
+ A shared flow is a class that defines actions, exception handlers and state which can be shared by
+ <a href="#pageFlowController">page flow controller</a>s.
</dd>
</dl>
<dl id="databinding">
@@ -54,9 +62,9 @@
the web application:
</p>
<ul>
- <li>in the <a href="#controller_file">Controller file</a></li>
+ <li>in the <a href="#pageFlowController">page flow controller class</a></li>
<li>in container provided JSP implicit objects</li>
- <li>in NetUI framework provided JSP implicit objects</li>
+ <li>in NetUI framework-provided JSP implicit objects</li>
</ul>
<p>
More details about data binding can be found <a href="site:pageflow/databinding">here</a>.
@@ -67,12 +75,12 @@
<dt><strong>form bean</strong></dt>
<dd>
<p>
- Typically, a Form Bean is a server-side representation of the data in an HTML <form> tag. A Form Bean follow ordinary
- Java Bean syntax: each Form Bean is a class consisting of any number of members, each member having a setter and a getter
- method associated with it. Form Beans should also extend <code>java.io.Serializable</code> in order to facilitate persistence
- of Form Bean instances. The Sample Form Bean below has two members, each member has a getter and setter method associated with it.
+ Typically, a form bean is a server-side representation of the data in an HTML <form> tag. A form bean follows ordinary
+ Java Bean syntax: each form bean is a class consisting of any number of properties, each property having a setter and a getter
+ method associated with it. Form bean classes normally implement <code>java.io.Serializable</code> in order to facilitate persistence
+ of form bean instances. The sample form bean below has two properties; each one has a getter and setter method associated with it.
</p>
- <source>
+ <source>
public class ProfileFormBean
implements java.io.Serializable {
@@ -94,20 +102,19 @@
public String getName() {
return this.name;
}
-}
- </source>
- <p>
- Form Beans are most often used to pick up data that is submitted from a <netui:form> tag, or incoming data from a back-end resource.
- Once the POST data has been mapped to a Form Bean instance, the Form Bean is passed to a Page Flow Action method. Note, Form Beans
- can be either standalone Java files or inner-classes of a Page Flow Controller.
- </p>
+} </source>
+ <p>
+ Form beans are most often used to pick up data that is submitted from a <code><netui:form></code> tag.
+ Once the POST data has been mapped to a form bean instance, the form bean is passed to a Page Flow action method.
+ Note that form beans can be either standalone Java files or inner classes of a <a href="#pageFlowController">page flow controller</a>.
+ </p>
</dd>
</dl>
<dl id="netui_tag_lib">
<dt><strong>NetUI JSP Tag Library</strong></dt>
<dd>
- The JSP library for Page Flow web applications. The <netui> tag library uses JSP 2.0 and NetUI databinding expressions to
- bind UI to data provided by the Page Flow Controller and other web application data / resources.
+ The JSP library for NetUI web applications. The <netui> tag library uses JSP 2.0 and NetUI databinding expressions to
+ bind UI to data provided by the <a href="#pageFlowController">page flow controller</a> and other web application data/resources.
</dd>
</dl>
</section>