Breaking up xml configurations?

Question

Hi,
I'm wondering if there's an easy way to break up xml cache configurations into different (partial) xml files so that they can be easily included into other (master) xml files. That way one can easily reuse definitions without requiring to apply a single change to several files. Here's my current need:
I want to have several nodes that ultimately need to work/share a single distributed map. However there are two types of node participants:
WRITE-type nodes which can only do puts to the map
READ-type nodes which can only do reads
On top of this the storage is only enabled on the READ-type nodes (that's fine since I can do it using the init-param tags based on passed properties.)
Now, the key here is that I want the WRITE-type to use a distributed scheme and READ-type nodes to have a nead cache configuration with a back-scheme coinciding with the WRITE-type map. In both cases the real distributed cache is the same.
I don't seem to get away with this config unless I have 2 different config files for READ and WRITE types.
Am I missing anything? I would really like to avoid coding this into the application.
Also I was thinking that maybe I could use the include capabilities of xml, but either Coherence does not follow the XML standard or I've messed up something..
Anybody has had a similar problem? Am I the only one that wants to access a distributed map from different cache configurations?

Answer 1

Hi,
You can use, for example, property name to override scheme name:
<code>
<cache-mapping>
<cache-name>someCacheName</cache-name>
<scheme-name system-property="some.property">default-scheme-name</scheme-name>
</cache-mapping>
</code>
That will allow you to use a single configuration file and specify an actual scheme by using -Dsome.property=name override.
Regards,
Dimitri