on 11-30-2006 3:26 PM
Hello,
we are receiving a request from a web service (SOAP sender adapter).
The message is put into pipeline and running on error during mapping.
This is how payload looks like:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!--
Mapping of Request-Message
-->
<GetMRPResult xmlns="http://xxx.com/xi/global" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<content of message....>
What I would expect is more like this (as generated from the test tool):
<?xml version="1.0" encoding="UTF-8" ?>
<ns0:GetMRPResult xmlns:ns0="http://xxx.com/xi/global">
<content of message....>
Error message in trace:
Cannot produce target element /ns0:GetMRPResult/numCandidateMatches. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at ....
<numCandidateMatches>2</numCandidateMatches> is the first element afther this header information.
What can we do to work with this incoming payload with this header area.
Or how can we move it to that what we expect...
Best regards
Dirk
Message was edited by:
Dirk Meinhard
hi,
check the occurance of the target value but use procedure like this:
/people/michal.krawczyk2/blog/2005/09/16/xi-how-to-test-your-mapping-in-real-life-scenarios
and you will find the error
Regards,
michal
-
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Michal,
the problem is definitely in this line:
ns0:GetMRPResult/numCandidateMatches -> cannot be generated.
Yes, right, because the source line for this looks like this (it is only a mapping 1:1 between same types):
<GetMRPResult xmlns="http://xxx.com/xi/global" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
So I am wondering wh this is generated instead of
<ns0:GetMRPResult xmlns:ns0="http://xxx.com/xi/global">
which I expect..
Can I influence this with the SOAP Adapter settings?
Or somehow else?
Best regards
Dirk
Hi,
That's not a SOAP adapter problem. It is due to wrong namespace in request. Check this:
<<b>ns0:</b>GetMRPResult xmlns<b>:ns0</b>="http://xxx.com/xi/global" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
Second solution is to remove namespace in integration repository.
Regards,
Wojciech
Message was edited by:
Wojciech Gasiorowski
Thanks Michal,
for remembering me about this nice thread, how to test with BPE.
Thanks Wojciech for helping me solving my problem.
I should burn this idea into my brain, because I had a similar problem some weeks ago and found this solution there on my own.
Solution: "Second solution is to remove namespace in integration repository."
Best regards
Dirk
User | Count |
---|---|
84 | |
25 | |
12 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.