|
Hi,
Why is the
validContexts in the new option D enabled EntitySynchronizationInterceptor *NOT*
synchrnoized. Will you really have a thread safe implementation in that case?
I'd sent out an implementation of the soft ball cache refresh option sometime
back [which I never got time to check in!!] and that was after finally
persuading Marc that we had to synchronise the hashset. Also,
a. the hashset is unique anyway why check for
presence!
b. there will be only one ctx per bean [correct me
if i am wrong].
Also then we'd planned to have
it as a separate class that could be fit into the inteceptor stack if
required.
Vinay
Vinay
|
- Re: [JBoss-dev] Option D in SynchronizationInterceptor K.V. Vinay Menon
- Re: [JBoss-dev] Option D in SynchronizationIntercept... Georg Rehfeld
