Anil,

When do you think Geode will have it, I want to check it .?
Dor

From: Anilkumar Gingade [mailto:[email protected]]
Sent: יום ג 16 פברואר 2016 19:46
To: [email protected]
Subject: Re: cache.xml

I am suspecting, since this is part of "WAN" functionality, which was not yet 
part of the Geode code base (when m2-snapshot created); it may not be 
working...This was added recently (as part of merging CQ and WAN functionality 
from closed to open source)....

Geode dev's correct me if i am wrong...

-Anil.












On Tue, Feb 16, 2016 at 7:56 AM, Dor Ben Dov 
<[email protected]<mailto:[email protected]>> wrote:
Hi,

We are having the following problem, need your assistance if you can,

Short description of the problem :

In the cache.xml configuration, we are using gateway-event-substitution-filter 
element that allow us to define implementation to the 
com.gemstone.gemfire.cache.wan.GatewayEventSubstitutionFilter,
this implementation allow us to choose the Object that we want to insert to the 
async queue.
This implementation should be called when doing put to the region before 
calling to the GatewayEventFilter implementation.

        <async-event-queue id="PWInfoQueue" persistent="false" parallel="true" 
batch-size="10"
        dispatcher-threads="1" order-policy="partition"
                disk-store-name="PWInfo-queue-overflow" 
maximum-queue-memory="256">
                <gateway-event-filter>
                        <class-name>listeners.PWInfoFilter</class-name>
                </gateway-event-filter>
                <gateway-event-substitution-filter>
                        
<class-name>listeners.PWInfoSubstitutionFilter</class-name>
                </gateway-event-substitution-filter>
                <async-event-listener>
                        <class-name>listeners.PWInfoListener</class-name>
                </async-event-listener>
        </async-event-queue>

It seems that this functionality is missing from the M2-SNAPSHOT version , and 
our implementation is never called when doing put on the region.

Thanks,
Guy

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement, you may review at 
http://www.amdocs.com/email_disclaimer.asp

Reply via email to