On Jul 21, 2010, at 7:17 PM, Ivan wrote:
> Or maybe we could have a reference in the ThreadContext for the next
> ThreadContext in the invocation chain ?
Hmm. Maybe we just go simple and hook the wasCancelCalled method up to its own
ThreadLocal. Having more thread locals is generally frowned
Or maybe we could have a reference in the ThreadContext for the next
ThreadContext in the invocation chain ?
2010/7/21 Ivan
> Hi, David :
>Thanks for the info, it almost covers all the implementation details ;-)
>Currently, I have moved all the asynchronous related code logic out from
>
On Jul 21, 2010, at 1:08 AM, romain.manni-bucau wrote:
>
> Hi,
>
> Hazelcast needs a javax.resource.spi.ConnectionManager to create its
> ConnectionFactory.
> I don't know where i could get the good object in openEJB.
>
Is hazelcast packaged as a standard j2ca connector?
david jencks
>
Hi,
Hazelcast needs a javax.resource.spi.ConnectionManager to create its
ConnectionFactory.
I don't know where i could get the good object in openEJB.
-
http://rniamo.o-n.fr http://rniamo.o-n.fr
--
View this message in context:
http://openejb.979440.n4.nabble.com/Clustering-OpenEJB-with-
Hi, David :
Thanks for the info, it almost covers all the implementation details ;-)
Currently, I have moved all the asynchronous related code logic out from
those ***Container. While considering how to implement the
sessioncontext.wasCancellCalled method, I got an issue. Seems that the place
