Hi all guys, I've been doing some experiment using the last beta of iBatis 3 and I've the feeling you happily fixed the inglorious IBATIS-555 issue about the CacheKey unique hashcode generation on different JVMs :)
Now I've been porting my old stuff to the new iBatis implementation and everything has worked fine until I plugged-in the cache, I really hope you can help me to understand where I'm wrong: I implemented a Memcached-based Cache class, wrapping the spy memcached client (code.google.com/p/spymemcached/), injecting a singleton instance to the Configuration programmatically using google-guice 2 and finally referenced in the sql-map via the snippet: <cache-ref namespace="memcached"/> What I noticed, reading the logs, is the following: * when flushing the statements defined in the sql map, is called the method org.apache.ibatis.cache.Cache#clear(): that makes me a little worried, because in a memcached context I ideally want to use just one memcached client instance and reference it in the whole application, when performing an insert operation I wouldn't flush the whole cache, but rather remove only the interested statements; since I'm still used to the old iBatis2 cache model, how can I fix it? * no data is cached, the method org.apache.ibatis.cache.Cache#putObject(Object,Object) is never called; All the code I've been producing is public, you can find it on google-code[1], and on the test directory you can find the scenario[2] I described Thanks in advance for your help, any kind of suggestion will be very appreciated!!! Simone [1] http://code.google.com/p/ibaguice/source/browse/#svn/trunk [2] http://code.google.com/p/ibaguice/source/browse/trunk/src/test/java/com/ibaguice/SimpleTestCase.java -- http://www.google.com/profiles/simone.tripodi --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@ibatis.apache.org For additional commands, e-mail: dev-h...@ibatis.apache.org
