> Is the no of EJBObjects created by the EJB container is one object per
> client or on object per bean instance.
> Does it differ anyhow in entity and session beans. If yes then why?
> I had my own understanding that there in one per client but I developed
> doubts when I read things like shared EJBObject for preventing concurrency
> problems in Richards book(Enterprise JavaBeans).
This is vendor dependent. There may be one per bean instance, one per
client, or any other scheme. The important issue is whether the
contracts between a client and the container can be maintained.
<vendor>
In the case of EJBoss there are no physical EJBObject's *at all*. This
makes it very efficient, and simplifies the container architecture
immensely. You never notice this as a client however, as it will behave
as defined in the EJB-specification.
</vendor>
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.dreambean.com
Question reality
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
