<Nishi>
Sorry for a very delayed response.
<Nishi>
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).
>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.)
<Nishi>
I think this is a very interesting scenario, and somtime sooner or later EJB may
container may need to deal with issues realted to a "DB" being modified via some other
Server/Application etc.
If I get it right "dbIsShared" flag in WebLogic would inform the container that the DB
is being shared and that it needs to "load" data from DB on any subsequent client
request.
Can't the above scenario be extended IMHO even across multiple containers with in the
same EJB server.
If it the case of where we have multiple EJB-Server trying to access DB in two
different VM's as your original question, hope I got it right) then a common
Messaging Service like JMS sounds like a good solution again this is IMHO. This might
allow the first EJB server to publish an event with the Messaging Service after any
modifications to the DB. The second EJB server's "cache" should subscribe to any DB
update events.
Thanks,
Nishi
===========================================================================
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".
