Forum Discussion

Jeroen's avatar
Jeroen
Occasional Contributor
17 years ago

Schema Compliance fails validating xsi:type with unprefixed namespace

soapUI (2.5) Schema Compliance test fails when response contains xsi:type with unprefixed namespace.

When validation via tools like XMLSpy or Stylus with different parsers the response is valid.

What (parser, ...) does soapUI uses to check schema compliance.
Is there a possibility do the schema compliance check with another parser, ...?

Thanx,

Jeroen Willems

10 Replies

  • omatzura's avatar
    omatzura
    Super Contributor
    17 years ago
    Hi Jeroen,

    soapUI uses XMLBeans 2.4.0 for validation.. can you give an example schema/xml that fails validation so I can have a look?

    regards!

    /Ole
    eviware.com
  • Jeroen's avatar
    Jeroen
    Occasional Contributor
    17 years ago
    Hi Ole,

    Thanx for the quick response.

    I can't give the example (security reasons) but I tested it using the validate.cmd from XMLBeans 2.4.0 from commandline and via Stylus Studio and the xml was valid.

    Hope you can do something with this.

    Regards,
    Jeroen
  • omatzura's avatar
    omatzura
    Super Contributor
    17 years ago
    ok.. is the namespace imported from another file? Can you give a schematic overview of import/include/namespace constructs so I can try to reproduce this?

    regards!

    /Ole
    eviware.com
  • Jeroen's avatar
    Jeroen
    Occasional Contributor
    17 years ago
    In the .xsd there are a lot of imports, but these don't affect the issue I think.

    Summary:
    xsd :
    targetNamespace='http://jefke.com/v1'
    ...
    xmlns:xyz='http://jefke.com/v1'
    ...

    ....


         
    ....


          ...
    ....



    xml
    xmlns:ns5="http://iets.com"
    ....
    xmlns="http://jefke.com/v1"
    ...


           
                        3551sfsdf62fsdf305
           

    ...


    This results in soapUI 2.5 (free version)
    Invalid xsi:type qname: 'HereIsIt' in element SomeElements@http://jefke.com/v1
  • omatzura's avatar
    omatzura
    Super Contributor
    17 years ago
    Hi Jeroen,

    not yet unfortunately.. I'll let you know!

    regards,

    /Ole
    eviware.com
  • Jeroen's avatar
    Jeroen
    Occasional Contributor
    17 years ago
    Hi Ole,

    is there any progress on this issue?

    Cheers,
    Jeroen
  • omatzura's avatar
    omatzura
    Super Contributor
    17 years ago
    Hi Jeroen,

    sorry, not yet.. stay tuned..

    regards,

    /Ole
    eviware.com
  • genesis's avatar
    genesis
    16 years ago
    I seem to experience the same problem.
    I suspect it has something to do with abstract complexType. All the schema compliance errors points to the types that are extended from an abstract type.
    I see in this example there is some abstract type as well.


    Thanks.
  • grussell's avatar
    grussell
    Contributor
    14 years ago
    Any update on this?

    I think i am getting something similar in v3.6.1, hopefully it won't be too long before I get my pro licence and download of v4 to see if it's fixed there...

    Thanks