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?

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077138#4077138

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077138
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to