[hibernate-issues] [Hibernate-JIRA] Updated: (HSEARCH-372) ClassBridges are not handled in projection

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-372?pag... ] Emmanuel Bernard updated HSEARCH-372: ------------------------------------- Fix Version/s: (was: 3.1.1) 3.2.0 Issue Type: New Feature (was: Bug) I've analyzed the code a bit. I think I did not activate this feature because in most ClassBridge, we don't know which field name is used. This could work however: - if the user explicitly adds a name() to the @ClassBridge - and the bridge impl does not mess around and use the field name straight I am contemplating the idea of adding an interface implemented by bridges and declaring which field is used (I dont' think I like the idea very much though as field names could be dynamic), or simply a flag declaring the bridge as a good citizen to increase error discovery. I am not willing to rush an impl of this new feature (with or wo interface) in a micro release but we can help you implement it (see below the key parts that needs enhancement to make it work). Implementation: - DocumentBuilderIndexedEntity.checkAllowFieldSelection does nto take classBridge into account - DocumentBuilderIndexedEntity.processFieldsForProjection does nto take class bridges into account Side note: - DocumentBuilderIndexedEntity.checkAllowFieldSelection does not take embeddedBridges into account, it probably should but we could have some circularity issue? -- 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