Recently our team switched from Entity Manager 3.2.0.cr2 to 3.2.1.ga and discovered that strict JPA-QL compliance is no longer enforced (on a query such as "FROM Entity"). I've seen the issue in JIRA (http://opensource.atlassian.com/projects/hibernate/browse/HHH-2103) which says that it was rolled back, but I'm wondering why? We want to force our developers to use JPA QL and discourage them from using HQL. This used to work by specifying the "hibernate.query.jpaql_strict_compliance" property in persistence.xml, but now it doesn't work. So, I'm wondering if this is a bug or an intention. If need be I can provide a test project to demonstrate the problem. Thanks.

We lobbied Sun to get rid of the TCK test triggering a failure. The spec and the TCK were not intended to limit natural product extensions.