Hi,
I would appreciate any feedback on the following problem.
I'm developing a web application using jsp/servlets talking to EJB.
Originally the servlets called entities directly for loading and saving data.
I encountered the following scenario a few times but never resolved the cause.
Scenario A:-
1. Start Orion
2. Create a number of "Web application objects" which have entity EJB's behind them.
3. Successfully edit & save these "Web application objects" a number of times.
At all times the integrity of the data seemed to be correct.
4. Shut down Orion
5. Re-start Orion
6. View the summary lists of the previously created "Web application objects"
7. Attempt to drill down into the "Web application objects"
8. I get errors which refer to the disappearence of the sub-parts of the "Web application objects", (Although, I had no problems accessing and editing the same sub-parts before shutting down/restarting Orion (see 3&4 above).
Scenario B:-
The same as A, using a Session bean to wrap calls to entities when saving.
I can understand that the session provides Tx support, so the save is atomic.
==> if any errors encountered during save ==> no "Web application objects" created.
When Orion is restarted, the summary "Web application objects" and the sub-parts are fine.
What I don't understand is the case in Scenario A when summary "Web application objects" and the sub-parts appear to be created and accessible within a web session, but when Orion is restarted, the previously "fine" summary "Web application objects"/sub-parts are broken.
Any ideas, Is Orion caching partially created objects or am I just missing something here.
Thanks,
Ray Power
