Here's the problem:
UserTransaction is started on client-side. Then, client performs an update on entity
bean, follows by an execution of stateless session bean. Pseudo code:
| utx.begin();
| cmbA.setField("new value");
| sessionBean.readCmbAValue();
| utx.commit();
|
where readCmbAValue opens a JDBC connection and "SELECT" the newly-updated field and
return it.
The code runs fine, and database is updated correctly. However, readCmbAValue always
get the old value. Any hints?
My configuration is:
JBoss 3.2.5 with local transation for MS SQL 7.0
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3843946#3843946
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3843946
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
