Introducing the Functor Pattern

Question

As discussed at the London and New York Coherence Special Interest Group events last month, we've now made an initial implementation of the [Functor Pattern|http://coherence.oracle.com/display/INCUBATOR/Functor+Pattern] available on the [Coherence Incubator|http://coherence.oracle.com/display/INCUBATOR] Site.
The [Functor Pattern|http://coherence.oracle.com/display/INCUBATOR/Functor+Pattern] is an extension of the [Command Pattern|http://coherence.oracle.com/display/INCUBATOR/Command+Pattern] but additionally allows for values to be returned (or exceptions to be re-thrown) from an executed Functor (through the use of standard Java 5+ Futures).
The internal implementation makes use of the new Command Pattern (version 2.2.0) implementation released two weeks ago. If you haven't already done so, you'll need to upgrade to Command Pattern 2.2.0 and Coherence Common 1.2.0 to use the Functor Pattern.
Enjoy
-- Brian

Answer 1

Figured this out thanks to a pointer from Randy Stafford.
Original commands-cache-config.xml that the functor pattern uses by default (which the functor results cache references as a scheme):
          <distributed-scheme>
               <scheme-name>distributed-scheme-with-backing-map-listener</scheme-name>
               <service-name>DistributedCacheWithBackingMapListener</service-name>
In order for CacheServer processes to start that service up - you need to add:
<autostart>true</autostart>
like this:
          <distributed-scheme>
               <scheme-name>distributed-scheme-with-backing-map-listener</scheme-name>
               <service-name>DistributedCacheWithBackingMapListener</service-name>
<autostart>true</autostart>
I used the cache-config files that ship in the Incubator project source so that should probably be adjusted.
Then it works