Re: [JBoss-user] The first bean
Very true, and in accordance with the spec. EJB isn't about caching live instances of data objects. Never has been. There are very few business applications that have the luxury of sole ownership of their data. For those that do, you may use commit option a or b, others must user c. 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 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 > > > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-user > ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] The first bean
> > 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.sourceforge.net/cgi-bin/cvsweb.cgi/jboss/src/main/org/jboss/ejb/p lugins/EntitySynchronizationInterceptor.java?rev=1.31&content-type=text/x-cv sweb-markup&cvsroot=jboss Last page of code. /Rickard -- Rickard Öberg Software Development Specialist xlurc - Xpedio Linköping Ubiquitous Research Center Author of "Mastering RMI" Email: [EMAIL PROTECTED] ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] The first bean
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 ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] The first bean
> 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? ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] The first bean
> 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 values anymore, is there a way to refresh beans ? Should we turn > 4GL update routines off ? 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. /Rickard -- Rickard Öberg Software Development Specialist xlurc - Xpedio Linköping Ubiquitous Research Center Author of "Mastering RMI" Email: [EMAIL PROTECTED] ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] The first bean
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 is for the data store to notify JBoss of changes. Doing this requires code that is very specific to the data store. For example, if you were using Oracle as a data store, you could have an update trigger on each table set up to send a JMS notification to JBoss, and use message driven beans to cause the reloading of entity bean data. If you stop JBoss while the legacy application uses the data store, and restart it afterwards, entity beans reading the data store for the first time will pick up the latest values, correctly reflecting whatever changes your legacy application made. This is much simpler and will certainly work. ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] The first bean
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 values anymore, is there a way to refresh beans ? Should we turn 4GL update routines off ? Thanks Rene Jansen ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
