"vyemialyanchyk" wrote : anonymous wrote : What do you mean by "automatic"? | here I mean something like "Generate Hibernate/JPA annotations" in Hibernate Tools. Of cause it is rather difficult to define correct places for the Field annotation - here I propose generate it only for Strings fields as a first step. | I very deliberately haven't added any automatic code generation that is non-deterministic/dangerous to hibernate tools so let's not start doing that ;) You could do something like use meta attributes that hibernate tools support to annotate which things you want to be searched and users can then either use reveng.xml to indicate which fields needs indexing or use a programmatic strategy to compute it. So if the generation is pretty simplistic (i.e. nothing fancy) then it could be integrated into reverse engineering/code generation but not sure if its really useful/will be used. anonymous wrote : | anonymous wrote : you refer to an interface update to the luke tools? what's wrong with being tightly coupled to Lucene for a tool like this? | that is right. Luke is a good tool exactly for Lucene, Lucene is a good index search tool, but there are several other and if they will get a common switch in common interface, the developers could select the best index search tool for their needs. As I think this will not add too much complexity, but will give a real flexibility like Hibernate has with plenty DBMS. | What other good index search tools are there and why should we generalize them ? Hibernate only support many db's because the db's has a common language (SQL, tables, rows, columns,..). Index search tools doesn't afaik...and again - why not just focus on Lucene ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203260#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...