Forum Discussion

TimHurkmans's avatar
TimHurkmans
14 years ago

[Resolved] Schema validation fails for MockService

I have created a MockService in soapUI 4.0.1 (and 4.5), based on an existing WSDL. Now that I'm connecting to this webservice through my application, it errors on the following line: SchemaValidat...
bhamail's avatar
bhamail
New Contributor
13 years ago
I am having a similar problem.

My workaround was to use double escapes in the pom.xml property that specified my schemaLocation="" value. For example, instead of:
&


I used:
&


This allowed a filtered wsdl file to work with axis2 (1.6.1) wsdl2code.
  • bobrunstein's avatar
    bobrunstein
    New Contributor
    11 years ago

    Has anyone found a solution that does not involve pom.xml?  We do not use that.  The xsd:import statement in our wsdl does not contain any ampersands.  SoapUI is rewriting the import specified in the wsdl and adding the unescaped ampersand. This worked fine with Java 6. We noticed the SaxParseException only after upgrading to Java 7 with the same version of SoapUI.