On 2 Jan 2014, at 12:10, Emmanuel Bernard <emmanuel(a)hibernate.org> wrote:
I don’t think copying these 15 or 30 field bridges implementations is
really a good thing. In the end, we will have to support them anyways in JDG if the
problem is not solved at the root instead of shifted to the next lib.
My understanding was that only a couple of bridges are referenced directly. Should in the
most common case our bridge discovery work?
—Hardy
On 01 Apr 2014, at 22:02, Hardy Ferentschik
<hardy(a)hibernate.org> wrote:
>
> On 1 Jan 2014, at 16:36, Emmanuel Bernard <emmanuel(a)hibernate.org> wrote:
>
>> ## References to field bridges
>>
>> Despite being on an internal class, some implementations (Infinispan remove query
at least) uses direct references to FieldBridge.SOME_BRIDGE.
>
> IMO, they should not. There is a unnecessary coupling here. Easiest way for
Infinispan is to use their own bridge
>
>> I’ll reinstate them so that Sanne could integrate continuously HSearch 5 with
Infinispan.
>
> What does reinstate mean for Search 5 mean? For the next Alpha release, until Beta or
even for Final.
>
>> I would prefer to see them go
>
> +1 I would do it as part of this work. I don’t see a point in keeping them
>
> —Hardy