|
[
Permalink
| « Hide
]
Sanne Grinovero added a comment - 10/Jun/08 05:27 AM
I agree it would be an improvement, but you should be able to annotate your entities with Search specific annotations and keep the rest of hibernate's configuration in xml.
Sanne is correct, you don't need to convert your existing mapping into annotations to benefit from Hibernate Search
You just need to use the HSearch annotations. I think I give an example in Hibernate Search in Action. You can also check http://hibernate.org/443.html. I changed the bug into new feature I would really like this feature. Could you direct me to your project's guidelines/resources for contributing code? I may decide to implement this.
Cool
There is no strong guideline Here is how to get the source and compile the project http://hibernate.org/6.html#A4 Excellent. If I have questions concerning the implementation, is there a point of contact? I may have questions for the contributors of the code that creates the attributes from the mapping file. (org.hibernate.cfg.annotations.reflection). If I get a working implementation, I plan to contribute it. Anyone that has already made some progress on this feature (or has useful tips) may contact me isaacwhanson@gmail.com
redirect your questions to the Hibernate dev list. hibernate-dev@lists.jboss.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.
|
||||||||||||||||||||||||||||||||||||||||||||||