Re: [Webwork-devel] Sessionable Actions

[Rickard <ri...@xp...>]

Stefan Mainz wrote:

> I am rather new to webwork, but having built an own framework before i
> need to say that synchronizing is not what you need. You have to lock
> the action as long as the first request is running. Otherwise you ent up
> havin one thread setting one property and the other a second before
> execute is called.


Good point, which is one reason I really don't want to have actions that 
are long-lived and stateful.


> A completely different question, having looked at webwork only at 
> topmost level.
> 
> - Are there any hooks one can place some initialisation. We set up a
>   lot of services upon startup?


No, currently you'd do that as a servlet that is loaded on startup. It 
would be entirely possible to allow some actions to be configured to run 
on startup though. Any idea of how you'd want this to work?


> - Is it possible to add RequestInterceptors, which get called when
>   a browser hits the server and just before the call leaves the server?


Not in the framework, no, but typically you do this by making action 
base classes that overload execute() and do things there before 
delegating to the usual handling. I.e. you do this as action internal 
functionality.


> - Do you have SessionInterceptors wich will be called, when a session
>   terminates?

No, same as above, you'd use regular servlet session event listeners for 
that.

/Rickard

-- 
Rickard Öberg