As suggested, changed the log from "hibernate.transaction.manager_lookup_class" to "hibernate.transaction.jta.platform".

There was some incorrect logic around the logging call that effectively caused it to occur even when the JTA platform was set. That's been corrected. However, there's not really an easy way to determine if all forms of caching are disabled, at least from JtaTransaction. So, for now, if hibernate.transaction.jta.platform (and other related properties) are set, the log shouldn't happen.

If anyone sees it erroneously occur (after 4.2.8-SNAPSHOT is built, shortly), please upload a test case