According to the specs, it should work. BeanB should synchronise
automatically with the underlying datasource. In fact, u don't need another
entity bean to modify the datasource, u could do it at the RDBMs level and
still get consistent data. This is the job of the EJB container.
Lionel
----- Original Message -----
From: "Dan Christopherson" <[EMAIL PROTECTED]>
To: "JBoss-User" <[EMAIL PROTECTED]>
Sent: Thursday, March 08, 2001 3:37 AM
Subject: Re: [jBoss-User] Enity beans in multiple app servers...
> On Wed, 7 Mar 2001, Doug Ferguson wrote:
>
> > If I deploy the same entity bean on two seperate app servers,
> > will I have iunconsistent behaviour?
> >
> > For ezample. If I update the entity on Server A will Server B
> > have an old copy? If not does this mean that ejbLoad gets called
> > every time that you call a method on a bean?
> ejbLoad will be called when the bean is activated in a transaction. Don't
> call entities directly from your client, rather use a stateless session
> bean to form a transactional wrapper around them.
>
> >
> > Thanks.
> > d.
> >
> >
> >
> > --
> > --------------------------------------------------------------
> > To subscribe: [EMAIL PROTECTED]
> > To unsubscribe: [EMAIL PROTECTED]
> >
>
> --
> Dan Christopherson (danch)
> nVisia Technical Architect (www.nvisia.com)
>
> Opinions expressed are mine and do not neccessarily reflect any
> position or opinion of nVISIA.
>
> --------------------------------------------------------------------------
-
> If you're a capitalist and you have the best goods and they're
> free, you don't have to proselytize, you just have to wait.
> -Eben Moglen
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
