I need to map a view in the DB to a Hibernate object. Everything seems as straightforward as mapping a normal table. However I want to prevent updates to this Bean class.

The attribute "usage=read-only" talks about caches. There seems to nothing at the property level of the Bean that says read-only.

All my bean access is though a Session facade. But I wish I can set up a guard against updates so that future programmers or API users would be stopped from trying it by accident.

Not a show stopper but some thoughts would be useful. Many thanks.


Cheers
-raj

from docs:



and to totally prevent inserts, i don't think we have other means than install an interceptor and let it complain if certain classes are being passed to it.

Name the persistent class something like ImmutableFooBar and don't expose any setters on it. If future programmers in your organization don't get the hint, I think it's a lost cause. ;-)

Of course, you must also then map the columns directly to object fields instead of property setters.

Aah, that was the bit I was missing. I did try removing the setters but got error with my ear loaded into JBoss.

Of course, that still leaves the problem of inserts which has to be handled by intercepting the call to the Bean as stated above. Any implementation example anywhere?

Cheers
-raj

Another approach: If the ID field has a not-null constraint, you could map it to an "assigned" ID generator in Hibernate. Since there's no way for code to set the ID, any attempt to insert a new row should generate a constraint violation.

Haven't tried this myself, but can't think of a reason it won't work.