"Kenneth D. Litwak" wrote:
> I f an entity bean can be passivated in the middle of a transaction, then it
> is conceivable, under CMT, that it cold be passivated in the middle of a method,
> since mehtods map one for one to transactions? Wouldn't that violate the
> requirment for the container to maintain data integrity between the entity bean
> and the resource manager?
Well, yes, under CMT there is SOME method around which the begin..commit is
wrapped, but it need not be a method on your entity bean. It could just as easily
be a method on some session bean that calls many methods on many entity beans.
>
>
> And speaking of entity beans, in the basic scenario
> 1. find a primary key
> 2. get a bean
> 3. call bean methods
> 4. client goes away
> since you woulnd't necessarily use create or remove on an entity bean, how
> do containers geneally deal with potentially huge numbers of entity bean
> instances that have been generated through a finder method that are sitting
> active in memory, since there';s no way for a caller to get rid of them?
> Thanks.
Entity beans can be pooled. When you are done with one, and its state has been
written out to the database, the container can use the same instance structure to
hold the data for another bean. That's one reason your clients never get to hold
references to the instances themselves, but only to their EJBObject wrappers.
John Collins
===========================================================================
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".
