Let me say publicly that the author of this article may know something about COM
(I'm not an expert on that subject so I will let others judge his competence);
however, I am an expert on EJB and he knows practically nothing about the
technology. The errors in this article are to numerous to mention. Please
completely disregard it and get your information from a more reliable source.
[EMAIL PROTECTED] wrote:
> > Now I'm using WebLogic, whose EJB support, as I understand it, is supposed
> > to offer me a more open way of accessing these kind of services. But I
> > don't see where EJB addresses any of these questions.
>
> There is a good article out there that explains
> the concepts of EJB with respect to scalability.
> You find it here: http://www.objectwatch.com/issue18.htm
> (ObjectWatch Newsletter 18 - In the Fishbowl; Scalability in EJB and MTS)
>
> To summarize its main points:
>
> - The spec. doesn't define any specific mechanism for pooling and
> db connection reuse
> (in fact Weblogic and others do a lot of fancy things on that...)
>
> - But: EJB does not use a Just-In-Time-Activation algorithm for
> instance management; instead it uses another instance management
> algorithm called Instance Pooling.
> (the middle tier instances - session or entity beans -
> are themselves pooled, not the db conn.)
>
> With regards,
> Martin
>
> ===========================================================================
> 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".
===========================================================================
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".
