Hi Hardy! because it's the key for the static weakhashmap for the autoregistration of listeners, that would introduce a memory leak. I had proposed to care for registration of listeners in other ways, don't have the reference now from the phone (I'd +1 to remove the static weakhashmap)
cheers, Sanne Il giorno 09/lug/2010 18:47, "Hardy Ferentschik" <hibern...@ferentschik.de> ha scritto: Hi, just wondering whether there is a reason why we don't expose the configuration properties in SearchFactory? I think we talked about this once, but I cannot remember exactly. I noticed that the properties are now exposed in StateSearchFactoryImplementor anyways. Maybe we could push this all the way down to SearchFactory? I need would need access to the properties and several places to for example check for hibernate.search.generate_statistics or "hibernate.search.jmx_enabled. While looking at the code I also started to wonder whether we need all these sub-interfaces for SearchFactory. Currently we have SearchFactory -> SearchFactoryIntegrator -> SearchFactoryImplementor -> StateSearchFactoryImplementor -> Mutable-/Immutable-SearchFactory Is this really all needed? --Hardy _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
