Contributions
Re: Schema Compliance fails validating xsi:type with unprefixed namespace
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/v12.2KViews0likes0CommentsRe: Schema Compliance fails validating xsi:type with unprefixed namespace
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, Jeroen2.2KViews0likes0CommentsSchema 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 Willems5.4KViews0likes10CommentsTestrunner export all on windows xp (path too long)
We are using significant names in our testsuites/testcases/testrequest but because Testrunner will export to files using the following naming: "Exported files are written to a file named - - - - .txt" the path to the file is too long and the file isn't accesible via windows. Is it possible to reduce the name size in the export (not in the soapUI-project)? Thanx, Jeroen1.5KViews0likes2Comments