We are currently using a stateless session bean to perform a direct update of a table in the database and then using the home method of an entity bean which is mapped over the same table to retrieve the records that have just been updated. Because both transactions are managed by the application server, it should know that the entity bean needs to refresh from the database because some data has changed.
 
However the result is that the direct update is committing the change to the database as you would expect, but the entity bean does not reflect that change when it is created. Do we need to force the entity bean to refresh from the database?
 
We are using 1.5.4 Orion Application Server, EJB 1.1 and MSSQL 7 database.
 
ta,
 
- dave

Reply via email to