Hi, I'm a J2EE developer with experience using entity beans, but I'm new to Hibernate and have one question. With entity beans, I often rely on method locking and transaction locking to ensure "synchronized" behavior:

Method Locking

Method locking ensures that only one thread of execution at a time can invoke on a given Entity Bean.

Transaction Locking

Transaction locking ensures that only one transaction at a time has access to a given Entity Bean. This means that if any method at all is invoked on an Entity Bean within a transaction, no other transaction can have access to this bean until the holding transaction commits or is rolled back.

Does Hibernate support any similar behavior, without having to resort to synchronized code blocks that violate EJB programming restrictions?

Hibernate implements the instance-per-transaction model (actually instance-per-session) which is similar to EJB commit option C, except that Hibernate also features a second-level cache which gives you the main advantages of commit option A.

This architecture is designed for extremely high scalability via minimal resource contention.