A question about Lucene module objectives

[puccio]

Hi,
I read a bit of the documentation of the springmodules 0.3 lucene integration (the html little tutorial and some javadoc), and from what I see it is a nice set of APIs for integrating Lucene low level APIs in the spirit of the Spring framework.

What I can't find out is if this module's objectives could be to provide high level APIs functionalities for indexing domain objects and searching over the lucene indeces to get back them as result (something like the Compass Framework).

I am asking this because in a project I am working on we used Spring + Hibernate with hibernate lucene integration for keeping the Lucene index and the database in sync with no code at all apart some annotations for the objects properties we wanted to store in lucene fields.

Then we built a little abstraction over the Lucene multi searcher to retrieve lucene Documents and map them back to the actual domain objects through the id field and a "type" field. It works quite good but obviously is wired to Hibernate.

So in the end, I just wanted to know which are the directions of this module and how it now compares to Compass and which direction will it take :-)

Thanks in advance

[Costin Leau]

Try posting the question on the Spring Modules mailing list also. Thierry Templier, the module maintainer might answer this question in detail. I personally, have chosen SM Lucene support in the past since it was very easy to integrate and very lightweight. I haven't used compass that much but it seems to have be more or less a blackbox and I wanted complete control over the indexing process as well as how objects are indexed.
Basically, I had to work a lot with Lucene and SM Lucene support provided everything I needed.