Differences between revisions 16 and 17
Revision 16 as of 2006-06-24 21:15:58
Size: 5065
Comment:
Revision 17 as of 2009-09-20 23:11:52
Size: 5086
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 35: Line 35:
inline:javanet_notloggedin.gif {{attachment:javanet_notloggedin.gif}}
Line 39: Line 39:
inline:javanet_loggedin.gif {{attachment:javanet_loggedin.gif}}
Line 60: Line 60:
Next: [:StrutsManualActionWebComponentSync:Building synchronous login component] Next: [[StrutsManualActionWebComponentSync|Building synchronous login component]]
Line 64: Line 64:
Download the sample: attachment:struts-components.war It also contains source code of business-related files (login action, form, JSP file) as well as suggested modifications for upcoming Struts 1.4 core. Download the sample: [[attachment:struts-components.war]] It also contains source code of business-related files (login action, form, JSP file) as well as suggested modifications for upcoming Struts 1.4 core.

Attention: this page describes functionality that is not yet available! Work in progress!

Struts 1.4 allows building portlet-like web components. A web component is an independent server-side object that is able to accept user input and to render itself.

A Struts Web Component is a combination of:

  • one Action class that handles input events and updates component state;
  • one or more JSP files that represent one or more component subviews;
  • an optional form bean that holds input/output data.

Struts web component uses Action class to process incoming events, and employs JSP technology to render a view. The lifecycle of the components is fully managed by Struts. The components can be used in any application that employs JSP as rendering technology, not just in Struts-based application.

Dual-Mode Capability

Struts utilizes two request processing concepts when dealing with web components:

  • Traditional synchronous HTTP request/response cycle (Non-Ajax mode), and
  • Asynchronous in-place update for Javascript-enabled browsers with XMLHTTPRequest support (Ajax mode).

In synchronous mode the browser submits input data to a fragment, the fragment updates its state if necessary, then the composite page is automatically reloaded by redirecting browser to the original page location. A request that follows pulls up web components and they render themselves.

In Ajax mode browser submits input data using an asynchronous request. Struts renders a view directly in response to this request, no page reloading is needed. HTML markup, returned by a component, is inserted into the composite page without full page refresh.

Pages composed from Struts components look and behave uniformly whether they run in Ajax mode or not. The dual-mode functionality of Struts web components is invaluable for environments where JavaScript is not allowed or in browsers that do not support the XMLHTTPRequest object, like some mobile browsers.

Use Case: Login Component

Consider a website's composite page that contains a login component. The login component authorizes access to member-only area of the website. A non-logged-in user must be presented with login form, a logged-in user should be able to log out. The screenshot from http://www.java.net website illustrates this use case.

A casual visitor sees a login form:

javanet_notloggedin.gif

After a visitor logs in, he is presented with exactly the same page, the only difference is the login form replaced with logout form:

javanet_loggedin.gif

In a regular web application the login/logout module would be responsible for navigation to a proper location after processing user input. In the example above a user must be transferred to the same location that he was browsing before logging in. Therefore login/logout module should be tightly integrated with its parent page, or the parent page must process login/logout events itself.

With Struts you can build truly independent web components that bear no knowledge about a page they are included into. Furthermore, a composite page does not need to know about components contained in it. A web component should mean its own business, that is, handling its input and rendering its markup. Struts takes care about the rest. These boring tasks include:

  • Calculating the location of a composite page (used to automatically reload a composite page).
  • Calculating the location of a component (can be used as submission target).
  • Save page/component locations between requests.
  • Checking whether a browser supports Javascript and if it does, using Ajax to replace component markup in place instead of reloading a whole composite page.

Building A Simple Struts Web Component

This guide explains Struts component functionality by building a simple login component. The Login Component has two states: "Logged In" and "Not Logged In", two corresponding views: "loggedin" and "notloggedin", and two input events: "login" and "logout".

If a user has not logged in yet, the Login Component stays at "Not Logged In" state. The "notloggedin" view displays login form with "username" and "password" fields and "Log In" button. The button submits login form, sending "login" event to the component.

When a user logs in, the Login Component switches to "Logged In" state. The corresponding "loggedin" view displays logout form that shows user name and "Log Out" button. The button submits logout form, sending "logout" event to the component.

We will build a synchronous component first, then we will convert it into a true dual-mode component.

Next: Building synchronous login component

Download WAR file

Download the sample: struts-components.war It also contains source code of business-related files (login action, form, JSP file) as well as suggested modifications for upcoming Struts 1.4 core.

StrutsManualActionWebComponent (last edited 2009-09-20 23:11:52 by localhost)