Hey
punit malik wrote:
> Can anyone please let me know what I am missing in the following case where
> dbms is touched by 2 different containers.
>
> 1. When one creates/finds an entity bean, container looks in dbms.
Not on find if it has been cached from previous calls. I.e. if you first
create Account "1234", and subsequently do a
Account.findByPrimaryKey("1234") and the instance is still in the cache
then it can be instantly returned.
> 2. Once I have entity bean, whenever i want to use it ejbload will/should be
> called to see if any data has been changed since last use.
Yes, unless the EJB server caches the data which it may do if the EJB
server is the only user of the database, i.e. all your data modification
calls go through EJB.
> Whenever I do anything with entitybean, there is a dbms lookup, so where is
> caching? I think caching of data doesn't make sense if more than one
> container works with same database. The cached data can be incorrect .
If you have more than one EJB which points to the same table, then you
have an interesting setup. Can you expand on when this would be needed?
For example, would you ever deploy a bean Account twice and let them
point to the same database table. Why?
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
Homepage: http://www-und.ida.liu.se/~ricob684
===========================================================================
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".
