I think all you need is database pessimistic locking (SELECT FOR UPDATE)
which will row lock the inventory item in the database for the length of
the transaction as soon as it is loaded (finder or ejbLoad). You can
turn this on in JBossCMP with the row-locking element and in JAWS I
think you
Thanks Marc for the reply.
The issue with your solution is that the inventory checks are for different
users than the where we are updating inventory. Each time an item is
displayed on a page, the server checks inventory to see if it is still in
stock. This is required because the data keeps
I'm not sure I understand all the details of what you are doing, however it
might be that the firebird database versioning scheme would do what you
want. With this, and the db set to repeatable read, each transaction is
guaranteed a stable view of the committed data as of the time the
I'm not sure that I see a difference between using straight SQL in the session bean
versus finding the appropriate entity bean and querying it for the current inventory.
The advantage to using the entity bean is, of course, the portability that you
mention. I would think that two methods on
