Forum Discussion

BenD's avatar
BenD
Occasional Contributor
5 years ago

WSDLException Encountered illegal extension element '{http://schemas.xmlsoap.org/wsdl/}annotation'

I'm getting this WSDLException and have no clue where to start looking.  I looked at soapui-errors.log and pasted the stack trace below the WSDLException text.   WSDLException (at /definitions/mess...
InvalidDefinitionException
SOAP
WSDLException
  • richie's avatar
    richie
    5 years ago
    Hey BenD,

    I understand you're using a tool to dynamically build the .wsdl but that doesnt necessarily mean the .wsdl is built with zero issues.

    I've done a bit of googling and there are a number of reasons why this could occur.

    There's a possible problem with incorrect capitalisation of element so all words in an node name were lower case rather than lower camel case (e.g.porttype rather than portType, targetnamespace rather than targetNamespace, etc.), inclusion of an erroneous element <document>, someone else reckomed they removed ampersnd characters which they say fixed it (although i dont believe that), ensuring all elements had the appropriate namespace prefix, ensuring all elements included a namespace prefix if >1 xmlns is included and to an xmlns prefix is not required.
    If i were you i'd focus on the namespace and make sure the elements are referenced by the correct xmlns as that's whst your error message is saying

    Ta

    Rich
BenD's avatar
BenD
Occasional Contributor

HimanshuTayal: Thank you for your reply. I forgot to mention that I created the .h files that were input into soapcpp2 tool which produced the WSDL file. soapcpp2 appears to be a gsoap product from Genivia. It’s supposed to generate compliant wsdl. Wondering why SoapUI is complaining about the wsdl. The errors SoapUI gives are not very good. No idea why it’s complaining.

richie's avatar
richie
Community Hero
5 years ago
Hey BenD,

I understand you're using a tool to dynamically build the .wsdl but that doesnt necessarily mean the .wsdl is built with zero issues.

I've done a bit of googling and there are a number of reasons why this could occur.

There's a possible problem with incorrect capitalisation of element so all words in an node name were lower case rather than lower camel case (e.g.porttype rather than portType, targetnamespace rather than targetNamespace, etc.), inclusion of an erroneous element <document>, someone else reckomed they removed ampersnd characters which they say fixed it (although i dont believe that), ensuring all elements had the appropriate namespace prefix, ensuring all elements included a namespace prefix if >1 xmlns is included and to an xmlns prefix is not required.
If i were you i'd focus on the namespace and make sure the elements are referenced by the correct xmlns as that's whst your error message is saying

Ta

Rich
  • BenD's avatar
    BenD
    Occasional Contributor
    5 years ago

    Hi Rich:  Your suggestions helped narrow in on the problems.  I had some type-documentation issues and did change some variable names to camelCase.  However, I left one variable as all lower case and it worked just fine.  Now I'm wondering if the camelCase thing is an issue.  Anyway, thank you for your suggestions.  Greatly appreciated.