====================== #hibernate-dev Meeting ====================== Meeting started by emmanuel at 17:03:15 UTC. The full logs are available at http://people.redhat.com/~manderse/irc.freenode.org/meetings/hibernate-dev/2011/hibernate-dev.2011-06-27-17.03.log.html . Meeting summary --------------- * @inject (emmanuel, 17:04:54) * ACTION: Support @Inject @QueryBuilder(for=Entity.class, overridesForFields = …) (we can support overridesForFields later) (emmanuel, 17:36:22) * ACTION: support @Inject SearchFactory (multiple PUs won't be supported and will require users to write a qualified producer and write the unwrapping code themselves) (emmanuel, 17:37:24) * ACTION: Sanne checks if Analyzers provided to users via SearchFactory.getAnalyzer() must be closed by the user or not (my guess is not) (emmanuel, 17:46:29) * ACTION: sannegrinovero open a JIRA to close Analyzers at shutdown :) (emmanuel, 17:47:33) * ACTION: Support @Inject @Analyzer (the HSearch annotation) Analyzer analyzer; if @Analyzer has no param set, inject the global analyzer, otherwise inject the requested analyzer (emmanuel, 17:49:20) * ACTION: SearchFactory and QueryBuilder are the most important wrt injectability, the others would be nice to have (emmanuel, 17:54:18) * ACTION: explore the idea of providing CDI Hibernate Search events for backend exceptions, mass indexing end of work etc (emmanuel, 18:10:25) * ACTION: let Filter implementations be managed beans like bridges (emmanuel, 18:12:56) * ACTION: explore further the idea of a declarative fitlter activation / desactivation by annotating managed beans with @Filter and associate @Filter with a CDI interceptor https://gist.github.com/1049434 One possible implementation is to stick the list of activated filters in a thread local context and let Hibernate Search HSQueryImpl read this TL. The implementation details are still a bit unclear (emmanuel, 18:34:18) * ACTION: hardy why is FacetManager an SPI? (emmanuel, 18:38:42) * ACTION: let Hardy think about useful injections wrt faceting. Maybe it would make sense to wait until after we have annotation driven / programmatic configuration for facet definitions (emmanuel, 18:39:26) * on filters => sannegrinovero approach is to have globally enabled filters that are managed beans and get their activation and parameters injected by CDI (from scoped / qualified providers). This is elegant but does it go too far? (emmanuel, 18:46:27) * LINK: https://github.com/LightGuard/seam-example-confbuzz/blob/develop/src/main/java/seam/example/confbuzz/PersistenceProducer.java (lightguard_jp, 18:52:16) * ACTION: lightguard_jp asks on seam-dev where hsearch-cdi should live (brand wise) (emmanuel, 19:03:07) * ACTION: lightguard_jp takes the coordinating lead to get thinks started and delegates at will :) (emmanuel, 19:03:39) Meeting ended at 19:04:26 UTC. Action Items ------------ * Support @Inject @QueryBuilder(for=Entity.class, overridesForFields = …) (we can support overridesForFields later) * support @Inject SearchFactory (multiple PUs won't be supported and will require users to write a qualified producer and write the unwrapping code themselves) * Sanne checks if Analyzers provided to users via SearchFactory.getAnalyzer() must be closed by the user or not (my guess is not) * sannegrinovero open a JIRA to close Analyzers at shutdown :) * Support @Inject @Analyzer (the HSearch annotation) Analyzer analyzer; if @Analyzer has no param set, inject the global analyzer, otherwise inject the requested analyzer * SearchFactory and QueryBuilder are the most important wrt injectability, the others would be nice to have * explore the idea of providing CDI Hibernate Search events for backend exceptions, mass indexing end of work etc * let Filter implementations be managed beans like bridges * explore further the idea of a declarative fitlter activation / desactivation by annotating managed beans with @Filter and associate @Filter with a CDI interceptor https://gist.github.com/1049434 One possible implementation is to stick the list of activated filters in a thread local context and let Hibernate Search HSQueryImpl read this TL. The implementation details are still a bit unclear * hardy why is FacetManager an SPI? * let Hardy think about useful injections wrt faceting. Maybe it would make sense to wait until after we have annotation driven / programmatic configuration for facet definitions * lightguard_jp asks on seam-dev where hsearch-cdi should live (brand wise) * lightguard_jp takes the coordinating lead to get thinks started and delegates at will :) Action Items, by person ----------------------- * lightguard_jp * lightguard_jp asks on seam-dev where hsearch-cdi should live (brand wise) * lightguard_jp takes the coordinating lead to get thinks started and delegates at will :) * sannegrinovero * sannegrinovero open a JIRA to close Analyzers at shutdown :) * **UNASSIGNED** * Support @Inject @QueryBuilder(for=Entity.class, overridesForFields = …) (we can support overridesForFields later) * support @Inject SearchFactory (multiple PUs won't be supported and will require users to write a qualified producer and write the unwrapping code themselves) * Sanne checks if Analyzers provided to users via SearchFactory.getAnalyzer() must be closed by the user or not (my guess is not) * Support @Inject @Analyzer (the HSearch annotation) Analyzer analyzer; if @Analyzer has no param set, inject the global analyzer, otherwise inject the requested analyzer * SearchFactory and QueryBuilder are the most important wrt injectability, the others would be nice to have * explore the idea of providing CDI Hibernate Search events for backend exceptions, mass indexing end of work etc * let Filter implementations be managed beans like bridges * explore further the idea of a declarative fitlter activation / desactivation by annotating managed beans with @Filter and associate @Filter with a CDI interceptor https://gist.github.com/1049434 One possible implementation is to stick the list of activated filters in a thread local context and let Hibernate Search HSQueryImpl read this TL. The implementation details are still a bit unclear * hardy why is FacetManager an SPI? * let Hardy think about useful injections wrt faceting. Maybe it would make sense to wait until after we have annotation driven / programmatic configuration for facet definitions People Present (lines said) --------------------------- * emmanuel (173) * sannegrinovero (76) * lightguard_jp (72) * pmuir (25) * hardy_ (20) * gastaldi (6) * jbott (2) * sebersole (2) * gbadner (1) * jbossbot (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot