Hi,

We started using Hibernate Search on our project two years ago. It seemed to be a good fit for our needs at the time. The more complex our domain got and the more complex our search needs became ... the less fit this choice seem. I might be wrong however. Hence this post.

My biggest concern is that our main entity (the indexed one) now has alot (really) of methods which are only there to provide special data (agreagations, denormalizations etc.) to the index at index-time. They do not serve any real purpose in the domain. This of course bothers me.

Here is a question which might reveal if I have missed something fundamental:
Can I somehow associate a factory class (or some kind of decorator) with the indexed entity which in turn can hold all index-taylored methods so I can get clean entities again.

Hope this made any sense and you get what I mean.

Tobias

Why not using a ClassBridge?
It's cool you can add to the index with some annotations, if the code is growing uncontrolled to have special indexing needs, I agree you should move it out.