Hi all, The current eventing implementation in Synapse is fairly extensible as it provides you with the option to create custom Event Subscribers etc. However, the filter implementation is not fully abstracted and the XPath based default filter is technically hard-coded in the implementation (ex:- the Subscription Message Builder, and the Default Subscription Manager). As the WS-Eventing specification does allow the possibility to define custom filters, I believe that it would be better if it is possible to make the filter implementation more abstract.
After doing a small research into the code base, it seems that all locations at which the filter is being used, does have access to the o.a.synapse.MessageContext. Therefore, it is possible for someone to define a custom filter either on the MessageContext or any resource made available through the MessageContext (ex:- AxisConfiguration), and then have it used in place of the default XPath based filter. I believe that there might be better ways in which this can be done, and please forgive me for any wrong assumptions made here. WDYT? Regards, Senaka
_______________________________________________ Esb-java-dev mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
