tESBProviderRequest mapping issue (maybe?)

[alang1]

For internal testing, I am trying to create a local implementation of some of the services (highlighted below) in this WSDL: https://wsnet.sendwordnow.com/webservices/v2_2/users.wsdl I imported that WSDL into my repository:

For each of the highlighted services, I created a job using “assign job” and choosing to create a new job. The simple Echo jobs work as expected. In the tXMLMap I was able to import the schema definitions from the repository for both the request and response. Here is the job and the tXMLMap component:

And after one client call, you can see (below) 1 row exiting the tESBProviderRequest and entering the map. And you can see one row exiting the map. The response is generated, and the client received it as expected:

Now, on to the next service which is not working. Again, here is the job and the tXMLMap. There are some strange things here:

1. the namespace prefixes have been changed from “v2” to “tns”
2. element “v2:contacts” has been changed to “tnsInfo”
3. the namespace prefix of “sen” has been changed to “tns”

In the Echo service, the namespace prefixes were changed as well, but everything worked. So, I am not so concerned about that change, but the “sen” prefix is supposed to point to a different namespace, so I am somewhat concerned about that. So, here is the result of a request. You can see that 1 row exists the tESBProviderRequest. But nothing comes out of the tXMLMap.

So, I am pretty sure this is a mapping issue, but I don’t know how to make it right. I have been trying different things, like changing the loop element and different logging things just to try to see if I could learn more and get to the root of the problem.  I even did a debug run to walk through all the Java code, but didn't find the answer there.  Anyone have any suggestions on what the problem is, how I can isolate it, or fix it? 

[alang1 · Accepted solution]

I was able to "solve" this be editing the xml schema to match the xml that I was submitting. I guess there is a difference between the schema generated from the wsdl by Talend vs. the sample XML generated by SoapUI.  I used the tXMLMap map editor to edit the payload schema to add/mod the namespaces and element prefixes to match what is being sent from SoapUI.  Once, I did that, the ouput started producing at least one row.