[hibernate-issues] [Hibernate-JIRA] Issue Comment Edited: (HSEARCH-904) Have TwoWayFieldBridge report which fields should be loaded from a Document

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-904?pag... ] Hardy Ferentschik edited comment on HSEARCH-904 at 9/9/11 10:07 AM: -------------------------------------------------------------------- The last discussed solution was to create a new interface a bridge can optionally implement (similar to _ParameterizedBridge_) - _FieldNameReportingBridge_: {code} public interface FieldNameReportingBridge { Iterable<String> getGeneratedFieldNames(); } {code} Maybe we should introduce a wrapper object though to be able to not only return the names, but also analyzer names (see HSEARCH-664). To properly support this though the bridge implementation needs to know the property name to which the bridge applies. For this reason it makes sense to make bridges stateful and add an _initalize_ method which takes the field name (property name in most cases) and the _LuceneOptions_. These two parameters could then be removed from the _set_ method of _FieldBridge_ simplifying the API. The drawback of making the bridges stateful is a increased memory footprint (see above email thread) was (Author: hardy.ferentschik): The last discussed solution was to create a new interface a bridge can optionally implement (similar to _ParameterizedBridge_) - _FieldNameReportingBridge_: {code} public interface FieldNameReportingBridge { Iterable<String> getGeneratedFieldNames(); } {code} Maybe we should introduce a wrapper object though to be able to not only return the names, but also analyzer names (see HSEARCH-664). To properly support this though the bridge implementation needs to know the property name to which the bridge applies. For this reason it makes sense to make bridges stateful and add an _initalize_ method which takes the field name (property name in most cases) and the _LuceneOptions_. These two parameters could then be removed from the _set_ method of _FieldBridge_ simplifying the API. The drawback of making the bridges stateful is a increased memory footprint. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira