I'm using database level auditing with oracle and I've overriden my connection factory to utilize the Oracle extensions. However, since entity beans are cached in the application server I'm not able to audit every time a record is accessed.
I know there has got to be a way to shut off the application server level cache of entity beans and I was wondering if this could be done by overriding the cache-policy-conf parameters in my jboss.xml's container-configuration elements? Or are these parameters for a different type of cache mechanism?
If so would it be best to decrease the max-bean-age parameters or the max-capacity parameter?
I'd really appreciate any help on this.
BTW - There wouldn't be any way for me to specify different entity bean caches for each user that has been logged in via JAAs would there?
The cache is shared.
Commit option B or C