Multiple MapTriggers allowed on the same cache?

Question

I'm trying to register a pair of trigger listeners on the same cache (Coherence 3.5.1)
(See below for xml scheme reported in storage node log).
It appears as if only the first listener is active.
Both triggers work if configured in isolation.
We could partially solve the problem by creating a "super" trigger that encapsulates both functions, but this would prevent us from removing one of them at runtime by unregistering the listener.
In summary:
1) If multiple triggers are not supported, then shouldn't the config below be rejected?
2) If multiple triggers are supported, could anyone suggest what I'm doing wrong?
3) If multiple triggers are supported when added programatically, but not via config, is there a recommended way of managing them?
Thanks,
Philip
<distributed-scheme>
  <scheme-name>dist-default</scheme-name>
  <backing-map-scheme>
    <local-scheme/>
  </backing-map-scheme>
  <autostart>true</autostart>
  <serializer>
    <class-name>com.tangosol.io.pof.ConfigurablePofContext</class-name>
    <init-params>
      <init-param>
        <param-type>string</param-type>
        <param-value>java_pof_config.xml</param-value>
      </init-param>
    </init-params>
  </serializer>
  <thread-count>2</thread-count>
  <listener>
    <class-scheme>
      <class-factory-name>com.psinventory.cache.EntryVersioningTrigger</class-factory-name>
      <method-name>createMapTriggerListener</method-name>
    </class-scheme>
  </listener>
  <listener>
    <class-scheme>
      <class-factory-name>com.psinventory.cache.EntryLoggingTrigger</class-factory-name>
      <method-name>createMapTriggerListener</method-name>
    </class-scheme>
  </listener>
</distributed-scheme>

Answer 1

Hi Philip
Multiple triggers do work if you add them using NamedCache.addMapListener(...). If you configure the trigger using the xml cache config file then only the first trigger is added. I will enter an internal bug for this issue.
Please be aware of 2 items:
1) The order in which the trigger is called is not specified in the API or any doc (that I know of). I did some testing and the last trigger added was the first called. However, you cannot rely on this behavior unless it is documented.
2) The output of the first trigger is passed as input to the second trigger. If you cannot rely on the ordering of the triggers then this could be a real problem.
Paul