Page History

JSP support in WebWork is very easy: by default action-default.xml configures the Dispatcher Result as the default result (see Result Types). This means any JSP 1.2+ container can work with WebWork immediately.

Getting Started

Because JSP support occurs through the Dispatcher Result, which is the default result type, you don't need to specify the type attribute when configuration action.xml:

...

Where name is a property on your action. That's it!

Servlet / JSP Scoped Objects

The following are ways to obtained Application scope attributes, Session scope attributes, Request scope attributes, Request parameters and SAF framework Context scope parameters:-

Application Scope Attribute

Assuming there's an attribute with name 'myApplicationAttribute' in the Application scope.

<saf:property value="%{#application.myApplicationAttribute}" />

Session Scope Attribute

Assuming there's an attribute with name 'mySessionAttribute' in the Session scope.

<saf:property value="%{#session.mySessionAttribute}" />

Request Scope Attribute

Assuming there's an attribute with name 'myRequestAttribute' in the Request scope.

<saf:property value="%{#request.myRequestAttribute}" />

Request Parameter

Assuming there's a request parameter myParameter (eg. http://host/myApp/myAction.action?myParameter=one).

<saf:property value="%{#parameters.myParameter}" />

SAF Context Scope Parameter

Assuming there's a parameter with the name myContextParam in SAF context.

<saf:property value="%{#myContextParam}" />

Tag Support

See the JSP Tags documentation for information on how to use the generic Tags provided by WebWorkthe framework.

Exposing the ValueStack

There are a couple of ways to obtain access to ValueStack from JSPs.