Seam essentially does this for you - requests don't hit the bean concurrently, they are serialized.
What is your concern?
my concern is the technical jargon in it. can you break it down for us peter? please
Ok, so this is how *I think* it goes, but someone correct me if I'm wrong :)
1) Stateful beans cannot be accessed concurrently (you get a ConcurrentAccessException)
2) Seam solves this by serializing (queueing) accesses to the component so you don't hit this problem (with the provisos
requests that take place in the same long-running convesation context,
I'm guessing the OP wasn't asking about this, but I'm not sure ;)