+1, that's quite counter-intuitive. Also not consistent with how other stuff works,
e.g. adding an interceptor *instance* to the chain.
I couldn't find the JIRA either, so I created one. Better a duplicate it than forget:
From: "Sanne Grinovero" <sanne(a)infinispan.org>
To: "infinispan -Dev List" <infinispan-dev(a)lists.jboss.org>
Sent: Tuesday, June 26, 2012 3:21:14 PM
Subject: Re: [infinispan-dev] Configuring a Loader by Instance
BTW this is also needed to be able to migrate the testsuite to
actually use the new Configuration API, which in turn is needed to
make sure the new API is stable.
I'm migrating the testsuite of Query and Lucene Directory, I think we
should migrate all tests ASAP, as I'm sure we promised to do to Pete
back in October to test his configuration work...
Sanne
On 26 June 2012 15:15, Sanne Grinovero <sanne(a)infinispan.org> wrote:
> I'm needing to pass an instance of a CacheLoader and other services
> directly to a ConfigurationBuilder, or have any way to start an
> EmbeddedCacheManager using my existing instances.
>
> There is this comment in the code, which seems to promise it will
> be
> possible in 5.2 :
>
>
https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o...
>
> Who's working on it? Any progress? Sorry I couldn't find the issue,
> nor I remember any discussion about this.. still this would be very
> useful.
>
> Actually configuring a CacheLoader is just the first step of the
> flexibility I need, I eventually will need to be able to wire-up
> more
> "internal" component type from provided instances, but the
> CacheLoader
> would be a good start.
>
> Cheers,
> Sanne
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev