hello,
I am running Oracle 8.1.7, Hibernate 3.0 and Middlegen from CVS with version="3.0" attribute in the hibernate sub-task in ant.

In the Middlegen GUI, I uncheck the mutable checkbox. Middlegen produces the following mapping:


But even though mutable is set to false, hbm2java generates setters for my POJOs.
I found a workaround in another thread (http://forum.hibernate.org/viewtopic.php?t=948288), which says that <meta attribute="scope-set">private</meta> should do the thing. This is ok, but I wonder why Middlegen is producing mutable=false, when it doesn't really have an impact!? Is there any way to use Middlegen and still end up with unmutable POJOs in the end?

cheers,
pj

The mutable attribute affects hibernates' behaviour not the code generators. As you discovered, the scope meta data [as all the meta data attributes] affects the generators behaviour.

it has an effect on how hibernate treats the objects.

we could probably change the default scope for a non mutable property to private (protected?) for its setters.

add a jira for it