Hi All,

My question is should I be able to use hibernate.mapping.precedence to resolve duplication of query names? According to the documentation "hibernate.mapping.precedence" is used to resolve conflicts between annotated classes and hbm files. But what about named queries?

I am using annotated classes to define the mappings and named queries - using only JPA annotations.

I have experimented with overriding named queries defined in hbm files and using hibernate extenstions (e.g. caching) in the hbm files.

I was hoping to be able to avoid Duplicate Query errors by specifying This does not work. Hibernate complains with DuplicateMappingException.

Would it make sense to extend hibernate.mapping.precedence to resolve conflicts with Named Queries?

Thanks!

It might not be very easy, but if someone come up with a patch, why not.