I like annotations as much as the next guy but it's a complete non-starter for our business (and, I suspect, plenty of others) to add full text search to our existing apps via Hibernate Search if it means we must convert all our existing hbm.xml configurations into annotations. The regression testing alone would kill us.
The Hibernate project has always been supremely pragmatic which is why I've filed this as a bug rather than a feature request. I don't think Hibernate would have been half as popular if it didn't support things like direct SQL and reverse engineering tools. I think Search would see a big boost if it could be easily added to existing applications.
Please consider adding the needed syntax for xml mapping. At the very least an entry in the FAQ that explains the lacking is needed.
redirect your questions to the Hibernate dev list. firstname.lastname@example.org (you need to be registered)
this is where you will get most feedback.
+1 for this feature. In many cases, you have no control over the object model being stored in the cache, either because it's not your source code, or it's a generated object model. Annotations are all well and java-trendy, but they don't cover every situation. By supporting only the annotation model, all you do is limit the application of the tool.
+1 for this feature. Annotations just arent flexible enough and require the annotations classes to be available, even if the annotations arent used in all cases. For classes that I want to implement on mobile devices this is a problem.
For information, we have a much better solution than XML