"Process" scope

[Aleksei Valikov]

Hi.

In web applications, it is often desirable to have a "process" scope of beans. 
Process-scoped beans are retained between sessions, but in contradiction to 
session scope there can be many of them per session. An example of process scope 
scenarion is a document deletion:

select document -> display backup options page -> display deletion confirmation 
page -> congratulate that the document is deleted

During the deletion process you somehow need to keep track of the document that 
is being deleted.
You can't model that with a request-scope bean since this will be lost in a 
multiple-step process.
You also can't model this with session-scope bean since if the user tries to 
delete several documents concurrently, you'll get into trouble.
Therefore you need a "process"-scoped bean. There'll be one instance per 
initiated process, but these instances will not be lost across requests.

Are there any existing approaches to process-scoping that could be used with 
MyFaces?

My idea was tracking processes with an URL parameters and use a custom variable 
resolver (+ Spring maybe) to instantiate beans on a per-process basis.

Bye.
/lexi