When several users are working on the same data set, how to best handle the concurrency with Seam?
In the specific case I have an application where approx 100 users concurrently work with registering and administrate contacts (i.e. add, edit, remove). The app is built with a stateful session bean as seam component which holds a list of contacts.
What is the best practice to trigger an update of the contacts list between users? I was looking at component events, but although it's not spelled out clearly it seams to me that those events are only propagated within one users context.
Another way could be to to send update events by jms, but a MDB doesn't have reference to my stateful session bean instance. Maybe make the SF bean a message listener itself?
This is of course an issue in a normal ejb application but it gets more noticeable with Seam as more state is held by Seam than normally is done when using stateless session bean as facades.