[4.6.4] Boundary tests not working (skipped)
I have used the soapUI tutorial's sample WSDL, modified it slightly to add a constraint to it and then set up a Boundary Scan security test to try the feature. However, the scan gets skipped all the t...
Forum Discussion
I tried the same thing earlier with one of our own WSDL, and got a slightly different "error" message in the Boundary Scan window:
After doing a bit of digging, I found the following line (36) in main\java\com\eviware\soapui\security\boundary\BoundaryRestrictionUtill.java
The reason soapUI didn't pick up our restriction is that our namespace is xs, not xsd:
From what I understand, that's perfectly valid XML - which leads me to the question: why is the xsd namespace hardcoded into soapUI?!
Sure enough, after changing xs to xsd in our schema, soapUI was only too happy to oblige...
Mind you, that doesn't fix the initial problem from above (that soapUI can't find the type for the element above and throws the error message "parameter is missing type in schema") and both issues might be completely unrelated, but it's a start.
Could you please fix that issue (hard-coded namespace) in soapUI and investigate where the error with your sample WSDL comes from (I'm sure it's just a user issue), and maybe tell me how I can get my two days back...
Kind regards,
Christian
No restrictions in schema are specified for this parameter!
After doing a bit of digging, I found the following line (36) in main\java\com\eviware\soapui\security\boundary\BoundaryRestrictionUtill.java
if( "xsd:restriction".equals( mynode.getParent().getNodeName() ) )
The reason soapUI didn't pick up our restriction is that our namespace is xs, not xsd:
<xs:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
From what I understand, that's perfectly valid XML - which leads me to the question: why is the xsd namespace hardcoded into soapUI?!
Sure enough, after changing xs to xsd in our schema, soapUI was only too happy to oblige...
Mind you, that doesn't fix the initial problem from above (that soapUI can't find the type for the element above and throws the error message "parameter is missing type in schema") and both issues might be completely unrelated, but it's a start.
Could you please fix that issue (hard-coded namespace) in soapUI and investigate where the error with your sample WSDL comes from (I'm sure it's just a user issue), and maybe tell me how I can get my two days back...
Kind regards,
Christian