All sounds very good. We should discuss this on infinispan-dev BTW...
On 28 Apr 2010, at 15:14, Ales Justin wrote:
It looks pretty good. Perhaps you should create a wiki page about this on Infinispan's wiki - I'm sure others will be interested.
I still need to play around a bit.
Perhaps wiki really is the best way to push this fwd, along with mentioning this on the-core and/or our weekly AS confcall.
Also, what else would we need to create an infinispan-mc module? Essentially this would be an adapter that would allow Infinispan lifecycle and config parsing to hook in to the MC, so that we could build a JBoss AS "data grid" profile such that:
${JBOSS_HOME}/servers/datagrid/lib/<infinispan jars>
${JBOSS_HOME}/servers/datagrid/conf/infinispan.xml
running:
$ run.sh -c datagrid
would start a standalone Infinispan node with:
* MC
* JNDI
* JMX
* Infinispan (based on the config in infinispan.xml)
With my prototype you can already do all of this. ;-)
All you're missing is infinispan.deployers dir/module in AS' deployers directory.
And then you would simply move conf/infinispan.xml into datagrid/deploy/ dir.
Voila! ;-)
I can setup this once you/we get confirmation from the AS team that this is the right approach.
Some configs may also include HotRod/Memcached/WebSock/REST server - the latter which would then need a web container. Same goes for servers/datagrid-managed which would also contain a JOPR instance. Perhaps then what we are looking for is:
servers/datagrid // default, p2p comms
servers/datagrid-server // + HotRod/Memcached/WebSock endpoints
servers/datagrid-REST // + REST endpoint
servers/datagrid-managed // + JOPR instance
Thoughts?
This looks too much fuss for simple config diff.
We can ask around on what the new ProfileService (PS) can help us here,
to make this a single config + some PS magic.
-Ales