<p><br>
On 17 Mar 2011 10:55, "Mircea Markus" <<a href="mailto:mircea.markus@jboss.com">mircea.markus@jboss.com</a>> wrote:<br>
><br>
><br>
> On 17 Mar 2011, at 10:22, Sanne Grinovero wrote:<br>
><br>
> > I think we could suggest many improvements, but if it's not in this<br>
> > specific existing API<br>
> Which API do you have in mind?<br>
> org.infinispan.client.hotrod.RemoteCache/RemoteCacheManager ?</p>
<p>The subject of this thread: Spring cache API ;)</p>
<p>> > then people won't use it (at least via Spring's<br>
> > integration)<br>
> ><br>
> > Il giorno mercoledì 16 marzo 2011, Mircea Markus<br>
> > <<a href="mailto:mircea.markus@jboss.com">mircea.markus@jboss.com</a>> ha scritto:<br>
> >> This method can return more than cache names, some info about status would be helpful as well.<br>
> >> E.g. verb to return all the cache names together with a status indicator: defined, running, stopped.<br>
> >> On 16 Mar 2011, at 08:06, Galder Zamarreño wrote:<br>
> >><br>
> >>> Olaf, you're current method won't work since it will only give you the cache names of the caches being interacted with by that client. It does not represent all the caches active on the server side.<br>
> >>><br>
> >>> It's something that could be useful and easy to implement - I've created <a href="https://issues.jboss.org/browse/ISPN-984">https://issues.jboss.org/browse/ISPN-984</a><br>
> >>><br>
> >>> Olaf, if you fancy learning some Scala, you could try implementing it when you're finished with the Spring work? I can guide you through it :)<br>
> >>><br>
> >>> On Mar 14, 2011, at 1:40 PM, Manik Surtani wrote:<br>
> >>><br>
> >>>> There isn't anything of the sort at the moment. I presume you'd just have to use a singleton list containing the default cache name for now.<br>
> >>>><br>
> >>>> Galder/Mircea, what are your thoughts around adding a verb to retrieve cache names to Hot Rod?<br>
> >>>><br>
> >>>><br>
> >>>> On 13 Mar 2011, at 22:30, Olaf Bergner wrote:<br>
> >>>><br>
> >>>>> I have more or less finished my first attempt at implementing Spring<br>
> >>>>> 3.1's forthcoming cache abstraction for Infinispan embedded. While doing<br>
> >>>>> the same for Infinispan remote, i.e. for Infinispan's hotrod client, I<br>
> >>>>> noticed that org.infinispan.client.hotrod.RemoteCacheManager lacks a<br>
> >>>>> method for asking it for the names of all caches that are currently<br>
> >>>>> known to it. This, however, is required for successfully implementing<br>
> >>>>> org.springframework.cache.CacheManager. For now, I work around this<br>
> >>>>> limitation by using reflection to get at RemoteCacheManager's map from<br>
> >>>>> cache names to caches. Suffice it to say that this reeks of a hack.<br>
> >>>>><br>
> >>>>> So do you think that adding such a method to RemoteCacheManager is<br>
> >>>>> feasible? Alternatively, do you know of any other way to get at the<br>
> >>>>> names of all caches managed by RemoteCacheManager?<br>
> >>>>><br>
> >>>>> Cheers,<br>
> >>>>> Olaf<br>
> >>>>> _______________________________________________<br>
> >>>>> infinispan-dev mailing list<br>
> >>>>> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
> >>>>> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
> >>>><br>
> >>>> --<br>
> >>>> Manik Surtani<br>
> >>>> <a href="mailto:manik@jboss.org">manik@jboss.org</a><br>
> >>>> <a href="http://twitter.com/maniksurtani">twitter.com/maniksurtani</a><br>
> >>>><br>
> >>>> Lead, Infinispan<br>
> >>>> <a href="http://www.infinispan.org">http://www.infinispan.org</a><br>
> >>>><br>
> >>>><br>
> >>>><br>
> >>>><br>
> >>>> _______________________________________________<br>
> >>>> infinispan-dev mailing list<br>
> >>>> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
> >>>> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
> >>><br>
> >>> --<br>
> >>> Galder Zamarreño<br>
> >>> Sr. Software Engineer<br>
> >>> Infinispan, JBoss Cache<br>
> >>><br>
> >>><br>
> >>> _______________________________________________<br>
> >>> infinispan-dev mailing list<br>
> >>> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
> >>> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
> >><br>
> >><br>
> >> _______________________________________________<br>
> >> infinispan-dev mailing list<br>
> >> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
> >> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
> >><br>
> ><br>
> > _______________________________________________<br>
> > infinispan-dev mailing list<br>
> > <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
> > <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
><br>
><br>
> _______________________________________________<br>
> infinispan-dev mailing list<br>
> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
</p>