I have an annotation for the fields used in generating a key's hash code (used for complex keys and collocation of data). Erik From: infinispan-dev-bounces(a)lists.jboss.org [mailto:infinispan-dev-bounces@lists.jboss.org] On Behalf Of Manik Surtani Sent: Thursday, March 17, 2011 6:56 AM To: infinispan -Dev List Subject: [infinispan-dev] Annotations In some ways related to the @Marshallable annotation thread, but in many ways not, I was having a look at: http://code.google.com/p/ehcache-spring-annotations/ I think we need to do something in this space, to make life easier for developers to consume distributed caches. As such, what I'm thinking of is: * Spring annotations for Infinispan - Olaf, will we get this for free with your work on the Spring cache adapter for Infinispan? If so, we should talk about this (blog, wiki, etc) * SEAM annotations. Pete did a POC some while back, maybe we need to formalise this? Other thoughts? Cheers Manik -- Manik Surtani manik@jboss.org<mailto:manik@jboss.org> twitter.com/maniksurtani<http://twitter.com/maniksurtani> Lead, Infinispan http://www.infinispan.org ________________________________ The information contained in this message is legally privileged and confidential, and is intended for the individual or entity to whom it is addressed (or their designee). If this message is read by anyone other than the intended recipient, please be advised that distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete or destroy all copies of this message.

On 18 Mar 2011, at 16:08, Pete Muir wrote: Do you have a JIRA for this on SEAM which we can track? Cheers Manik -- Manik Surtani manik(a)jboss.org twitter.com/maniksurtani Lead, Infinispan http://www.infinispan.org

Am 17.03.11 11:55, schrieb Manik Surtani: This is my current understanding of how Spring Cache is supposed to work. The way I see it is that org.springframework.cache.Cache and org.springframework.cache.CacheManager form an SPI that may be implemented by different cache providers. A user tells Spring via his application context which cache provider to use and Spring will merrily delegate all crosscutting caching concerns as defined through its caching annotations to that cache provider. Regarding the suggestion to talk about this I have added a comment to that effect to ISPN-961 lest I forget about it.