Hello everyone,
This question has been asked before in this mailing list but there has been
no answer yet. I hope that there is some response this time.
The questions are:
1. Does Orion implement EJB object caching? If yes, I'll appreciate some
details on what has been implemented.
2. I want to
I'm also like to hear the answers - we're also seeing an apparent database
write per CMP bean reference.
At this point our test programs (not our real application...) are clients
that access entity beans directly, rather than going through a session bean
facade. We've speculated that the
I'd also like to know a bit more about how the caching works. As for all those
"unnecessary" database writes - I guess they're there to help ensure data
integrity in the event of a crash... You can eliminate many of them though -
from the FAQ:
Q: I am using CMP Entity beans and call many
I have experienced the same thing too.
Would be very helpful if someone from orion team could
provide some info on this.
I should have mentioned that I've already added isModified() to our entity
beans; sorry. I'm seeing an ejbStore on every setXxxx call; isModified()
eliminated the ejbStore that was occurring on every getter. My previous
assumption that the container could tell gets from sets and not store
