u wrote:
But entity beans normally reperesents a row in a table
Harvinder:
Very true...But it happens when container gives an identity to an entity
object. Objects in a pool don't have any identity but they are similar.
EJB1.1 Specification doesn't say any thing about the object pooling in case
of entity beans BUT it states it can be one approach which some vendors
follow.
Each entity bean will be having a separate pool i.e. if you have two entity
beans E1 and E2. For E1 and E2 there will be two different pools as you
deploy your entity components.
Even when you call yr finder methods container takes any object from pool,
calls the finder method on that instance and returns it back to pool. Once
container gets the primary key(s) then only it takes any object(s) from pool
and assigns an identity(s) with that.
Regards,
Harvinder
-----Original Message-----
From: Hariharan N [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 01, 2001 4:52 PM
To: [EMAIL PROTECTED]
Subject: Re: Entity Beans
Thanks! But entity beans normally reperesents a row in a table... if so by
instance pooling we are actually having many objects repersenting the same
row! in that case how is the data integrity is maintained across instances!
At 10:18 AM 3/1/2001 -0000, you wrote:
>Hariharan,
>
>Yes , Entity Bean Instances can be pooled. They are basically recyclable -
>how they are pooled depends on yr app server policy.
>
>HTH...
>
>rgds
>
===========================================================================
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".
