[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-160?pag... ] Emmanuel Bernard updated HSEARCH-160: ------------------------------------- Fix Version/s: (was: 3.1.0.Beta1) 3.1.0 -- 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-160?pag... ] Hardy Ferentschik commented on HSEARCH-160: ------------------------------------------- The idea for solving this issue is: * build some kind of "superclass" tree at init time - Map<Class<?>, List<Class<?>> * at query time compared the targeted classes to this tree/list, eg if targeted class is Object all indexed entities are targeted since Object is a superclass of all entities. If for example the targeted class is Serializable only the ndexed entities which implement Serializable are returned Caveat: Do not add subclasses in result list if eg the targeted class is Serializable and Person is for example superclass of Customer. Or think about the case one class implements Serializable and the other Auditable and the query includes both interfaces. Check MultiQueryLoader. It contains similar code. -- 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