[hibernate-dev] API changes in FieldBridge

Hardy Ferentschik hardy at hibernate.org
Wed Sep 7 08:25:14 EDT 2011


On Wed, 07 Sep 2011 13:27:17 +0200, Sanne Grinovero <sanne at hibernate.org>  
wrote:

>>
>> OK, got it.
>> The absence of this TargetedFields (or whatever name we could give it)  
>> interface would be equivalent to allowSkipOnUnchangedField = false for  
>> a bridge. Likewise for DynamicBoost and DynamicAnalyzer.
>> Of course an additional interface is less in your face than an explicit  
>> method on the existing interfaces.
>
> I'm fully aligned. That looks like the best approach, but I don't like
> it much to deal with complex hierarchies of interfaces

It is not really a hierarchy. It is just an additional interface a bridge
can implement. Think of Scala traits. There almost everything is its own
interface (for good and for bad)
And yes, I am not a big fan of deep hierarchies either.

--Hardy



More information about the hibernate-dev mailing list