The best way for getting started with WFNM framework is to run the provided sample which is self-explanatory.
Download from SourceForge the file wfnm-sample-<version>.zip , unpack it and take a look of the content of the "build" directory: it contains two version of the WFNM sample, one for J2EE 1.4 implementations and one for J2EE 1.3 implementations.
The file "wfnm-sample.war" can be deployed into J2EE 1.4 web containers. It has been sucessfully tested with the following J2EE 1.4 implementations:
The file "wfnm-sample-j2ee13.war" can be deployed into J2EE 1.3 web containers. It has been sucessfully tested with the following J2EE 1.3 implementations:
After the deployment, you can open a browser and digit the URL of the WFNM sample, which is tipically something like http://<host>:<port>/wfnm-sample
Please refer to the sample description to have more information about it.
Below a brief description on how the sample shows the WFNM framework capabilities:
It also allows other features like:
The WFNM framework allows to define a webflow by placing a tag on pages which are entry for that webflow. Every page of the sample show the WFNM tags used on the page JSP source, if any is present.
For example a tag <wfnm:webflow name="A"/>
indicates that the page is an entry for webflow A .
The WFNM provide a java factory, called DynamicFactory, that provides the information needed to implement the following dynamic navigation capabilities:
Each page of the sample (excluding pages for entering and configuring the framework) provide the following dynamic navigation buttons:
The WFNM framework allows to automatic clean the session when returning to a previous visited page or webflow. When it happens, it writes on the application server console messages like the following:
Removed from container object set [b1Form, obj_a2_b1, obj_b2_b4, obj_b1_b2, b4Form, b2Form]
If statistics are enabled, a session statistic file called "wfnm-sample-stats.csv" is also created inside the java temporary directory defined by the "java.io.tmpdir" system property (%CATALINA_HOME%/temp for Tomcat 5).
The session statistic file contains information like:
wfnm active | page url | session size |
---|---|---|
TRUE | /jsp/struts/a1.jsp | 1314 |
TRUE | /jsp/struts/a2.jsp | 2676 |
TRUE | /jsp/struts/b1.jsp | 4107 |
TRUE | /jsp/struts/b2.jsp | 5469 |
TRUE | /jsp/struts/b4.jsp | 6831 |
TRUE | /jsp/struts/a2.jsp | 2676 |
In the above example, the file "wfnm-sample-stats.csv" shows numerically how the session size increase and how, by returning to page a2, it is automatically cleaned returning to be of the same size it was when the page a2 has been visited for the first time.
The WFNM framework provides other interesting features that are useful when developing a web application: