Yeah. I wanted to have an EhcacheIntegratorService registered, that would, during the integrate call, do the potential mapping from old to new name (so this would be able to use ....class.getName()). Also, I could keep a ref to the ServiceRegistry, so I'd be able to address any classloader concerns you mentioned. Not sure what that would give wrt to the hack on getting the RegionFactory in org.hibernate.cfg.SettingsFactory.createRegionFactory But anyways, I don't really see how to plug that integrator in... So that seems like the wrong path.
On Thu, Jul 14, 2011 at 3:18 AM, Strong Liu <st...@hibernate.org> wrote: > > > On Jul 14, 2011, at 4:57 AM, Steve Ebersole wrote: > >> Or do you mean java.util.ServiceLoader ? > > yes, i think Alex means this >> >> On Wed 13 Jul 2011 03:54:16 PM CDT, Steve Ebersole wrote: >>> On 07/13/2011 09:46 AM, Strong Liu wrote: >>>> On Jul 11, 2011, at 10:48 PM, Alex Snaps wrote: >>>> >>>> a warning >>>>> - Second level cache isn't (yet?) using "ServiceInitiator approach", >>>>> is this going to change ? >>>> >>>> I don't pre-see it, Steve? >>>>> - Right now the mapping plan is "weak" in terms of typing since core >>>>> doesn't know anything about hibernate-ehcache. I guess, if second >>>>> level caching also goes the ServiceInitiator path, that will change, >>>>> right ? >>> org.hibernate.cache.internal.RegionFactoryInitiator >> >> -- >> st...@hibernate.org >> http://hibernate.org > > -- Alex Snaps <alex.sn...@gmail.com> Senior Software Engineer - Terracotta http://twitter.com/alexsnaps http://www.linkedin.com/in/alexsnaps _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
