EntityQuery.resultCount throws a exception when the entity has composite key

Invoking EntityQuery.resultCount() resulted in a query such as <code>select count( entity )...</code>. However, if the persistence provider is Hibernate and the Entity has a composite key, the exception <code>[ERROR JDBCExceptionReporter] Operand should contain 1 column(s)</code> is triggered, because Hibernate does not support composite keys in <code>count</code> queries. This constraint prevented you from using seam-gen and JBoss Developer Studio to generate CRUDs if you had Entities with composite keys and you use Hibernate. Hibernate extensively uses <code>EntityQuery.resultCount()</code> in the generated code, and this class triggered the exception. Seam has been updated, so that if the persistence provider is Hibernate, Seam builds the query using the notation <code>select count( * )</code> instead of <code>select count ( entity )</code>. This method works, even with composite keys. With this fix in place, <code>EntityQuery.resultCount()</code> works for all entities and all persistence providers, as do generated CRUDs.