on 08-20-2014 1:38 PM
Hi Experts,
We are working with Integration gateway converting SOAP WS into OData services. We have observed a weird behavior in OData response. Let me share some insight on this:
some of the input parameters in SOAP WS are having "underscore" in their names (as highlighted below). like: Amfi_Code, End_Date etc
We are able to do request and response mapping and able to deploy as well. When we do a "POST" method in rest client, we get a response says:
com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot produce target element /ns4:GetSWPSummaryMarged/ns4:Input/ns3:QueryParameters/ns5:Amfi_Code. Queue has not enougth values in context. Target xsd requires a value for this element, but target field mapping does not produce one. Probably the xml-instance is not valid to the source xsd, or the target field mapping does not fulfill the requirement of the target xsd.
To overcome this issue, backend team updated this service's input parameters by removing "underscore" and it worked.
So is this a bug in Integration gateway? Can we not have an input parameter having "underscore" in its name?
Regards,
Jitendra
Dear Jitendra,
Thank you for reporting this.
We are aware of the issue, and this is planned to be fixed in the upcoming PL03 for SP03.
Kind regards
Bjoern
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
yeah. This issue has been resolved in SMP 3.0 SP04 PL01.
Regards,
JK
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
95 | |
11 | |
11 | |
10 | |
9 | |
8 | |
6 | |
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.