[hibernate-dev] [Search] Why is global @AnalyzerDefs scanning limited to @Entity?

Guillaume Smet guillaume.smet at gmail.com
Thu Jun 20 12:22:59 EDT 2013


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
global @AnalyzerDefs.

Thanks for your feedback.


More information about the hibernate-dev mailing list