Forum Discussion

kiranvuppala's avatar
kiranvuppala
16 years ago

-> Invalid xsi:type qname: 'n2:articlelistResponse'

Hi,
  while executing the test case it is failing by throwing below error.
 
  -> Invalid xsi:type qname: 'n2:articlelistResponse'

  I think SoapUI is using XMLBean parser which is unable to parse my response. i validated it using XMPSpy even. how can i replace the parser with another one ?

Can anybody help me on this ?

Thanks,
Kiran

6 Replies

Sort By
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    16 years ago
    Hi Kiran,


    Based on the short error message alone I cannot conclude what's the reason for the error. So far XMLBeans has not betrayed us.

    Could you please attach the SOAP message that is causing this error?
    Thank you!


    Cheers!
    /Nenad Nikolic a.k.a. Shonzilla
  • Rene_Single's avatar
    Rene_Single
    Occasional Contributor
    16 years ago
    I'm having the same issue, although with a different xsi:type obviously 

    What is rather strange in my case though is the following.

    The ServiceResponse contains multiple Response Elements of xsi:type="NormalResponse", the first Response element gives me no error in the schema compliance test. Only starting from the second element I get "Invalid xsi:type qname: 'NormalResponse' ..." errors for all following Reponse elements.

    I'm using SoapUI 2.5.1
    Build dist-104-2009-02-01, Build Date 2009/02/01 21:22

    I've attached wsdl, schemas and the response.xml if that may help.

    kind regards

    René
  • Rene_Single's avatar
    Rene_Single
    Occasional Contributor
    16 years ago
    To add some further information.
    I just ran the WS-I tests against the response, and the tests pass.
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    16 years ago
    Hi Rene,

    thanks.. I get this error also, either it is a bug in how soapUI calls XmlBeans for validation or in XmlBeans itself.. (or a misunderstanding on how the schema should be interpreted).. I'll let you know when we know more..

    regards,

    /Ole
    eviware.com
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    16 years ago
    Hi again,

    this was indeed an error in how soapUI calls XmlBeans which is good since then we can (try to) fix it! Renes response validates fine now but it would be great if Kiran could either attach his message and WSDL for testing or try the upcoming nightly build and let us know if the fix works for him as well..

    Anyhow, thanks for reporting!

    regards,

    /Ole
    eviware.com
  • Rene_Single's avatar
    Rene_Single
    Occasional Contributor
    16 years ago
    Just to give you a Heads-up. The latest nightly build has indeed fixed the issue.

    Thanks for the quick fix !

    René