Now it works as I hoped, thanks a lot!
It seems that the essential point was this "tuned-updates".
--
Timo Fager
"Castro, David" wrote:
>
> This is "tuned-updates" in jboss.xml (If I understand your question
> correctly)
>
> true - update if data changed
> false - update always
>
> > -----Original Message-----
> > From: Jonathan Keller [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, March 01, 2001 10:47 AM
> > To: JBoss-User
> > Subject: Re: [jBoss-User] Problem with CMP and shared database
> >
> >
> >
> > I took a look into the source code, and it appears (although
> > I'm not sure) that
> > the while the container does call ejbStore, it does not
> > actually send SQL to the
> > database unless some data has changed. So that works if all
> > you're doing is
> > calling getXXX methods.
> >
> > Does anyone have an explanation of why this happens or a
> > configuration to stop
> > it? I tried changing the transaction attribute on the get
> > functions to no avail.
> > I would also like to avoid using the isModified() method
> > since that's not part of
> > the EJB 1.1 spec. (Is it part of 2.0?)
> >
> > (clip clip)
> >
> > > > > > > Hello,
> > > > > > >
> > > > > > > We have a database used by both EJB and several
> > > > > > > non-EJB tools. Problem is, that whenever a getField()
> > > > > > > method of a bean is invoked, the bean writes its data
> > > > > > > back to database. The data may have been changed
> > > > > > > in the database, so the bean should actually read
> > > > > > > it from there.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
