General object-locking gizmo

[nickarls]

Hello,

I need an application level class for general locking with an interface something like

public void lock(Object o, User u);
public void unlock(Object o, User u); // u for verification
public boolean isLocked(Object o);
public List getUserLocks(User u);
public void releaseAllUserLocks(User u);

The issue if the all-too-familiar "what happens when the user just hangs around". If i make this an application-scoped component, how should I handle this?

If I put a destroy-methdod that calls releaseAllUserLocks on a session based component, does it detect the session has ended (probably not) or is it detected only when accessed the next time?

Do I have to maintain a sessionid->user mapping somewhere in the servlet context and use a session-ended-listener? Even then, can I access the seam component from there?

Any other options?

[nickarls]

any theories on this lock-release-on-session-expire-thing?

[amitev]

Create session listener and on destroy notify the application scoped component that this user has left.

[nickarls]

"amitev" wrote:
Create session listener and on destroy notify the application scoped component that this user has left.

Is there any convinient util to get to the seam application context from a servletcontext?