On 12 mai 2012, at 11:12, Guillaume Smet wrote: >> That would go counter to the JPA design I think and to be honest, I like the >> idea of being able to not index a given branch of a class hierarchy. >> But more importantly, you would require Hibernate Search to scan for all >> subclasses in the classpath and I don't want to go anywhere near that. > > Having struggled with the new Servlet 3 stuff allowing pure Java > configuration and having Tomcat scan the whole classpath at startup to > find the information, I can get your point as it adds between 10 and > 20 seconds at each startup. > > That said, I'm still not a big fan on maintaining at hand @Indexed > annotations on a branch with a lot of subclasses :).
10-20 seconds? For how many classes in your app ?! Use a real app server man, we worked hard to reduce this time in JBoss AS :) _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
