Re: [hibernate-dev] Various expectation changes in hibernate-core after consolidating hibernate-entitymanager

Well we'll agree to disagree about the validity of allowing queries outside the scope of a transaction; it does not matter, because JPA says it should be allowed, so we have to allow that. However, historically Hibernate allowed writes outside the scope of a transaction as well (auto-commit support), so that is what I am talking about. After pulling over HEM logic we now have some test failures due to tests trying to write data outside of an explicit transaction ( javax.persistence.TransactionRequiredException). So I propose we continue to expect that as a failure starting in 5.2. For queries we will continue to supports it, but only because JPA requires us to; not because it is a valid concept. Why? This is exactly the kind of thing I have in mind when I talk about the unnecessary complexity. Clearly asking if the Session contains a boolean e.g. is complete non-sense. If JPA requires that condition to throw an exception, why even worry about the other case? Well that's great in principle. But JPA actually requires an exception be thrown when #getTransaction() is called in the JTA case. So there is no simple "just allow it as an extension" solution, we'd have to specific allow users to opt-in to allowing that.