Re: [infinispan-dev] splitting infinispan-lucene-directory.jar
Hi Galder,
I'm not sure I understood your suggestion. Are you thinking of having
users explicitly avoid defining it in their configuration file, and
then have the application - when it's eventually started - override
the configuration of an already started cache?
2011/7/4 Galder Zamarreño <galder(a)redhat.com>:
Hmmmm, question:
Did you look into the possibility of using the LifecycleCallbacks to hook the
LuceneKey2StringMapper at runtime?
In theory, that should allow the cache manager to hook the mapper on lucene mapper on
startup assuming that the cache manager jar can successfully locate the module properties
file belonging to the lucene directory deployed in the EAR.
On Jul 2, 2011, at 12:35 AM, Sanne Grinovero wrote:
> Hello all,
> it seems that people defining an Infinispan configuration in the
> application server for the Lucene directory, and using the ad-hoc
> TwoWayKey2StringMapper, need to move the
> infinispan-lucene-directory.jar in the commons-lib directory of the
> application server.
>
> Since this module depends on Lucene too, people would need to move the
> Lucene jar too, and this is not desirable as applications might want
> to use different applications.
>
> The mapper depends of course to the objects it creates: the only clean
> option I'm seeing is to split the jar in two jars, making sure that
> the keyMapper and keys are independent from Lucene, but I'm not a big
> fan of this split.
>
> Thoughts?
>
> http://community.jboss.org/message/613078#613078
>
> Sanne
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev