[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-249?pag... ] Emmanuel Bernard commented on HSEARCH-249: ------------------------------------------ Can you be more specific as for what scenario is not covered. AFAIK Hibernate Search deals with annotations the way we intended it to be but we might have overseen something. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-249?pag... ] Frank Zimmerli commented on HSEARCH-249: ---------------------------------------- The problem came up when using Hibernate Search in an AndroMDA generated environment. Each persistent element has an implementation class (ElementImpl) which is inherited by a generated abstract class (Element). In the hibernate mapping you will find the ElementImpl, but the class variables, which will be indexed in Hibernate Search, can only be found in the generated abstract class. So when you do model changes Element will be overwritten, but ElementImpl will stay in place. In that special case it would be usefull if the Hibernate Search annotations would be declard with @Inherited. I changed the Hibernate Search so far and the index files were generated. I don't know other MDA applications (e.g. openArchitectureWare) and I don't know how they treat changes in the model compared to the already implemented things. Maybe the @Inherited for HSearch could cause problems. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-249?pag... ] Frank Zimmerli commented on HSEARCH-249: ---------------------------------------- The problem is that the class variables are in the abstract class and they are annotated with @Field but the perisistent class is the implementation class of the abstract class. Therefore the @Field should be inherited from the abstract class to the implementation class. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-249?pag... ] Frank Zimmerli commented on HSEARCH-249: ---------------------------------------- I sent you a mail with an example of that subject. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira