You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beehive.apache.org by ek...@apache.org on 2006/01/26 19:07:00 UTC
svn commit: r372578 [2/3] - in /beehive/trunk: ./ controls/
docs/forrest/release/ docs/forrest/release/src/documentation/content/xdocs/
docs/forrest/release/src/documentation/content/xdocs/controls/
docs/forrest/release/src/documentation/content/xdocs/...
Modified: beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/jspOverview.xml
URL: http://svn.apache.org/viewcvs/beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/jspOverview.xml?rev=372578&r1=372577&r2=372578&view=diff
==============================================================================
--- beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/jspOverview.xml (original)
+++ beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/jspOverview.xml Thu Jan 26 10:06:32 2006
@@ -11,18 +11,18 @@
binding of the JSPs to the controller class. These tag libraries add a number of features such
as HTML form controls, data grids, and trees. For a detailed overview of the tag libraries
and their usage see the <a href="site:pageflow_tag_overview">NetUI Tag Library Overview</a>. The
- <a href="../apidocs/taglib/taglib-overview-summary.html">tag library API documentation</a>
+ <a href="apidocs/taglib/taglib-overview-summary.html">tag library API documentation</a>
describes all of the details.
</p>
<p> The tag libraries provided by NetUI are:
</p>
<ul>
- <li><a href="../apidocs/taglib/taglib-overview-summary.html#netui"><code><netui:xxx></code></a> --
+ <li><a href="apidocs/taglib/taglib-overview-summary.html#netui"><code><netui:xxx></code></a> --
This is the primary tag library supporting HTML, including the form controls. In addition,
it contains the Tree support.</li>
- <li><a href="../apidocs/taglib/taglib-overview-summary.html#netui-data"><code><netui-data:xxx></code></a> --
+ <li><a href="apidocs/taglib/taglib-overview-summary.html#netui-data"><code><netui-data:xxx></code></a> --
This tag library provides binding to relational data, providing the Data Grid.</li>
- <li><a href="../apidocs/taglib/taglib-overview-summary.html#netui-template"><code><netui-template:xxx></code></a> --
+ <li><a href="apidocs/taglib/taglib-overview-summary.html#netui-template"><code><netui-template:xxx></code></a> --
This tag library provides a very simple templating facility, allowing common elements such
as headers, footers, etc.</li>
</ul>
Modified: beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/lifecycleAndState.xml
URL: http://svn.apache.org/viewcvs/beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/lifecycleAndState.xml?rev=372578&r1=372577&r2=372578&view=diff
==============================================================================
--- beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/lifecycleAndState.xml (original)
+++ beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/lifecycleAndState.xml Thu Jan 26 10:06:32 2006
@@ -35,11 +35,11 @@
focused on the task at hand. In some cases, you may want to create a "long-lived" page flow
controller that <em>never</em> gets destroyed (until the session itself ends). In this case,
you simply set the
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html#longLived()">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html#longLived()">
<code>longLived</code>
</a>
attribute to <code>true</code> on
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html">
<code>@Jpf.Controller</code></a>:
</p>
<source>
@@ -56,7 +56,7 @@
</p>
<p>
You can remove this long-lived controller instance explicitly by calling its
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/FlowController.html#remove">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/FlowController.html#remove">
<code>remove()</code>
</a>
method.
@@ -70,11 +70,11 @@
is created and stored in the session. If a shared flow controller of the right type already
exists in the session, that instance is used instead. Once one is created, it is not removed
unless you call its
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/FlowController.html#remove">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/FlowController.html#remove">
<code>remove()</code>
</a>
method, or
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/PageFlowUtils.html#removeSharedFlow(java.lang.String, javax.servlet.http.HttpServletRequest, javax.servlet.ServletContext)">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/PageFlowUtils.html#removeSharedFlow(java.lang.String, javax.servlet.http.HttpServletRequest, javax.servlet.ServletContext)">
<code>PageFlowUtils.removeSharedFlow()</code></a>.
</p>
</section>
@@ -84,9 +84,9 @@
When you hit a JSF page (e.g., "/mydir/mypage.faces"), the NetUI runtime looks for a class
with the same name and package (e.g., <code>mydir.mypage</code>). If this class exists, is
annotated with
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.FacesBacking.html">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.FacesBacking.html">
<code>@Jpf.FacesBacking</code></a>, and extends
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/FacesBackingBean.html">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/FacesBackingBean.html">
<code>FacesBackingBean</code></a>, then an instance is created and stored in the session.
It is removed from the session on the next request that is not for the same page.
</p>
@@ -115,9 +115,9 @@
</ul>
<p>
To run code at either of these points in the lifecycle, you simply override the appropriate method
- (<a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/PageFlowManagedObject.html#onCreate"><code>onCreate</code></a>
+ (<a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/PageFlowManagedObject.html#onCreate"><code>onCreate</code></a>
or
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/PageFlowManagedObject.html#onDestroy"><code>onDestroy</code></a>), e.g.,
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/PageFlowManagedObject.html#onDestroy"><code>onDestroy</code></a>), e.g.,
</p>
<source>
@Jpf.Controller
@@ -139,7 +139,7 @@
<ul>
<li>
<strong>
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/FlowController.html#beforeAction">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/FlowController.html#beforeAction">
<code>beforeAction</code>
</a>
</strong>
@@ -147,7 +147,7 @@
</li>
<li>
<strong>
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/FlowController.html#afterAction">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/FlowController.html#afterAction">
<code>afterAction</code>
</a>
</strong>
@@ -175,20 +175,20 @@
<ul>
<li>
<strong>
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/PageFlowController.html#onExitNesting">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/PageFlowController.html#onExitNesting">
<code>onExitNesting</code>
</a>
</strong>
- when the page flow is exiting nesting (through a
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Forward.html#returnAction()">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.Forward.html#returnAction()">
<code>returnAction</code>
</a>
on
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Forward.html">
+ <a href="apidocs/javadoc/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">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.SimpleAction.html">
<code>@Jpf.SimpleAction</code>
</a>).
</li>
@@ -198,29 +198,29 @@
<title>JavaServer Faces "Backing Bean" Lifecycle</title>
<p>
JSF backing beans (extended from
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/FacesBackingBean.html">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/FacesBackingBean.html">
<code>FacesBackingBean</code></a>)
have one additional lifecycle method:
</p>
<ul>
<li>
<strong>
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/FacesBackingBean.html#onRestore">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/FacesBackingBean.html#onRestore">
<code>onRestore</code>
</a>
</strong>
- when the backing bean is being restored (along with the page itself) through
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Forward.html#navigateTo()">
- <code>navigateTo</code></a><code>=</code><a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.NavigateTo.html#currentPage"><code>currentPage</code></a>
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.Forward.html#navigateTo()">
+ <code>navigateTo</code></a><code>=</code><a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.NavigateTo.html#currentPage"><code>currentPage</code></a>
or
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Forward.html#navigateTo()">
- <code>navigateTo</code></a><code>=</code><a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.NavigateTo.html#previousPage"><code>previousPage</code></a>
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.Forward.html#navigateTo()">
+ <code>navigateTo</code></a><code>=</code><a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.NavigateTo.html#previousPage"><code>previousPage</code></a>
on
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Forward.html">
+ <a href="apidocs/javadoc/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">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.SimpleAction.html">
<code>@Jpf.SimpleAction</code></a>.
</li>
</ul>
Modified: beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/nestedPageFlow.xml
URL: http://svn.apache.org/viewcvs/beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/nestedPageFlow.xml?rev=372578&r1=372577&r2=372578&view=diff
==============================================================================
--- beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/nestedPageFlow.xml (original)
+++ beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/nestedPageFlow.xml Thu Jan 26 10:06:32 2006
@@ -97,11 +97,11 @@
} </source>
<p>
Note the
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html#nested()">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html#nested()">
<code>nested</code>
</a>=<code>true</code>,
which defines this as a nested page flow. Also note the
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.SimpleAction.html#returnAction()">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.SimpleAction.html#returnAction()">
<code>returnAction</code>
</a>
attribute on the simple action <code>done</code>. When this action is executed, it returns to the
@@ -158,7 +158,7 @@
and changing the desired result, this member variable is kept up-to-date. In the end, it is
<em>returned</em> as an "output form bean" along with the <code>chooseAirportDone</code> return-action,
using the
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.SimpleAction.html#outputFormBean()">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.SimpleAction.html#outputFormBean()">
<code>outputFormBean</code>
</a>
attribute. This is what it looks like in the annotations:
@@ -172,11 +172,11 @@
<note>
You do not have to return a member variable as an output form bean. If you just want to return a
local variable, you would use the
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Forward.html#outputFormBeanType()">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.Forward.html#outputFormBeanType()">
<code>outputFormBeanType</code>
</a>
attribute instead, and you would pass the bean on the
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/Forward.html">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/Forward.html">
<code>Forward</code>
</a>
object returned from an action method, like this:
@@ -226,15 +226,15 @@
</p>
<p>
To navigate to the most recent page, the page flow uses the
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.SimpleAction.html#navigateTo()">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.SimpleAction.html#navigateTo()">
<code>navigateTo</code>
</a>
attribute on a
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.SimpleAction.html">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.SimpleAction.html">
<code>@Jpf.SimpleAction</code>
</a>
(or a
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Forward.html">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.Forward.html">
<code>@Jpf.Forward</code>
</a>), like this:
</p>
@@ -251,15 +251,15 @@
@Jpf.SimpleAction(name="chooseAirportCancelled", navigateTo=Jpf.NavigateTo.previousAction)</source>
<note>
The
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Forward.html#navigateTo()">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.Forward.html#navigateTo()">
<code>navigateTo</code>
</a>
feature is not only used with nested page flows. You can use it on any
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.SimpleAction.html">
+ <a href="apidocs/javadoc/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">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.Forward.html">
<code>@Jpf.Forward</code>
</a>
annotation in your page flow. It just happens to be a very valuable feature when used in conjunction
@@ -273,7 +273,7 @@
returning data from a nested page flow, it is useful for initializing data in the flow. To do this,
you will add a form bean to the <code>begin</code> action of the nested page flow, and in the
calling page flow you will pass an instance of this bean on the
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/Forward.html">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/Forward.html">
<code>Forward</code>
</a>
object that is sent to the nested page flow.
@@ -313,7 +313,7 @@
<title>Pass the form bean from the calling page flow to the nested page flow</title>
<p>
You can pass the initialization bean to the nested page flow by adding it to the
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/Forward.html">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/Forward.html">
<code>Forward</code>
</a>
object that is sent to the nested page flow:
@@ -331,7 +331,7 @@
} </source>
<p>
Note that the
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Forward.html#outputFormBeanType()">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.Forward.html#outputFormBeanType()">
<code>outputFormBeanType</code>
</a>
annotation attribute is optional; it mainly helps tools understand the output of the action, and
@@ -348,15 +348,15 @@
<ul>
<li>
Aside from the
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html#nested()">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html#nested()">
<code>nested=true</code>
</a>
on the
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html">
<code>@Jpf.Controller</code>
</a>
annotation, and defining exit points through
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Forward.html#returnAction()">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.Forward.html#returnAction()">
<code>returnAction</code></a>,
nested page flows are built just like other non-nested page flows.
</li>
@@ -365,7 +365,7 @@
hitting the URL for any of its pages (pages in the same directory path). When nesting occurs, the
original page flow is pushed onto the "nesting stack", and is popped off the stack when the nested
page flow hits an exit point (through a
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Forward.html#returnAction()">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.Forward.html#returnAction()">
<code>returnAction</code>
</a>
attribute).
@@ -376,7 +376,7 @@
<li>
While in a nested page flow, you can get a reference to the calling page flow through
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/PageFlowUtils.html#getNestingPageFlow(javax.servlet.http.HttpServletRequest, javax.servlet.ServletContext)">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/PageFlowUtils.html#getNestingPageFlow(javax.servlet.http.HttpServletRequest, javax.servlet.ServletContext)">
<code>PageFlowUtils.getNestingPageFlow()</code></a>.
</li>
</ul>
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=372578&r1=372577&r2=372578&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 Thu Jan 26 10:06:32 2006
@@ -44,7 +44,7 @@
<p>
Additionally, Beehive weaves magic into controller classes using metadata annotations.
The
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html">
<code>@Jpf.Controller</code>
</a>
annotation is a required marker on any NetUI controller class. The <code>@Jpf.Controller</code>
@@ -125,12 +125,12 @@
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
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/Forward.html">
+ <a href="apidocs/javadoc/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">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.Action.html">
<code>@Jpf.Action</code>
</a>
annotation:
@@ -155,7 +155,7 @@
</p>
<p>The simple action implementations appear below. The following
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.SimpleAction.html">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.SimpleAction.html">
<code>@Jpf.SimpleAction</code>
</a>
annotations define a set of mappings between action names
@@ -211,11 +211,11 @@
<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">
+ <a href="apidocs/javadoc/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">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.Action.html">
<code>@Jpf.Action</code>
</a>
annotation.
@@ -223,7 +223,7 @@
<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
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/Forward.html">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/Forward.html">
<code>Forward</code>
</a>
object, the method indicates which page to
@@ -611,19 +611,19 @@
</p>
<p>
You can implement exception handling using the
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Catch.html">
+ <a href="apidocs/javadoc/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">
+ <a href="apidocs/javadoc/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">
+ <a href="apidocs/javadoc/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">
+ <a href="apidocs/javadoc/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>
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=372578&r1=372577&r2=372578&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 Thu Jan 26 10:06:32 2006
@@ -37,9 +37,9 @@
<p>
If you derive from a base class, then you inherit all its public/protected <em>annotated</em>
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>).
+ (<a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.Action.html"><code>@Jpf.Action</code></a>), exception handler methods
+ (<a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.ExceptionHander.html"><code>@Jpf.ExceptionHander</code></a>), or shared flow fields
+ (<a href="apidocs/javadoc/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>.
@@ -82,7 +82,7 @@
<title>Inheriting the <code>@Jpf.Controller</code> annotation</title>
<p>
When you extend a base class controller, you inherit its
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html">
<code>@Jpf.Controller</code>
</a>
annotation
@@ -110,11 +110,11 @@
} </source>
<p>
The controller <code>DerivedFlow</code> inherits
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html#nested()">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html#nested()">
<code>nested</code></a><code>=true</code>
from the base class, and still keeps its <code>simpleActions</code>. It is as if
<code>DerivedFlow</code> defined the following
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html">
<code>@Jpf.Controller</code>
</a>
annotation:
@@ -128,11 +128,11 @@
) </source>
<p>
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">
+ <a href="apidocs/javadoc/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">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.Forward.html">
<code>@Jpf.Forward</code>
</a>
. In the following example, <code>ChildFlow</code> inherits the
@@ -169,7 +169,7 @@
} </source>
<p>
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">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html">
<code>@Jpf.Controller</code>
</a>
annotation:
@@ -200,11 +200,11 @@
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
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html">
+ <a href="apidocs/javadoc/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
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Catch.html">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.Catch.html">
<code>@Jpf.Catch</code>
</a>
for <code>LoginException</code> is overridden in <code>DerivedFlow</code>.
@@ -252,18 +252,18 @@
<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
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html#nested()">
+ <a href="apidocs/javadoc/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">
+ <a href="apidocs/javadoc/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">
+ <a href="apidocs/javadoc/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()">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.Forward.html#returnAction()">
<code>returnAction</code>
</a>
attribute. This would normally be required.
@@ -275,7 +275,7 @@
</li>
<li>
It is not required to have the
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html">
<code>@Jpf.Controller</code>
</a>
annotation.
@@ -313,7 +313,7 @@
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
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html">
<code>@Jpf.Controller</code>
</a>
annotation, e.g.,
Modified: beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/popupWindows.xml
URL: http://svn.apache.org/viewcvs/beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/popupWindows.xml?rev=372578&r1=372577&r2=372578&view=diff
==============================================================================
--- beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/popupWindows.xml (original)
+++ beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/popupWindows.xml Thu Jan 26 10:06:32 2006
@@ -217,18 +217,18 @@
</netui:configurePopup>
</netui:button></source>
-<p>This attribute is legal on all tags that can raise an action, except for <a href="../apidocs/taglib/beehive.apache.org/netui/tags-html-1.0/imageButton.html"><netui:imageButton></a>.
+<p>This attribute is legal on all tags that can raise an action, except for <a href="apidocs/taglib/beehive.apache.org/netui/tags-html-1.0/imageButton.html"><netui:imageButton></a>.
</p>
<ol>
- <li><a href="../apidocs/taglib/beehive.apache.org/netui/tags-html-1.0/anchor.html"><netui:anchor></a></li>
- <li><a href="../apidocs/taglib/beehive.apache.org/netui/tags-html-1.0/imageAnchor.html"><netui:imageAnchor></a></li>
- <li><a href="../apidocs/taglib/beehive.apache.org/netui/tags-html-1.0/button.html"><netui:button></a></li>
- <li><a href="../apidocs/taglib/beehive.apache.org/netui/tags-html-1.0/area.html"><netui:area></a></li>
+ <li><a href="apidocs/taglib/beehive.apache.org/netui/tags-html-1.0/anchor.html"><netui:anchor></a></li>
+ <li><a href="apidocs/taglib/beehive.apache.org/netui/tags-html-1.0/imageAnchor.html"><netui:imageAnchor></a></li>
+ <li><a href="apidocs/taglib/beehive.apache.org/netui/tags-html-1.0/button.html"><netui:button></a></li>
+ <li><a href="apidocs/taglib/beehive.apache.org/netui/tags-html-1.0/area.html"><netui:area></a></li>
</ol>
-<p>Note - Popup window support uses JavaScript behind the scenes. <a href="../apidocs/taglib/beehive.apache.org/netui/tags-html-1.0/imageButton.html"><netui:imageButton></a> is used for submitting a form <em>without</em> JavaScript, and thus cannot accept the <code>popup</code> attribute.</p>
+<p>Note - Popup window support uses JavaScript behind the scenes. <a href="apidocs/taglib/beehive.apache.org/netui/tags-html-1.0/imageButton.html"><netui:imageButton></a> is used for submitting a form <em>without</em> JavaScript, and thus cannot accept the <code>popup</code> attribute.</p>
</section>
<section id="configurePopupTag"><title>The <netui:configurePopupTag></title>
- <p>Use the <a href="../apidocs/taglib/beehive.apache.org/netui/tags-html-1.0/configurePopup.html"><netui:configurePopup></a>
+ <p>Use the <a href="apidocs/taglib/beehive.apache.org/netui/tags-html-1.0/configurePopup.html"><netui:configurePopup></a>
tag to determine the shape of the popup window.</p>
<source> <netui:button type="submit" value="Pick Color" action="getColor" popup="true">
<strong><netui:configurePopup location="false" width="550" height="150">
@@ -236,7 +236,7 @@
</netui:button></source>
</section>
<section id="retrievePopupOutputTag"><title>The <netui:retrievePopupOutput></title>
- <p>To access values returned by the nested page flow use the <a href="../apidocs/taglib/beehive.apache.org/netui/tags-html-1.0/retrievePopupOutput.html"><netui:retrievePopupOutput></a> tag,
+ <p>To access values returned by the nested page flow use the <a href="apidocs/taglib/beehive.apache.org/netui/tags-html-1.0/retrievePopupOutput.html"><netui:retrievePopupOutput></a> tag,
for example,</p>
<source><netui:retrievePopupOutput dataSource="outputFormBean.color" tagIdRef="colorField"/></source>
<p>Include multiple instances of the tag to set multiple fields.</p>
Modified: beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/servlet_container_adapters.xml
URL: http://svn.apache.org/viewcvs/beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/servlet_container_adapters.xml?rev=372578&r1=372577&r2=372578&view=diff
==============================================================================
--- beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/servlet_container_adapters.xml (original)
+++ beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/servlet_container_adapters.xml Thu Jan 26 10:06:32 2006
@@ -15,9 +15,9 @@
<ol>
<li>
Write a class that implements
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/ServletContainerAdapter.html">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/ServletContainerAdapter.html">
org.apache.beehive.netui.pageflow.ServletContainerAdapter</a>.
- You can extend <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/DefaultServletContainerAdapter.html">
+ You can extend <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/DefaultServletContainerAdapter.html">
org.apache.beehive.netui.pageflow.DefaultServletContainerAdapter</a>.
</li>
<li>
@@ -39,7 +39,7 @@
assertions are disabled. (See <a href="site:devmode">Development and Production Modes</a> for details.)
Even if you do not want to use existing adapters for container-specific features, you may want to write
your own adapter that defines production mode
- (<a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/ServletContainerAdapter#isInProductionMode"><code>ServletContainerAdapter.isInProductionMode()</code></a>)
+ (<a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/ServletContainerAdapter#isInProductionMode"><code>ServletContainerAdapter.isInProductionMode()</code></a>)
according to your own requirements.
</note>
</section>
Modified: beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/sharedFlow.xml
URL: http://svn.apache.org/viewcvs/beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/sharedFlow.xml?rev=372578&r1=372577&r2=372578&view=diff
==============================================================================
--- beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/sharedFlow.xml (original)
+++ beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/sharedFlow.xml Thu Jan 26 10:06:32 2006
@@ -57,14 +57,14 @@
<ol>
<li>
add the
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html">
<code>@Jpf.Controller</code>
</a>
annotation to the class, and
</li>
<li>
extend the
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/SharedFlowController.html"><code>SharedFlowController</code></a>
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/SharedFlowController.html"><code>SharedFlowController</code></a>
class.
</li>
</ol>
@@ -89,7 +89,7 @@
<p>
To share actions, exception handlers, and state from a shared flow, a page flow needs to <em>declare a
reference</em> in its controller class, using the
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.SharedFlowRef.html">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.SharedFlowRef.html">
<code>@Jpf.SharedFlowRef</code>
</a>
annotation. The following example shows two shared flow references being declared for page flow
@@ -147,10 +147,10 @@
<title>Shared Flow Exception Handling</title>
<p>
When an exception occurs and your page flow does not handle it (using
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Catch.html">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.Catch.html">
<code>@Jpf.Catch</code>
</a>), <em>every referenced shared flow gets a chance to handle it</em>. The list of
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.SharedFlowRef.html">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.SharedFlowRef.html">
<code>@Jpf.SharedFlowRef</code>
</a>
annotations is traversed in order, and the first shared flow with a matching <code>@Jpf.Catch</code>
@@ -199,7 +199,7 @@
initialized with a reference to a shared flow controller. This is <em>optional</em>; you do not have to
do this in order to use a shared flow controller. If you do want to access the shared flow controller
object directly, you annotate a member field using the
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.SharedFlowField.html">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.SharedFlowField.html">
<code>@Jpf.SharedFlowField</code>
</a>
annotation. For example, the following page flow controller gets its <code>mySharedFlow</code> field
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=372578&r1=372577&r2=372578&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 Thu Jan 26 10:06:32 2006
@@ -13,7 +13,7 @@
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
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.Controller.html">
<code>@Jpf.Controller</code>
</a>
annotation), and it uses a
@@ -113,7 +113,7 @@
</title>
<p>
Say you are sharing some bit of user interface, like a menu bar. You may be using the NetUI
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/tags/template/Template.html">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/tags/template/Template.html">
Template
</a>
tags, or you may be using Page Flow's support for
@@ -124,7 +124,7 @@
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
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.SharedFlowRef.html">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.SharedFlowRef.html">
<code>@Jpf.SharedFlowRef</code></a>.
</p>
<note>
@@ -138,7 +138,7 @@
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
- <a href="../apidocs/classref_netui/org/apache/beehive/netui/pageflow/annotations/Jpf.SharedFlowRef.html">
+ <a href="apidocs/javadoc/org/apache/beehive/netui/pageflow/annotations/Jpf.SharedFlowRef.html">
<code>@Jpf.SharedFlowRef</code></a>.
</p>
<p>
Modified: beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/tags/datagrid.xml
URL: http://svn.apache.org/viewcvs/beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/tags/datagrid.xml?rev=372578&r1=372577&r2=372578&view=diff
==============================================================================
--- beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/tags/datagrid.xml (original)
+++ beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/tags/datagrid.xml Thu Jan 26 10:06:32 2006
@@ -10,8 +10,8 @@
<p>
The NetUI data grid tag library is a high-level abstraction for rendering grids of data in HTML. This tag library
supports rendering uses from simple tables to complex sortable, filterable, pageable, and updatable grids of data. The
-<a href="../apidocs/taglib/beehive.apache.org/netui/tags-databinding-1.0/dataGrid.html"><netui-data:dataGrid></a> is
-part of NetUI's <a href="../apidocs/taglib/taglib-overview-summary.html#netui-data"><code><netui-data:xxx></code></a> tag
+<a href="apidocs/taglib/beehive.apache.org/netui/tags-databinding-1.0/dataGrid.html"><netui-data:dataGrid></a> is
+part of NetUI's <a href="apidocs/taglib/taglib-overview-summary.html#netui-data"><code><netui-data:xxx></code></a> tag
library.
</p>
</section>