Marius Kotsbak wrote: > I remember from using jboss 2.4.x, that manual changes in the DB would > take some time to be reflected from CMP-beans (no new data even in a new > transaction after the change), probably because jboss was caching the > data, and not writing it to the DB at the same time the set-method was > called.
No, it was because JBoss 2.4 used commit option A by default and in JBoss 3.0 we switched to B. If you want to know about commit options read the EJB spec. > With jboss 3.x, I don't see this behavior. What has happened, > what is the difference? Is there no write-cache now? Does it save one > and one property of the beans? What? Writes are delayed until the end of the transaction, if that is what you mean, but that is not really a cache. > There should be a doc of the CMP-engine to answer these FAQs, at least a > updated description of the settings in the DTD (the comments there > doesn't explain it very well) I am literally writing this chapter right now in another window. -dain _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
