In my view, such refactoring will make cache configuration very hard to use. My preference would be to leave it as is and wait for more user feedback.
On Tue, May 12, 2015 at 1:21 PM, Yakov Zhdanov <[email protected]> wrote: > I think this is a very good point. Val, please file a ticket. > > --Yakov > > 2015-05-09 3:45 GMT+03:00 Valentin Kulichenko < > [email protected] > >: > > > Guys, > > > > I noticed that some entities on cache configuration are configured via > > factories, while others are set directly. For example, we use factory for > > ExpiryPolicy, but not for EvictionPolicy, which looks inconsistent. Since > > factory-based approach comes from JCache, I think we should use it > wherever > > possible. > > > > Here is the list of settings that need to be fixed (I checked only cache > > config): > > > > - Affinity > > - AffinityMapper > > - EvictionFilter > > - EvictionPolicy > > - CacheInterceptor > > - TopologyValidator > > > > Agree? > > > > -- > > Val > > >
