I didn't clearly state my architectural question:
What's the view on sharing a single remote SB interface among
all servlet threads? I.E. a single Business Delegate in the
ServletContext (as apposed to bloating out the Session).
I've not read clear EJB spec / book statements regarding sharing SB or
Entity remote interfaces?
For SB's this should be perfectly ok since the container delagates
methods to bean instances, it should not mater whether it's via a
single remote interface or separate?
Threaded access to a single Entity might be a problem if reentrant
is set to false. I would still believe that the container should
simply queue methods against the Entity in that case.
Thanks for you opinions on the shared reference issue.
curt
> > I'm concerned about sharing a single SB remote interface amoung all
> > sessions (Threads)???
>
> Why not let the container manage the actual number of instances created?
> That would lead to 3000 proxy instances, but just a handful of SLSB.
>
> >
> > Of course SSB remote interfaces will need to be tied to that session!!
>
> I can't quite follow you here. Do you meaqn the http session?
>
> >
> > What about the few Entities that might be accessed from the web tier?
> > <reentrant> vs not reentrant Entities??
>
> Entities that are reentrant, by the EJB 1.1 spec (section
> 9.1.12), are those
> that can be called in a loopback WITHIN the same
> transaction. Different transactional contexts calling the same Entity(by
> this I mean an entity with equal PK) are not reentrant calls. Basically,
> this allows for loopbacks in a call thread, but its use is discouraged by
> the spec.
>
> >
> > I wish the EJB spec was clearer about reentrancy of the remote
> > interface or maybe someone can shed some light??
>
> Again, check out the same section on the spec; transactional context
> (sometimes called activity) plays an important role in
> determining if a call
> is reentrant.
> >
> > Thanks alot to the orion mail list.
> >
> > curt
> >
> >
> > Curt Smith
> > [EMAIL PROTECTED]
> > (w) 404-463-0973
> > (h) 404-294-6686
> >
