Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Incorrect value when generating a consumer proxy

Former Member
0 Likes
1,895

Hello,

When generating a consumer proxy, I get the following error, "Incorrect value: Entity"<<document>"(60/2961). end tag 'ul' dos not match begin tag 'p'. " (see attached screen shot).

What might be causing this and how may it be corrected?

Thanks,

Huntr

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
1,478

Hello,

It looks like you are trying to create a proxy using badly formed HTML instead of a WSDL file.

Stuart.

6 REPLIES 6
Read only

Former Member
0 Likes
1,479

Hello,

It looks like you are trying to create a proxy using badly formed HTML instead of a WSDL file.

Stuart.

Read only

0 Likes
1,478

Hello,

Formerly, I was using the URL to generate a consumer proxy and I was getting the previous message.  So, what I tried next was to download the WSDL file to a local file and used that instead.  This time, I got this error:

"WSDL error: any any message GetNCRInformationSoapIn(http://tempuri.org/) defined more than once."

And here's the snippet of the cause of the error (supposedly):

First instance of the message name:

<wsdl:message name="GetNCRInformationSoapIn"> 

<wsdl:part name="parameters" element="tns:GetNCRInformation" />
Second Instance:

- <wsdl:operation name="GetNCRInformation">

<wsdl:input message="tns:GetNCRInformationSoapIn" />

<wsdl:output message="tns:GetNCRInformationSoapOut" />
How is this resolved?
Kind regards,
Huntr

Read only

0 Likes
1,478

Hi,

Can you validate the WSDL using a tool?

If the WSDL is valid, your problems may be with how SAP interprets the WSDL file.

Unfortunately, we have had several issues with SAP loading WDSLs:

  • Check if the WSDL file references another file (xsd:import )
  • Check if there is an <extension> element
  • Check if there is mixed content
  • Watch out how SAP create namespaces when none are specified

All of the above have forced us to load WSDL files amended by hand for SAP. But maybe now there are notes or other fixes that may help you.

Good luck!

Stuart.

Read only

0 Likes
1,478

Thank you for the tips, Stuart.  I'll do more research.

Regards,

Reyleene

Read only

0 Likes
1,478

Hello again Reyleene,

I have just had a situation when I received the "defined more than once" error - this was fixed by removing some ref attributes from the WSDL "<element ref=...>".

Best of luck,

Stuart.

Read only

Former Member
0 Likes
1,478

This message was moderated.