Could you explain how the read-write-backing-map-scheme is configured in...

Question

Could you explain how the read-write-backing-map-scheme is configured in the following example?
<backing-map-scheme>
    <read-write-backing-map-scheme>
     <internal-cache-scheme>
      <class-scheme>
       <class-name>com.tangosol.util.ObservableHashMap</class-name>
      </class-scheme>
     </internal-cache-scheme>
     <cachestore-scheme>
      <class-scheme>
       <class-name>coherence.DBCacheStore</class-name>
       <init-params>
        <init-param>
         <param-type>java.lang.String</param-type>
         <param-value>CATALOG</param-value>
        </init-param>
       </init-params>
      </class-scheme>
     </cachestore-scheme>
     <read-only>false</read-only>
     <write-delay-seconds>0</write-delay-seconds>
    </read-write-backing-map-scheme>
</backing-map-scheme>
...Edited by: qkc on 30-Nov-2009 10:48

Answer 1

Thank you very much for reply.
In the following example, the cachestore element is not specified in the <read-write-backing-map-scheme> section. Instead, a class-name ControllerBackingMap is designated. What is the result?
If ControllerBackingMap is a persistence entity, is the result same with that of cachestore-scheme?
<distributed-scheme>
            <scheme-name>with-rw-bm</scheme-name>
            <service-name>unlimited-partitioned</service-name>
            <backing-map-scheme>
                <read-write-backing-map-scheme>
                    <scheme-ref>base-rw-bm</scheme-ref>
                </read-write-backing-map-scheme>
            </backing-map-scheme>
            <autostart>true</autostart>
        </distributed-scheme>
        <read-write-backing-map-scheme>
            <scheme-name>base-rw-bm</scheme-name>
            <class-name>ControllerBackingMap</class-name>
            <internal-cache-scheme>
                <local-scheme/>
            </internal-cache-scheme>
        </read-write-backing-map-scheme>