[5.0.0] Boundaries/Restrictions not picked up from schema
Hi all,
The bug [4.6.4] Boundary tests not working (skipped) is still persistent in version 5.0.0.
The offending code line is now here: com.eviware.soapui.security.boundary.BoundaryRestrictionUtill:40
Surely, if other open source libraries (like schema validators) can figure out what the correct standard namespace is, so can SoapUI - or ignore the namespace all together, e.g. by just looking for
As it stands, that bug stops boundary scans from working for all schemas that don't use "xsd" (but instead e.g. "xs") as their standard namespace.
Will this be fixed anytime soon?
Kind regards,
Christian
The bug [4.6.4] Boundary tests not working (skipped) is still persistent in version 5.0.0.
The offending code line is now here: com.eviware.soapui.security.boundary.BoundaryRestrictionUtill:40
if( "xsd:restriction".equals( mynode.getParent().getNodeName() ) )
Surely, if other open source libraries (like schema validators) can figure out what the correct standard namespace is, so can SoapUI - or ignore the namespace all together, e.g. by just looking for
if( ":restriction".equals( mynode.getParent().getNodeName() ) )
As it stands, that bug stops boundary scans from working for all schemas that don't use "xsd" (but instead e.g. "xs") as their standard namespace.
Will this be fixed anytime soon?
Kind regards,
Christian