EJB programming & troubleshooting: Ensuring an entity bean is reloaded from the database
How can you ensure that an enitity bean is reloaded from the database when you 'look' at it.
- Posted by: Demian Krige
- Posted on: January 28 2002 07:40 EST
Oracle seems to look at its cached copy of the entity bean, if something outside the container modifies the table data the entity bean does not reflect the changes. How can we ensure the entity bean sees these changes?
Thanks in advance
- Ensuring an entity bean is reloaded from the database by Richard Kenyon on January 28 2002 09:20 EST
- Ensuring an entity bean is reloaded from the database by Mani Venkatesan on January 28 2002 16:11 EST
- Ensuring an entity bean is reloaded from the database by Web Master on January 29 2002 00:17 EST
- Ensuring an entity bean is reloaded from the database by Demian Krige on January 29 2002 05:14 EST
There's usually a setting in the xml descriptors that needs to be set. This tells the EJB it must perform an ejbLoad for each access.
I don't know about OAS, but in weblogic you set a parameter in the weblogic-ejb-jar.xml file. I assume there'll be a oas-ejb-jar.xml (or something similar) you need for your ejb. There should be a setting in there somewhere.
Can you tell me what this setting is??
could u tell me whether this is possible using time stamp process. if it is then could u tell me how to achieve it
This is exactly the problem. In WebLogic the setting is <DB-IS-SHARED> correct? I cannot find a similar setting in Oracle Application Server...