Hibernate version: 3.2.6.ga via hibernate-entitymanager (JPA) using maven2

I have some entities that I consider to be read-only. They are JPA entities and ALL columns have insertable=false, updatable=false. However, the queries have to run inside of a transaction.

Is there any further way to ensure that the entities are not converted for management since I won't be updating them, but cannot operate outside of a transaction?

Can entities reside in the Hibernate first-tier cache as read-only if hibernate is dis-allowed from doing the extra work that is done to manage updatable entities?

Thanks.

If you are loading the entities with a HQL query you can call Query.setReadOnly(true) before executing the query. Unfortunately there seems to be no method with the same functionality for Criteria queries.

We are trying to stick with coding against neutral JPA. and unfortunately neither javax.persistence.Query nor JPA named queries expose this property.

Ok. Another option is to mark the class with mutable="false", but I think that is also a Hibernate extension.

Actually, that is a better option. Annotations are used in one place (per entity), so it's easier to manage the migration away from hibernate specifics in this case. I'll see how far that gets me. Thanks!