Hi!,
All the points were in the context of following setup:
There are 2 ejb servers on the network and each touching the same dbms.(to
be more strict touching same schema).
>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.
Well, its always possible somebody changed data since you last created it/or
used it. It will be right to say, that it will return you the instance which
has to be refreshed to make sure it is consistent.
Yes if you are in a TX load is once. But you have to get out of it at one
point.
>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.
I think its a very strong statement. In an enterprise solution, one dbms is
shared by all sorts of applicatons in a company java/non-java.
It will be correct to say that EJB server always provide instance pooling,
which in turn gives data-caching(which may not be correct in multiserver
env.)
>>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?
I don't need another ejb to point to the same table. I can have an ASP page
that uses the same table. The point is a table can be used by more than one
application.
Punit
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
===========================================================================
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".
