Description
WSDL schemaLocation with spaces in the relative path is valid but WSDLDefintionBuilder can't handle it because it does not encode the spaces before using it in URI methods.
Another problem is that ?wsdl can serve up a WSDL that includes unencoded space (e.g. http://localhost:3580/services/AddCustomer?xsd=../schema/folder with spaces/customer.xsd). It causes problem for client.