"Bordet, Simone" wrote:
> > we need a way to detect "EJB calls" and let them
> > be reentrant...
> > > a pig really
> >
> > Detect EJB calls somehow is right.
>
> There can be a way in the actual implementation, but I need confirms: the
> client can retrieve the EJBObject only through the
> EntityContext.getEJBObject ? If so, then all the client requests for the
> EJBObject pass through
> EntityEnterpriseContext.EntityContextImpl.getEJBObject and there we can set
> a flag that we can test in the EntityInstanceCache to see if the call is an
> "EJB call" or not.
..*shiver*.. I will pretend I didn't hear that.. ;-)
> > Agree, but how to solve cleanly? One way could be to make an
> > interceptor
> > that sits above the InstanceInterceptor.. ah shit... we still need the
> > instance for ejbRemove though.. not sure if the instance
> > itself can call
> > ejbRemove though.. humdidum.. tricky..
> >
>
> Marc, after your last answers to Rickard and me, I've understood that since
> isReentrant returns true by default I shouldn't check for the reentrant
> problem in rewriting the EntityInstanceCache. But your intention to split
> cache acquisition and cache synchronization means that I should really know
> what will be competence of the EntityInstanceCache and what is not, so I'll
> wait for further details.
Yes, this is a tricky one. Good discussion though.
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
