I use JBoss 3.2.0 with default container configuration - 'Standard CMP 2.x EntityBean', commit option B, pessimistick lock. All code working within transactions.
I see the next scenario: * first transaction started, using select with EjbQL selects some entities and print them to the screen using getters (HTML). After first transaction committed. * new transaction started, and do update on same entities group like in first transaction, but using pure SQL. Transaction completed. * started new transaction and do exactly what first transaction do. I think that JBoss should process ejbLoad() for each entity in group, cause commit option is B and entities now not synchronized with cache, but this not happens and I see the old results. What the reason of this strange behaviour ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3838678#3838678 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3838678 ------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X. >From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
