Hi,

We have an application which is consisted of 2 ears: each ear has its own hibernate session factory.
There are common objects for those 2 ears (each ear represents a product), managed by hibernate (persistent object).

We work with secondary-level cache, but we would like to disable caching for those common objects only, and to gain the benefit of it for the rest of the application. The reason is the need of reflecting each change between the 2 apps.

Is there a possibility to ignore the cache for few objects only?
I wasn't able to find a configuration on the level of object.

Thanks a lot,
Moti

Hibernate version: 3.0.5

Name and version of the database you are using: Oracle 10g

Hi

to use second-level cache you should mention in every hibernate mapping file
like <cache usage="read-only"/>

so remove those entry to disable second-level cache for selected element



Amila

(Don't forget to rate if helps)

At the beginning I suspected that working with 2nd-level cache might cause us problems: data won't reflect immediately between 2 application, working against the same DB (Oracle 10g).

But than, after few tests, and re-thinking, the problem exists no matter what kind of caching method I use.

If I create new 2 elements, one from each application, at the same time - the same Id will be supplied to both new created element causing one of them to fail (pk/unique constraint violation).

Meaning, I need to change the Id generation mechanism from general "increment" to "sequence" or any other shared (on physical level) resource.
There is no way to enforce 2 session factories, with 2 sessions to considerate each other - only on DB level (which strongly not supported by Informix 10 sequence)

Am I right? Is that the right way to implement object creation by 2 applications?

Another question raised by the same issue is the consistency when updating the same elements from both applications: I saw an advice to use timestamp or version - could it help to check one object is not occupied by other application? (this case will rarely occur if at all - but it's still interesting)

Thanks a lot,
Moti