jim
- Original Message -
From: "Sacha Labourey" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, April 06, 2001 8:12 AM
Subject: RE: [JBoss-user] The first bean
> Hello,
>
> >
> > OK Rickard, you've really got my curiosity piqued - where i
> > This is actually a frequently asked question. Change your commit option
to
> C
> > in standardjboss.xml. This will cause the beans state to be updated on
> every
> > transaction.
>
> OK Rickard, you've really got my curiosity piqued - where in the code is
> this particular miracle?
http://cvs
Hello,
>
> OK Rickard, you've really got my curiosity piqued - where in the code is
> this particular miracle?
>
I think there no magic here ;)
The container will simply reload the bean state each time the bean is
requested i.e. no more caching.
Cheers,
Sacha
> This is actually a frequently asked question. Change your commit option to
C
> in standardjboss.xml. This will cause the beans state to be updated on
every
> transaction.
OK Rickard, you've really got my curiosity piqued - where in the code is
this particular miracle?
___
> I have a question not seen before on any of the lists. I deployed
yesterday the first CMP bean in
> JBoss, works fine. The situation:
>
> The bean shows database records and is able to update. However the
database
> is also updated by legacy 4GL, as soon as this happens the beans don't
show
>
renej,
JBoss is software, not magic - even if it is amazing.
There are two ways JBoss could respond to changes in the data store
underlying your CMP beans. The first is for it to poll the data store. This
is not a good idea. It would place an unacceptable load on the data store.
The other way i
I have a question not seen before on any of the lists. I deployed yesterday the first
CMP bean in
JBoss, works fine. The situation:
The bean shows database records and is able to update. However the database
is also updated by legacy 4GL, as soon as this happens the beans don't show
the actual
