We are experiencing unexplainable behavior while executing session beans inside our webservices.

Here is an example:

aBean.setA("something");
aBean.getA(); <- returns null!

but once the transaction is over, the right information is populated in the DB!
Could it have to do with caching? Transaction isolation?

Thx