Motivation

Spring does currently not support session scoped beans/components out of the box. You can decide between singleton or prototype lifecycle, but not having your beans bound to the session lifecycle of web applications. There are plans for integrating such a feature in Spring 1.3 release, but this is not confirmed and there is no schedule.
We will try to point out some possible workarounds for your webwork based applications. First we look at general solutions found among Spring community, dealing with HTTPSession and all that. After that we will discuss the special conditions and requirements found in XWork/WebWork and how that might affect possible solutions. We will show some XWork/WebWork specific solutions for the given problem.

General Solutions for Webapplications

Custom TargetSource with ServletFilter

A quite "clean" solution for web applications in general can be found at JA-SIG. The solution is well documented and can be found here.

XWork/WebWork specific solutions

Preface

TODO: Document

Customized ApplicationContext Implementation

TODO: Document

Customized WW/XW ObjectFactory

TODO: Document

SessionProxy Compont Factory

TODO: Document