Architect Consultant blog

One of the features i missed within the WSO2 Developer Studio was a data mapper. We had to write our own XSLT or PayloadFactory within the product. But everything is going to change with the release of ESB 5.0.0 ! Or is it ? .... There is a first blog item on the datamapper that i read and tried: https://nuwanpallewela.wordpress.com/2016/04/10/how-to-use-wso2-data-mapping-mediator-in-esb/ A very good blog indeed. However when i tried the new developer studio, i was somehow disappointed. I am positive about the fact that the Mapper is a real resource (even project) now. But i miss a lot of features (like for example XPath functions, if-then-else-construct, constraints) within the mapper. As you can see from the picture below, only the following operators are supported: Concat Split LowerCase UpperCase And when you investigate the generated project files, you will notice that JScript? is generated to do the actual mapping. So my first impression is disappoin...

Here is an interesting post from Chris about dynamic transformations within the OSB. It looks great, but think about this: You loose the strong typing of the messages the proxy can receive (as described in the blog itself). This may lead to faults that are difficult to trace because the service contract is in fact far more coarse grained. How about maintenance? I like the approach that for a different major version of a service with different XML data, use a different proxy. This way services of different versions can live together and services can become obsolete when clients are no longer using the old service. If you try to put all versions of the service in one proxy service it can soonly become unmanageable. But it can still be useful to have dynamic transformations.