Re: [Architecture] Improving Enrich Mediator

Hi Nirthika, Can you please add a redmine task [1] to the new changes you have done and update the required information on this feature? Then we can update the test cases and documentation team will be able to update the documents as well. [1]

Re: [Architecture] Improving Enrich Mediator

Hi All, As discussed in the mail thread [1], Enrich mediator has too many parameters, and some combinations are not work. I just checked the combination and found the working scenarios as follows. *Target: type* *custom* *envelope* *body* *property* *Source: type* *custom* OK Not Support OK OK

Re: [Architecture] Improving Enrich Mediator

Hi Malaka, Noted. We will do. Regards, *Nirthika Rajendran* *Associate Software Engineer* WSO2 Inc : http://wso2.org Mobile : +94 77 719 8368 LinkedIn: https://www.linkedin.com/in/nirthika/ Blog : http://nirthi-tech-stuff.blogspot.com/ On Wed, Jul 19, 2017 at 9:09 PM,

Re: [Architecture] Improving Enrich Mediator

Hi Nirthika, Find my comments inline. On Wed, Jul 19, 2017 at 5:36 PM, Nirthika Rajendran wrote: > Hi All, > > I am working on the Jira improvement [1]. The earlier discussion on this > can see on the mail thread [2] and [3]. > > As mentioned in the mail thread [2] if we

[Architecture] Improving Enrich Mediator

Hi All, I am working on the Jira improvement [1]. The earlier discussion on this can see on the mail thread [2] and [3]. As mentioned in the mail thread [2] if we remove the attributes "type" and "property" and support both via Xpath only, then should it support for backward compatibility?