>>> -- Long transactions are blocking other accesses; in
particular "read"
>>> accesses, with no reason. We do not want to block an
E-Beans for
> read when
>>> another client writes it and has not committed yet.
(non-blocking
> writes
>>> are typically provided by database vendors like Oracle).
>>
>>Just a hunch: would it be possible to mark the bean as
"TX_REQUIRES" but
>>mark those methods not needing tx:s ("read":s) as
"TX_NOT_SUPPORTED"?
>>Would that yield a "non-blocking read"-effect?
>It depends on your transaction isolation setting for the db.
And of course EJB currently requires that all methods in a
transaction carry the same TX attribute. So, you won't be able to mix
TX_REQUIRES with TX_NOT_SUPPORTED within a transaction.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
