Forum Discussion

pepo's avatar
pepo
Occasional Contributor
16 years ago

Schema Compliance – FAILED during exception testing

I tried to run my old test in new SoapUI version 2.5.
But tests for exception testing weren’t successful.
For example I have next test response: 

 

 
     
        SOAP-ENV:Server
        ContractAlreadyExists
     
 

I didn’t have validation problem in previous version (2.0.2).
But in new version 2.5 I have Schema Compliance – FAILED problem.
Is it new SoapUI feature or bug?

6 Replies

Sort By
  • omatzura's avatar
    omatzura
    Super Contributor
    16 years ago
    Hi!

    hm... do you get any more details on the failure in any of the logs?

    regards,

    /Ole
    eviware.com
  • pepo's avatar
    pepo
    Occasional Contributor
    16 years ago
    Hi,
    I got next Schema Compliance fault in SoapUI 2.5 (see attachement SoapUI25.gif):

    Line 6: Attribute not allowed (no wildcards allowed): lang@http://www.w3.org/XML/1998/namespace in element faultstring

    I didn’t get this error in older SoapUI version (2.0.2 and 2.5 beta1) – see SoapUI202.gif.

    Regards
  • omatzura's avatar
    omatzura
    Super Contributor
    16 years ago
    Hi,

    hmm.. this may have been a bug in older versions (ie not failing), but I'm not really sure. The soap 1.1 envelope xsd does not explicitly allow any wildcard attributes, so the error seems correct. Do you have any indications that this should be ok?

    regards,

    /Ole
    eviware.com
  • al0's avatar
    al0
    Occasional Contributor
    16 years ago
    Yes, such reason exists and it is called WS-I Basic Profile Version 1.1, see
    http://www.ws-i.org/Profiles/BasicProfi ... t_Language
    and it states:
    3.3.5 SOAP Fault Language

    Faultstrings are human-readable indications of the nature of a fault. As such, they may not be in a particular language, and therefore the xml:lang attribute can be used to indicate the language of the faultstring.

    Note that this requirement conflicts with the schema for SOAP appearing at its namespace URL. A schema without conflicts can be found at "http://ws-i.org/profiles/basic/1.1/soap-envelope-2004-01-21.xsd".

    R1016 A RECEIVER MUST accept faults that carry an xml:lang attribute on the faultstring element.


    So better to follow this recommendation. At least for client 
  • omatzura's avatar
    omatzura
    Super Contributor
    16 years ago
    Hi!

    thanks for this! I had no idea :-)

    I'll update soapUI to use the WS-I's modified xsd for validation here instead, will be in upcoming nightly build.

    regards!

    /Ole
    eviware.com