<div dir="ltr">Hi,<div><br></div><div>I just want to re-iterate this to try and get it ready for the final Wildfly 10 release. In order to make Redis integration, what changes should I be making? In particular;</div><div><br></div><div><ol><li>xml reader/writer - should I be adding redis-store as a concrete xml tag?<br></li><li>persistence pom updates to add the redis jar dependency</li><li>xsd documentation updates</li><li>module configurations</li><li>jboss-cli - do I need to add a redis-store type to a cache container?</li><li>web management console - again redis-store type to a cache container?</li></ol><div><br></div></div><div>1 - 3 are done, 4 is in progress, however I am unclear on how to make 5 and 6 (can't find the code locations), and I also want steer on whether a concrete store type is needed or if the custom store should be the way to go, in which case I think only pom updates and module config is required.</div><div><br></div><div>Kind regards,</div><div>Simon</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 15 September 2015 at 14:38, Simon Paulger <span dir="ltr"><<a href="mailto:spaulger@codezen.co.uk" target="_blank">spaulger@codezen.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div>Hi Jason,</div><div><br></div><div>I have developed a redis cache store which has now been completed and released under the infinispan org as part of version 8, available through central.</div><div><br></div><div>I had begun to look at what changes would be required under wildfly. I have made changes to the xml reader and writer for config for a concrete redis-store type but haven't worked out how to update the web ui and cli.</div><div><br></div><div>This got me thinking as to whether a concrete config tag is required at all since there is always the custom store.</div><div><br></div><div>Therefore, I thought I'd check. What changes should I be developing to make my redis integration in to wildfly 10?</div><div><br></div><div>Thanks</div><div>Simon<br><br>Sent from my iPhone</div><div><div class="h5"><div><br>On 28 Jul 2015, at 21:22, Jason Greene <<a href="mailto:jason.greene@redhat.com" target="_blank">jason.greene@redhat.com</a>> wrote:<br><br></div><blockquote type="cite"><div><br><div><blockquote type="cite"><div>On Jul 28, 2015, at 3:04 PM, Simon Paulger <<a href="mailto:spaulger@codezen.co.uk" target="_blank">spaulger@codezen.co.uk</a>> wrote:</div><br><div><div dir="ltr">Hi,<div><br></div><div>My company uses JBoss AS 7 (before Wildfly I know). We also use Redis cache store for PHP stacks and I'd like to be able to do the same for Wildfly (I'm considering upgrade paths).</div><div><br></div><div>I see there is an old JIRA enhancement issue raised here: <a href="https://issues.jboss.org/browse/ISPN-3465" target="_blank">https://issues.jboss.org/browse/ISPN-3465</a></div><div><br></div><div>I was wondering what the appetite for creating a Redis cache store is. If this were something I were to develop in both inifinispan and wildfly, would it be well received by the JBoss community?</div></div></div></blockquote><div><br></div><div>Hi Simon, </div><div><br></div><div>Thanks for the interest, and it sounds great to me! </div><div><br></div><div>I would recommend starting by posting to infinispan-dev your interest in the feature (if you haven’t already), and they can help you get started. I would imagine the infinispan memcached code is a good starting point, and may in fact be adaptable to the Redis protocol, perhaps by forking it.</div><div><br></div><div>One thats done there is some integration bits on the WildFly side, but I wouldn’t worry about that until its shipped in an infinispan release.</div><div><br></div><div>Thanks,</div></div><div>--</div><div>Jason T. Greene<br>WildFly Lead / JBoss EAP Platform Architect<br>JBoss, a division of Red Hat
</div>
<br></div></blockquote></div></div></div></blockquote></div><br></div>