I'm having a look at the imported code, the DirectMemoryCache<K, V> is just a
new CacheServiceImpl<K, V>( ew MemoryManagerServiceWithAllocationPolicyEhcacheImpl<V>( new RoundRobinAllocationPolicy<V>() ) ); adapter. I suppose Michael added DirectMemoryCache<K, V> to turn around the absence of generics support, otherwise I don'd see the benefit of having yet another CacheService<K, V> wrapper. thoughts? TIA, -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Sat, Feb 25, 2012 at 11:07 PM, Simone Tripodi <[email protected]> wrote: > Sorry, I don't understand how it is related to declaring a package in > the SVN repo that's not org.apache.* > > Thanks anyway, having 3rd parties dependencies that adhere to ASL2.0 > simplifies the release process. > > bets, > -Simo > > http://people.apache.org/~simonetripodi/ > http://simonetripodi.livejournal.com/ > http://twitter.com/simonetripodi > http://www.99soft.org/ > > > > On Sat, Feb 25, 2012 at 7:58 PM, Michael André Pearce > <[email protected]> wrote: >> http://ehcache.org/apidocs/ >> >> See point 14, code is released under apache license already and approved by >> asf. >> >> Sent from my iPhone >> >> On 25 Feb 2012, at 15:35, Simone Tripodi <[email protected]> wrote: >> >>> Salut Benoit! >>> >>>> But, EHCache is done in a way that net.sf.ehcache.Cache is looking for >>>> the class net.sf.ehcache.store.offheap.OffHeapStore >>>> (http://ehcache.org/xref/net/sf/ehcache/Cache.html#1181). >>> >>> Ouch :( :( Cannot believe they didn't adopt a SPI-alike approach :( >>> >>> Looks like we don't have any chance to change/hack that behavior, so >>> we can just understand how to having it fixed under the legal PoV. >>> >>> Thanks for the clarification, very appreciated! >>> >>> -Simo >>> >>> http://people.apache.org/~simonetripodi/ >>> http://simonetripodi.livejournal.com/ >>> http://twitter.com/simonetripodi >>> http://www.99soft.org/
