Actually I think this is would work but I would hold off on this. There are
other ways.
We are almost done with the basic container and plugins. We need to finish
EJB compliance, you can help with the cache that mimics the current code.
thanks, regards
marc
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Bordet, Simone
> Sent: Wednesday, August 09, 2000 8:28 AM
> To: 'jBoss Developer'
> Subject: RE: [jBoss-Dev] Entity Instance Cache
>
>
> Err...
>
> >
> > "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*..
>
> Don't, can always be worse ;-)
>
> > I will pretend I didn't hear that.. ;-)
>
> Maybe I was unclear. The problem is that from inside the bean
> implementation
> we can obtain a reference to the EJBObject and call from there, and this
> will result in a false reentrant call for the container. Now, the
> only way I
> currently know to have a reference to the EJBObject from inside
> the bean is
> through the EntityContext. Given this, can't we flag this kind of calls ?
> Maybe I miss something important ?
>
> Simon
>
>
