[hibernate-dev] [HSEARCH] [Autodiscoverable] Implementation of the service loader based discovery

Emmanuel Bernard emmanuel at hibernate.org
Wed Apr 2 11:02:02 EDT 2014


https://hibernate.atlassian.net/browse/HSEARCH-1581

On 01 Apr 2014, at 22:24, Hardy Ferentschik <hardy at hibernate.org> wrote:

> 
> On 1 Jan 2014, at 16:36, Emmanuel Bernard <emmanuel at hibernate.org> wrote:
> 
>> ## Implementation of the service loader based discovery
>> 
>> Hardy proposes to make each BridgeProvider a Service in the ServiceManager sense.
> 
> It is right? We allow users to provide their implementations. 
> 
>> The idea being that when we make a compatible ServiceManager OSGi wise, it will also make a compatible bridge provider discoverer.
> 
> That’s a nice side effect imo. Depending on far you want to go with OSGi, you probably want to skip at some stage Java’s ServiceLoader
> and do service lookups via OSGi mechanism. Doing Java service loading all via our ServiceManager ensures that we just have one (pluggable)
> spot in case we want to down the OSGi service route.
> 
>> It looks fine to me but as Hardy pointed out, we would need to make the ServiceManager accept several implementations per Service.
>> I’d like to separate the bridge auto-discoverability feature from that ServiceManager improvement to stay focused.
>> We can converge the service discovery as soon as the SM gains the right capability.
> 
> Do you have a separate issue for the SessionManager enhancements? 
> 
> —Hardy
> 




More information about the hibernate-dev mailing list