This is part of my cashing change branch if you all wanted to take a look
On Thu, Mar 22, 2018, 7:57 AM Chris Cranford wrote:
> +1
>
> Makes sense to me.
>
>
> On 03/21/2018 02:42 PM, Steve Ebersole wrote:
>
> Thoughts on allowing certain services to be defaulted to the single
> implementor regi
+1
Makes sense to me.
On 03/21/2018 02:42 PM, Steve Ebersole wrote:
> Thoughts on allowing certain services to be defaulted to the single
> implementor registered with the `StrategySelector` service when there is
> just one?
>
> For example, when resolving the RegionFactory unless both (a)
> `hib
On 21 March 2018 at 19:15, Vlad Mihalcea wrote:
>
> Sounds good to me.
+1 nice
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Sounds good to me.
Vlad
On Wed, 21 Mar 2018, 20:48 Steve Ebersole, wrote:
> Thoughts on allowing certain services to be defaulted to the single
> implementor registered with the `StrategySelector` service when there is
> just one?
>
> For example, when resolving the RegionFactory unless both (a
Thoughts on allowing certain services to be defaulted to the single
implementor registered with the `StrategySelector` service when there is
just one?
For example, when resolving the RegionFactory unless both (a)
`hibernate.cache.region.factory_class` and (b) one of
`hibernate.cache.use_second_lev
