PRODUCTS AND SERVICES INDUSTRIES SUPPORT PARTNERS COMMUNITIES ABOUT
  The Coherence Incubator
  Coherence Common 1.1.1
Added by Brian Oliver, last edited by Rob Misek on Aug 12, 2009  (view change)

Labels

 
This documentation applies to the Coherence Common 1.1.1. The latest Coherence Common documentation is available here.

Coherence Common

The Coherence Common project provides a collection of classes that are commonly used to support the implementation of other Incubator projects.

Contained classes and packages include; an AdvancedConfigurableCacheFactory, several Backing Map Listener implementations, useful classed for creating different types of Identifiers, handling Tickets and Ranges and some customized Thread Factories.

Outline

Project Lead: Brian Oliver, Oracle
Release Name: Version 1.1.1: October 14th, 2008
Target Platforms: Java Standard Edition 5+
Requires Coherence Version: 3.3.1 or 3.4.0
Other Dependencies: (none)
Download: coherence-common-1.1.1.jar
MD5:d48f9d5ade4c1e2ee2367f89ef408dd4
Source and Documentation: coherence-common-1.1.1-src.zip
MD5:1d0c021c21cce05ddc3423fe9526b627

The AdvancedConfigurableCacheFactory

The com.oracle.coherence.common.configuration.AdvancedConfigurableCacheFactory is a drop in replacement for the standard (DefaultConfigurableCacheFactory) that Coherence uses to load cache-config.xml files.

It's completely backwards compatible with the standard ConfigurableCacheFactory, but also adds the ability to introduce and override other cache-config.xml files.

For Example;

<cache-config>
    <introduce-cache-config file="some-other-config-file-a.xml" />
    <introduce-cache-config file="some-other-config-file-b.xml" />
    ...
  </cache-config>

Order of "introduction" of files is important as each "introduction" may override and replace named elements from a previously "introduced" file. In the example above, named elements in the "some-other-config-file-b.xml" will override any definitions with the same name that where introduced in "some-other-config-file-a.xml". Additionally, the outer-level config file may also override any or all of the "introduced" named elements.

Why isn't it called <include ... />?

The <include ... /> element, as commonly used in POF configuration files, is a textual include (similar to #include in C or C++). The semantics of <introduce-cache-config ... /> are closer to that of <scheme-ref .../> but work on an entire file basis.