To me the real answer is to the programmatic API and add a
programmatic mapping factory to your configuration.
See Example 4.28. Use a mapping factory in
On Thu 2013-06-20 18:22, Guillaume Smet wrote:
We would like to declare our global @AnalyzerDefs on a class which
isn't a specific entity.
For the @TypeDefs of Hibernate, we do it by declaring the @TypeDefs on
a class annotated with @MappedSuperClass but with @AnalyzerDefs, we
are forced to declare them on a concrete @Entity.
Is this an oversight or something due to the way the initialization of
Hibernate Search is done and we cannot change?
I know it's only cosmetic but it's a bit ugly to have a dummy entity
and a dummy table in our core framework just to be able to declare
Thanks for your feedback.
hibernate-dev mailing list