on 04-01-2015 3:51 PM
Hi Shathish,
The problem is your java mapping. Go to the monitoring and take the payload, later in your operation mapping try to test it. If the exception persits, you will need to add traces to your java mapping in order to know in which step is raising the exception. The usual causes are the mentioned by Nabendu Sen
Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
In mapping level XML validation may not done, so take the sender payload and send from RWM test tab, If it is PO then make your sender channel as file channel and try to process the file.
There might be some invalid character found in the payload. also save the payload in desktop and open in browser.
Regards,
Manigandan
Check whether your Inbound IDoc xml or Outbound SOAP xml is well formed or has any special characters.
Are you using IDoc_AAE adapter or ALE IDoc adapter? Save your IDoc XML and SOAP XML as xml files. Then try to open them with any Explorer (Firefox / Internet Explorer)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.