enity bean performance && commit options B/C

[Juergen Petri]

Hi guys!

I really do need your experience.

If your app server isn't the only system accessing and possibly mutating certain tables in the database you have to choose commit options B/C.

Does anybody know how Oracle implements the task of ensuring the correct state of entity beans?

Are they really reloading the state from the database every time I access a getter?

Isn't this a really huge performance hit and is anyone able to provide something more concrete than 'huge'?

Do you know of some 'special tricks' Oracle AS does with Oracle DB?

Thank you very much for your help!

Best regards,
Juergen

[Jeanne Boyarsky]

Please don't post the same question in multiple forums. Please post responses
here.
[ February 09, 2005: Message edited by: Jeanne Boyarsky ]