Hi!
The behaviour you see is probably due to the use of transactions. It
works just fine (i.e. other clients will be blocked until the
transaction finishes), but if you're really paranoid you can use the
transaction setting REQUIRES_NEW instead of REQUIRED. This will cause
each method call to be in a new transaction. Not necessarily good from a
performance point of view (and again, not needed because of transaction
semantics), but it would accomplish what you ask for.
regards,
Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
