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/30 21:33:09 UTC
svn commit: r264838 - in
/beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui:
./ annotations/
Author: rich
Date: Tue Aug 30 12:32:59 2005
New Revision: 264838
URL: http://svn.apache.org/viewcvs?rev=264838&view=rev
Log:
Added hyperlinking for annotations (and for a few NetUI classes) throughout.
tests: build.release in docs/forrest (WinXP)
Modified:
beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/annotations/pageflow_method_annotations.xml
beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/databinding.xml
beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/pageFlowControllers.xml
beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/pageFlowInheritance.xml
beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/sharedFlow_vs_inheritance.xml
beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/tutorial_pageflow.xml
Modified: beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/annotations/pageflow_method_annotations.xml
URL: http://svn.apache.org/viewcvs/beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/annotations/pageflow_method_annotations.xml?rev=264838&r1=264837&r2=264838&view=diff
==============================================================================
--- beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/annotations/pageflow_method_annotations.xml (original)
+++ beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/annotations/pageflow_method_annotations.xml Tue Aug 30 12:32:59 2005
@@ -26,7 +26,11 @@
</ul>
<p>
- The <code>@Jpf.Action</code> annotation adorns action methods of the <code>Controller</code>
+ The
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Action.html">
+ <code>@Jpf.Action</code>
+ </a>
+ annotation adorns action methods of the <code>Controller</code>
class. It serves as a container for further configuration annotations and properties.
</p>
Modified: beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/databinding.xml
URL: http://svn.apache.org/viewcvs/beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/databinding.xml?rev=264838&r1=264837&r2=264838&view=diff
==============================================================================
--- beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/databinding.xml (original)
+++ beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/databinding.xml Tue Aug 30 12:32:59 2005
@@ -126,9 +126,10 @@
<a href="../apidocs/classref_netui/org/apache/beehive/netui/tags/databinding/bundle/DeclareBundle.html">
<code><netui-data:declareBundle></code></a>
tag is used to refer to a resource bundle or where a JSP is part of a page flow that has
- resource bundles declared witd tde
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Controller.html">
- <code>@Jpf.MessageBundle</code></a>
+ resource bundles declared with the
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.MessageBundle.html">
+ <code>@Jpf.MessageBundle</code>
+ </a>
annotation.</td>
<td>Provides access to message strings contained in a Java properties file. Strings are referred to by name in tde expression.</td>
</tr>
@@ -253,7 +254,10 @@
<li>when declaring a resource bundle accessible to a JSP via the
<a href="../apidocs/classref_netui/org/apache/beehive/netui/tags/databinding/bundle/DeclareBundle.html">
<code><netui-data:declareBundle></code></a> tag.</li>
- <li>when a page flow with which the JSP is associated exposes resource bundles via the <code>@Jpf.MessageBundle</code>
+ <li>when a page flow with which the JSP is associated exposes resource bundles via the
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.MessageBundle.html">
+ <code>@Jpf.MessageBundle</code>
+ </a>
annotation.</li>
</ul>
<p>
@@ -292,7 +296,10 @@
<code>messages.properties</code> file.
</p>
<p>
- Resource bundles can also be registered with the <code>bundle</code> implicit object by using the <code>@Jpf.MessageBundle</code>
+ Resource bundles can also be registered with the <code>bundle</code> implicit object by using the
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.MessageBundle.html">
+ <code>@Jpf.MessageBundle</code>
+ </a>
class-level annotation. This allows a page flow to also integrate with the implicit message resources object which is
available via a Struts module. These resource bundles will be available to all JSPs that are part of a page flow without having
to use the <code>declareBundle</code> JSP tag. Because a default resource bundle can be associated with a Struts module, the
@@ -587,8 +594,12 @@
${sharedFlow.aSharedFlow.sharedMessage}
]]></source>
<p>
- In a JSP whose current page flow controller is the <code>Controller</code> class defined above, the JSP has access to
- all of the shared flows associated to the page flow via its <code>@Jpf.SharedFlowRef</code> annotation. The shared
+ In a JSP whose current Page Flow controller is the <code>Controller</code> class defined above, the JSP has access to
+ all of the shared flows associated to the page flow via its
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.SharedFlowRef.html">
+ <code>@Jpf.SharedFlowRef</code>
+ </a>
+ annotation. The shared
flow can then be referenced by the <code>name</code> attribute of the <code>SharedFlowRef</code> annotation. In this case,
the name <code>aSharedFlow</code> is used in the JSP 2.0 expression to refer to the <code>SharedFlow</code>'s
<code>sharedMessage</code> property.
Modified: beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/pageFlowControllers.xml
URL: http://svn.apache.org/viewcvs/beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/pageFlowControllers.xml?rev=264838&r1=264837&r2=264838&view=diff
==============================================================================
--- beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/pageFlowControllers.xml (original)
+++ beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/pageFlowControllers.xml Tue Aug 30 12:32:59 2005
@@ -125,9 +125,17 @@
entire class. Again, if you are familiar with Struts, know that
action methods, just like simple actions, are complied as <code><action></code> elements in the
struts-config.xml file.) Syntactically speaking, an action method is a Java method that
- (1) returns the type <code>org.apache.beehive.netui.pageflow.Forward</code> and (2) is
- decorated with the <code>@Jpf.Action/@Jpf.Forward</code> annotations:</p>
-
+ (1) returns the type
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/Forward.html">
+ <code>Forward</code>
+ </a>
+ and (2) is
+ decorated with the
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Action.html">
+ <code>@Jpf.Action</code>
+ </a>
+ annotation:
+ </p>
<source> <strong>@Jpf.Action</strong>(
forwards = {
<strong>@Jpf.Forward( name="someName", path="somePath.jsp", <em>[...other properties...]</em> )</strong>
@@ -148,7 +156,10 @@
</p>
<p>The simple action implementations appear below. The following
- <code>@Jpf.SimpleAction</code> annotations define a set of mappings between action names
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.SimpleAction.html">
+ <code>@Jpf.SimpleAction</code>
+ </a>
+ annotations define a set of mappings between action names
and JSP destinations. When a particular action is invoked,
the user is carried to the corresponding JSP.</p>
<note>Each Controller class requires a simple action or action method named
@@ -198,16 +209,27 @@
<section>
<title>Rudimentary Action Methods: Constant Forwards</title>
- <p>A rudimentary action method must have two syntactical features: (1) it must return the type
- <code>org.apache.beehive.netui.pageflow.Forward</code> and (2) it must be decorated with
- the appropriate metadata annotations (<code>@Jpf.Action/@Jpf.Forward</code>).</p>
-
- <p>The first step in the re-implementation process is to remove the simple action named
+ <p>
+ An action method must have two features:
+ (1) it must the type
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/Forward.html">
+ <code>Forward</code>
+ </a>
+ and (2) must be decorated with the
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Action.html">
+ <code>@Jpf.Action</code>
+ </a>
+ annotation.
+ </p>
+ <p>
+ The first step in the re-implementation process is to remove the simple action named
<code>mypage</code> and replace it with a method named <code>myPage()</code>. By returning a
- <code>org.apache.beehive.netui.pageflow.Forward</code>
- object, the method indicates which page to
- display to the user.
- </p>
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/Forward.html">
+ <code>Forward</code>
+ </a>
+ object, the method indicates which page to
+ display to the user.
+ </p>
<source>
<strong>import org.apache.beehive.netui.pageflow.Forward;</strong>
@@ -592,15 +614,28 @@
<p>
<img src="images/impl-flow-1-exception-handling.png" alt="page flow exception handling"/>
</p>
- <p>You can implement exception handling using the <code>@Jpf.Catch</code>
- and <code>@Jpf.ExceptionHandler</code> annotations. The <code>@Jpf.Catch</code> defines
- some exception to intercept should it arise within the controller class.
- The <code>@Jpf.ExceptionHandler</code>
+ <p>
+ You can implement exception handling using the
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Catch.html">
+ <code>@Jpf.Catch</code>
+ </a>
+ and
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.ExceptionHandler.html">
+ <code>@Jpf.ExceptionHandler</code>
+ </a>
+ annotations. The
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Catch.html">
+ <code>@Jpf.Catch</code>
+ </a>
+ defines some exception to handle should it arise within the controller class.
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.ExceptionHandler.html">
+ <code>@Jpf.ExceptionHandler</code>
+ </a>
annotation is used to define a dedicated method for handling the exception.</p>
<source>
@Jpf.Controller(
<strong>catches={
- @Jpf.Catch(method="handleAccountAlreadyExistsException", type=AccountAlreadyExistsException.class)
+ @Jpf.Catch(type=AccountAlreadyExistsException.class, method="handleAccountAlreadyExistsException")
}</strong>,
simpleActions={
...
Modified: beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/pageFlowInheritance.xml
URL: http://svn.apache.org/viewcvs/beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/pageFlowInheritance.xml?rev=264838&r1=264837&r2=264838&view=diff
==============================================================================
--- beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/pageFlowInheritance.xml (original)
+++ beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/pageFlowInheritance.xml Tue Aug 30 12:32:59 2005
@@ -14,6 +14,13 @@
of controller classes. This document shows ways in which you might use the feature, and also shows
areas that go beyond what you might expect from standard Jave inheritance.
</p>
+ <note>
+ Both inheritance and <a href="site:pageflow_sharedFlow">Shared Flow</a>
+ offer ways to share actions and exception handlers. See
+ <a href="site:pageflow_sharedFlowVsInheritance">Shared Flow vs. Inheritance</a> for
+ some guidelines on when to use each one.
+ </note>
+
</section>
<section id="basic">
<title>Basic Inheritance</title>
@@ -28,8 +35,10 @@
<title>Inheriting Annotated Members</title>
<p>
If you derive from a base class, then you inherit all its public/protected <em>annotated</em>
- members, like action methods (<code>@Jpf.Action</code>), exception handlers
- (<code>@Jpf.ExceptionHandler</code>), or shared flow fields (<code>@Jpf.SharedFlowField</code>).
+ members, like action methods
+ (<a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Action.html"><code>@Jpf.Action</code></a>), exception handler methods
+ (<a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.ExceptionHander.html"><code>@Jpf.ExceptionHander</code></a>), or shared flow fields
+ (<a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.SharedFlowField.html"><code>@Jpf.SharedFlowField</code></a>).
This is not surprising, but it is important to point out. Inheriting an action method means that
you <em>inherit the action</em>. In the following example, <code>DerivedFlow</code> inherits its
<code>begin</code> action from <code>BaseFlow</code>.
@@ -71,7 +80,11 @@
<section id="inheritingControllerAnnotation">
<title>Inheriting the <code>@Jpf.Controller</code> annotation</title>
<p>
- When you extend a base class controller, you inherit its <code>@Jpf.Controller</code> annotation
+ When you extend a base class controller, you inherit its
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html">
+ <code>@Jpf.Controller</code>
+ </a>
+ annotation
in a special way: it is <em>merged</em> with the <code>@Jpf.Controller</code> annotation on your
derived class. Here is a very simple example:
</p>
@@ -97,7 +110,11 @@
<p>
The controller <code>DerivedFlow</code> inherits <code>nested=true</code> from the base class, and
still keeps its <code>simpleActions</code>. It is as if <code>DerivedFlow</code> defined the
- following <code>@Jpf.Controller</code> annotation:
+ following
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html">
+ <code>@Jpf.Controller</code>
+ </a>
+ annotation:
</p>
<source>
@Jpf.Controller(
@@ -107,8 +124,15 @@
}
) </source>
<p>
- A more common example involves merging of arrays of annotations, like <code>@Jpf.SimpleAction</code>
- or <code>@Jpf.Forward</code>. In the following example, <code>ChildFlow</code> inherits the
+ A more common example involves merging of arrays of annotations, like
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.SimpleAction.html">
+ <code>@Jpf.SimpleAction</code>
+ </a>
+ or
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Forward.html">
+ <code>@Jpf.Forward</code>
+ </a>
+ . In the following example, <code>ChildFlow</code> inherits the
simple action <code>baseAction</code> and a catch for <code>LoginException</code>.
</p>
<source>
@@ -141,7 +165,10 @@
{
} </source>
<p>
- It is as if <code>ChildFlow</code> was defined with the following <code>@Jpf.Controller</code>
+ It is as if <code>ChildFlow</code> was defined with the following
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html">
+ <code>@Jpf.Controller</code>
+ </a>
annotation:
</p>
<source>
@@ -168,9 +195,15 @@
<p>
You may have noticed from the <code>ParentFlow</code>/<code>ChildFlow</code> example above that
the <code>begin</code> action in <code>ChildFlow</code> overrode the one in <code>ParentFlow</code>.
- The simple rule is that any annotation or attribute within your <code>@Jpf.Controller</code>
+ The simple rule is that any annotation or attribute within your
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html">
+ <code>@Jpf.Controller</code>
+ </a>
will override one of the same name/type in the base class. In the following example, the
- <code>@Jpf.Catch</code> for <code>LoginException</code> is overridden in <code>DerivedFlow</code>.
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Catch.html">
+ <code>@Jpf.Catch</code>
+ </a>
+ for <code>LoginException</code> is overridden in <code>DerivedFlow</code>.
</p>
<source>
package base;
@@ -214,9 +247,23 @@
<ul>
<li>Even if it is a page flow controller, it does not need to have a <code>begin</code> action.</li>
<li>
- Even if it has <code>nested=true</code> in <code>@Jpf.Controller</code>, it does not have to
- have at least one <code>@Jpf.Forward</code> or <code>@Jpf.SimpleAction</code> with a
- <code>returnAction</code> attribute. This would normally be required.
+ Even if it has
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html#nested()">
+ <code>nested</code>
+ </a><code>=true</code>
+ in <code>@Jpf.Controller</code>, it does not have to have at least one
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Forward.html">
+ <code>@Jpf.Forward</code>
+ </a>
+ or
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.SimpleAction.html">
+ <code>@Jpf.SimpleAction</code>
+ </a>
+ with a
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Forward.html#returnAction()">
+ <code>returnAction</code>
+ </a>
+ attribute. This would normally be required.
</li>
<li>
If you have a local path (e.g., "index.jsp", which does not start with "/"), you will
@@ -224,7 +271,11 @@
local file with this name.
</li>
<li>
- It is not required to have the <code>@Jpf.Controller</code> annotation.
+ It is not required to have the
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html">
+ <code>@Jpf.Controller</code>
+ </a>
+ annotation.
</li>
</ul>
</section>
@@ -258,8 +309,11 @@
If you hit /derived/DerivedFlow.jpf, where do you end up? /base/index.jsp or /derived/index.jsp?
By default, you end up at /derived/index.jsp; the local path is relative to the current page flow
(/derived/DerivedFlow.jpf). You can change this behavior, though, by setting
- <code>inheritLocalPaths=true</code> in your derived class's <code>@Jpf.Controller</code> annotation,
- e.g.,
+ <code>inheritLocalPaths=true</code> in your derived class's
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html">
+ <code>@Jpf.Controller</code>
+ </a>
+ annotation, e.g.,
</p>
<source>
package derived;
@@ -277,4 +331,4 @@
</note>
</section>
</body>
-</document>
\ No newline at end of file
+</document>
Modified: beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/sharedFlow_vs_inheritance.xml
URL: http://svn.apache.org/viewcvs/beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/sharedFlow_vs_inheritance.xml?rev=264838&r1=264837&r2=264838&view=diff
==============================================================================
--- beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/sharedFlow_vs_inheritance.xml (original)
+++ beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/sharedFlow_vs_inheritance.xml Tue Aug 30 12:32:59 2005
@@ -12,7 +12,11 @@
<a href="site:pageflow_sharedFlow">Shared Flow</a>. At first glance the two seem similar; both allow you to share
actions and exception handlers. The general guideline for which to use is simple: <em>use Page Flow
inheritance whenever you can</em>. It allows you to share more than just actions and exception handlers
- (e.g., you inherit everything in the base class <code>@Jpf.Controller</code> annotation), and it uses a
+ (e.g., you inherit everything in the base class
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html">
+ <code>@Jpf.Controller</code>
+ </a>
+ annotation), and it uses a
familiar Java concept in order to do it. This document mainly explains the (important) cases where you
<em>would</em> want to use Shared Flow.
</p>
@@ -119,7 +123,9 @@
page flow controller, just to get the shared actions for something like a menu bar.</em> You may
be including <em>lots</em> of shared user interface (navigation bar, header, footer, etc.), and it
would be bad for each one to require its own base class. Instead, each one can have an associated
- shared flow, which you reference in your page flow using a <code>@Jpf.SharedFlowRef</code>.
+ shared flow, which you reference in your page flow using a
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.SharedFlowRef.html">
+ <code>@Jpf.SharedFlowRef</code></a>.
</p>
<note>
The <a href="site:netui-samples">NetUI Samples</a> show shared flows being used with both the Template
@@ -131,7 +137,9 @@
<p>
In some cases, you simply cannot change the base class for your page flow controller. You may have
a prescribed base class, yet you still want to share some separate group of actions. When this
- happens, you can always reference a shared flow, using a <code>@Jpf.SharedFlowRef</code>.
+ happens, you can always reference a shared flow, using a
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.SharedFlowRef.html">
+ <code>@Jpf.SharedFlowRef</code></a>.
</p>
<p>
Is this a sneaky way to support multiple inheritance? We leave it for you to decide.
Modified: beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/tutorial_pageflow.xml
URL: http://svn.apache.org/viewcvs/beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/tutorial_pageflow.xml?rev=264838&r1=264837&r2=264838&view=diff
==============================================================================
--- beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/tutorial_pageflow.xml (original)
+++ beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/tutorial_pageflow.xml Tue Aug 30 12:32:59 2005
@@ -160,8 +160,13 @@
</p>
<p>The controller class is an ordinary Java class with methods and annotations.</p>
<p>A Page Flow controller class must extend
- <code>org.apache.beehive.netui.pageflow.PageFlowController</code> and be decorated by the
- annotation <code>@Jpf.Controller</code>.</p>
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/PageFlowController.html">
+ <code>PageFlowController</code>
+ </a>
+ and be decorated by the annotation
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html">
+ <code>@Jpf.Controller</code></a>.
+ </p>
<p>The <code>onCreate()</code> method is executed whenever the Controller class is first
instantiated. The <code>onDestroy()</code> method is executed when the Controller
class is destroyed.</p>
@@ -578,7 +583,12 @@
(2) have a maximum length of 30 characters. The age field will also be required and must have a value
in the range 0 to 130.</p>
<p>Open the file <code>pageflow_tutorial/Controller.java</code></p>
- <p>Edit the <code>@Jpf.Action</code> annotation for the <code>processData</code> method in the
+ <p>
+ Edit the
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Action.html">
+ <code>@Jpf.Action</code>
+ </a>
+ annotation for the <code>processData</code> method in the
<code>Controller.java</code> file so it appears as follows. Code to add appears in bold.
Don't forget the comma after the <code>forwards={...}</code> element!</p>
<p><strong><code>Controller.java</code></strong></p>
@@ -737,7 +747,10 @@
<p>Open the file <code>pageflow_tutorial/Controller.java</code></p>
<p>Edit <code>Controller.java</code> so it appears as follows. Code to add appears
in bold type. Don't forget to add the <code>useFormBean</code> property to the
- <code>@Jpf.Action</code> annotation of the <code>processData</code> method. The
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Action.html">
+ <code>@Jpf.Action</code>
+ </a>
+ annotation of the <code>processData</code> method. The
ProfileForm is page flow-scoped for this example, using the same Form Bean
instance in multiple Action methods.</p>
<p><strong><code>Controller.java</code></strong></p>
@@ -1029,7 +1042,12 @@
<p>In this step you will add a Simple Action to the existing Shared Flow. The Action forwards to the
help page created in the previous step and will be available to multiple page flows in the application.</p>
<p>Open the existing Shared Flow file <code>pageflow_tutorial/WEB-INF/src/shared/SharedFlow.java</code></p>
- <p>Edit the <code>@Jpf.Controller</code> annotation for the Shared Flow controller class, <code>SharedFlow</code>, in the <code>SharedFlow.java</code> file and add the <code>simpleActions</code> property. Code to add appears in bold. Don't forget the comma after the <code>catches={...}</code> element!</p>
+ <p>
+ Edit the
+ <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html">
+ <code>@Jpf.Controller</code>
+ </a>
+ annotation for the Shared Flow controller class, <code>SharedFlow</code>, in the <code>SharedFlow.java</code> file and add the <code>simpleActions</code> property. Code to add appears in bold. Don't forget the comma after the <code>catches={...}</code> element!</p>
<p><strong><code>SharedFlow.java</code></strong></p>
<source>
...