I have an immutable domain object, with no setter mettods for primary key values and no default construtor.
How can I define my mapping file with in Hibernate?
There are 2 ways I can do preserve immutable domain object with Hibernate
1. Making the access level to "field" instead of property and define the fields private. Also make the default constructor private
2. Making the setter methods private and def constructor private.

Are these the best ways to handle this?
I am planning to implement using option 1. Is it a good practice to make the access level "field"

Thanks
J

On the class mapping definition, you can set the mutable property to false. e.g. <class name="eg.model.Person" table="PERSON" mutable="false">

http://www.hibernate.org/hib_docs/v3/re ... tion-class

But what will happen when the object is made transient or detached. If I service layer is using this object, and if I have public setter methods, they can still modify the object.

I do not think mutable="false" solves the problem

Thanks
J

Mutable="false" will just ensure that Hibernate won't persist any changes to the object...never a bad idea, just in case you use bytecode instrumentation or some other framework bypasses the scopes. If you want to make your setters private, Hibernate won't care, it will still be able to set the properties. That way no other process can change the field values.


And

And

Thanks for you reply.

I am not concerned with persisting Domain Object. I am more concerned with this immutable domain object being modified because of these public setters methods.

The only way I can get around the problem is by making access to private scope.

I just wanted to know whether cause any problem ?

Should not cause any problems for Hibernate if you use private setters.