Hibernate and ora_rowscn

Question

We are trying to implement optimistic locking through the used of ORA_ROWSCN, and the developers are running into the problem that hibernate is incrementing the ora_rowscn number when updates are done on the row.
Develpers don't see a way to make using ORA_ROWSCN work with the second-level cache. If they could tell Hibernate to invalidate the cache when updates are done instead of put the updated entity directly into the cache, they think they could make it work. Unfortunately they haven't been able to find a way to modify the cache's behavior.
Has anybody run into this problem?
I will appreciate any suggestions on how to make hibernate to work with ora_rowscn.
We are using Spring 2.5.6 with JPA Hibernate Entity Manager 3.3.2 running on Tomcat 6, we are not using OC4J.
We are using Atomikos 2.1.7 for our transaction manager, and here are some of our hibernate settings:
jpa.hibernate.max_fetch_depth=2
jpa.hibernate.default_batch_fetch_size=16
jpa.hibernate.order_updates=true
jpa.hibernate.connection.isolation=4
jpa.hibernate.generate_statistics=true
jpa.hibernate.jdbc.use_get_generated_keys=false
jpa.hibernate.jdbc.fetch_size=0
jpa.hibernate.jdbc.batch_size=30
jpa.hibernate.connection.release_mode=after_statement
jpa.hibernate.default_schema=
jpa.hibernate.strict_jpaql=true
jpa.hibernate.cache.use_second_level_cache=true
jpa.hibernate.cache.use_query_cache=true
Thanks in advance for any help on this.

Answer 1

thanks for your reply.
We are already doing that, but even with that setting we still have the problem and we cannot get hibernate to not increment the ora_rowscn.
This is what we have in our code.
@Version
@Column(name = "ORA_ROWSCN", insertable = false, updatable = false)
@org.hibernate.annotations.Generated(GenerationTime.ALWAYS)
private Long version;
Did anybody run into this problem with hibernate using ora_rowscn?
Any help will be greatly appreciated.
Thanks