Hello,
we're evaluating a migration from DataNucleus to Hibernate.

We're using bytecode enhancement and deny use of setters on persistent objects whilst outside of an transaction. In DataNucleus this is performed by setting the property "datanucleus.NontransactionalWrite" to false in the persistence.xml. In case of using a setter outside a transaction an exception is thrown.

However, I did not find any similar in Hibernate, is this behaviour possible?

Best Regards

In Hibernate, there is no such equivalent. However, you can't execute any modifications outside a transaction. This is prohibited by JPA. Therefore, you should be fine.

Well, I'm aware that the modification to the object is not written to the datastore whilst outside a transaction, but the object can be modified and on next call to save() all changes - even these made outside the transactions - are written to the datastore.

I suppose you mean saveOrUpdate() or merge(). Calling save() on a detached entity is the same like calling persist() on a non-transient entity, it just results in an exception being thrown.

There is no such feature, but you can add an improvement issue to our Jira.