Its not possible to implement this in a servlet engine, you can't see into other people's sessions.
> you can't see into other people's sessions
Ah yes, of course, Seam keeps its state in the servlet's session, not in some list that is otherwise accessible. Well, I had a nice dream for about 15 minutes ;-)
Has there been any thought about moving the seam state into a managed component keyed by session id, etc...? That way session scoped component could be accessed via normal JNDI from other apps....
Perhaps this might help :
If I am reading it correctly, then it would be possible to write your own custom session manager for seam, which may allow you access to the session for another user.
Of course, it would mean writing a session manager that was as good as the one that comes with your web server in production, and ensuring that no information is put into the session, outside of the seam environment since that wouldn't be available.
But hey, the dream can live on for a little longer...
DG: very cool. If I can get some time, I might take a stab at hacking something in:)