Hi again! I just want to correct a mistake in my last post... >The problem is that when I call a CMP setter on a bean with commit-option A, the new >value is correctly stored in the database, but the value is not updated in the cached >bean. So if I call for instance setFoo(42), the foo column in the database is updated >to 42, but if I then call getFoo(), I get the old value back. If I flush the EJB >cache or simply restart the server, the correct value is fetched from the database, >and getFoo() returns the correct value. > >One weirdness is that if I call getFoo() immediately after setFoo() (in the same >transaction?) I get the correct value back. It's like the EJB is rolled back at the >end of the transaction. > >The behaviour is the same no matter if I call the setters inside or outside a >transaction when I call the EEJB through a local interface. If I call it through the >remote interface, I get "java.lang.IllegalStateException: There is no tranaction >(sic!) associated with the current thread" when I call the setter without a >transaction, and the same behaviour as with the local interface if I call it within a >transaction.
Sorry, that last sentence is incorrect for JBoss 3.2.2RC3, where there is no difference in behaviour between remote and local interfaces (as it should be). But my actual problem still appears in 3.2.2RC3 as I said. Martin ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
