[
https://issues.jboss.org/browse/ISPN-5131?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-5131:
----------------------------------------
Not 100% sure about the factory idea. Although I like the simplification, what happens
when you have both a cache loader and writer deployed? The bigger problem is how to tie a
deployed cache loader/writer with the configuration itself. How are you going to say,
"x" cache loader needs to be plugged into "y" cache?
I really think you should write up your design in a design wiki (see
https://github.com/infinispan/infinispan/wiki), where it's easier for others to
collaborate and comment on the specifics. Also, once the wiki is complete, send it to the
dev list to get everyone's input there.
Deploy custom cache store to Infinispan Server
----------------------------------------------
Key: ISPN-5131
URL:
https://issues.jboss.org/browse/ISPN-5131
Project: Infinispan
Issue Type: Feature Request
Components: Loaders and Stores, Server
Reporter: Tristan Tarrant
Assignee: Sebastian Łaskawiec
Fix For: 7.2.0.Final
h2. Overview
Support the deployment and configuration of a custom cache store.
h2. Client Perspective
In order to create a deployable Cache Store the client will have to implement
{{AdvancedLoadWriteStoreFactory}} (which will contain factory methods for creating
{{AdvancedLoadWriteStore}}). Next, the factory will have to be annotated with
{{@NamedFactory}} and placed into a jar together with proper entry of
{{META-INF/services/org.infinispan.persistence.AdvancedLoadWriteStoreFactory}}. The last
activity is to deploy given jar into Hotrod server.
h2. Implementation overview
The implementation is based on Deployable Filters and Converters.
Currently all writers and loaders are instantiated in
{{PersistenceManagerImpl#createLoadersAndWriters}}. This implementation will be modified
to use {{CacheStoreFactoryRegistry}}, which will contain a list of
{{CacheStoreFactories}}. One of the factories will be added by default - the local one
(which will the same mechanism as we do now - {{Util.getInstance(classAnnotation)}}. Other
{{CacheStoreFactories}} will be added after deployment scanning.
h2. Implementation doubts and questions:
* Should we expose a factory for {{AdvancedLoadWriteStore}} or should we include also
{{ExternalStore}} (or even separate factory for {{CacheLoader}} and {{CacheWriter}}?
** YES, we should expose all of them.
* How to ensure that deployment scanning has finished before creating instantiating
{{AdvancedLoadWriteStore}}?
** Using {{org.infinispan.server.endpoint.subsystem.EndpointSubsystemAdd}}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)