This belongs in the persistence module, we need to coordinate with Stuart and Emmanuel to determine how we get it in there (I don't think it will be much work). Shane On 28/06/11 05:19, Jason Porter wrote:

IMHO, it makes more sense to belong to Hibernate Search than in the Persistence Module WDYT ? 2011/6/27 Jason Porter <lightguard.jp(a)gmail.com&gt;

As Jason mentioned, after he posted this I chatted with Sanne and Emmanuel about where this belongs and indicated it should belong in Hibernate Search. Let me elaborate here :-) In general, the mission of Seam is to make Java EE a kick-arse development platform. It can do this in a number of ways: (1) By prototyping extensions to existing specs. Examples: * the work John is doing in Seam JMS and in the JMS 2 EG * some of the stuff in Solder that George is writing up for CDI 1.1 * some of the work done in Seam Faces that may be added to JSF * some of the work in Seam Cron that could be standardized as part of the timer services EE offers (this is a longer term possibiltiy) * Seam config is providing inspiration for discussions on improved config for Java EE 7 (2) By providing CDI support for projects that are of interest but don't want to take CDI support directly right now. Examples might be: * Seam Reports (3) By assisting other projects with developing built in CDI support. Examples are: * Infinispan * Drools * JClouds * Errai (1) is a great role for Seam to fulfil. Some of the ideas might even become their own spec in the future, such as Catch or International. (2) and (3) are really the flip-side of each other. In general (3) is a much stronger option. Why? * The project team has domain knowledge and so understands much better what will work, and the use cases their users want to address * It expands the reach of CDI and the Java EE platform to the users of that project * CDI and Solder have been designed as backwards compatible APIs, therefore integrating this way around makes a lot of sense, as the project can depend on a stable API and not get into dependency issues * CDI has a comprehensive specification backing it, making learning it and it's rules simpler than the Seam project learning the quirks of another library However, one issue with this approach is that it de-centralizes the platform somewhat. To combat that, Seam should include documentation and examples (as it does for Errai) about using that other project with Seam/CDI. So IMO we should always try to follow (3) and only do (2) when we can't manage (3). In this case the Hibernate Search team is definitely happy to take the support so that is the way we should go. On 27 Jun 2011, at 22:40, George Gastaldi wrote:

My recommendation, based on what I've seen is that it belongs in hibernate search. Seems to be in line with what EG's are doing for CDI integration in their specs. John On Mon, Jun 27, 2011 at 5:50 PM, Shane Bryzak <sbryzak(a)redhat.com&gt; wrote: