Requirement: Support the deployment and configuration of a custom cache store at each node of my Client-Server cluster. Priority: P2 Status: Commit (see comments) Originator: Product Management Responsible team: Infinispan Engineering Team Comments: We can commit to deployable custom cache stores but configuration would still be limited to the generic <property> list instead of a custom schema (a limitation imposed on us by EAP’s subsystem configuration model). Deployment will happen in the following ways: - place jar file containing cache store implementation in server deployment directory to be automatically picked up by the automatic deployer - deploy using the CLI - deploy using JON
TLDR: it works and "on-fly" configuration is the matter for other BZ. So, good news. All 3 types of deployment are working as expected. CCS.jar = my-awesomely-brilliant-custom-cache-store-created-using-Vijays-archetype.jar 1) Putting CCS.jar into $server_home/stadalone/deployments folder - OK 2) Using JON's EAP's parent plugin operation: DEPLOY for deploying CCS.jar - OK 3) Using our server's jboss-cli.sh - OK I was able to get custom cache store registered by server and start using it with reconfigured cache after server RESTART. I want to be explicitly clear in this statement: We need to re-configure cache and then restart the server to apply changes in the case when we have ALREADY running server. The second, more fluent use case: We deploy our CCS.jar into $server_home/standalone/deployments, configure caches to use that store and THEN start server. Server picks up CCS.jar, deploy it and after that start caches. That works nicely. Cache configuration "on-fly" in not in the scope of this BZ. VERIFIED, function works as expected. Thank you Sebastian for excellent work!!