>The reason that I want the locking is this:
>The bean represents rows in a large table that also containes large
>BLOB:s.
>But I dont want the BLOB:s in the EJB server's memory, and I also dont
>want
>the EJB server to perform the READ/WRITE of BLOB:s due to capacity
>reasons.
>Therefore I have constructed a BLOB server that functions as a stream
>server
>for BLOB:s. For example, the server lockes the bean for READ of a BLOB
>when
>a user writes the BLOB to the database through the BLOB server.
I would tend to think a database field called "locked" might do it, with
a 'Y'/'N' value stored in it.
Or an isolation level of TRANSACTION_SERIALIZABLE for that bean
might do it as well, which prevents any other method being called during
the transaction process.
But I don't think Jonas supports Isolation levels yet. So you might have to
go with the "locked" thing.
I think you're trying to do to much with the EJB, it might be better to have
all access to that table handled by the BLOB server which can queue
the requests better then EJB can ...
--
Subvert the dominant paradigm
http://www.cyber4.org/members/grumpy/index.html
