Closed tao-aldo closed 6 years ago
It looks like Apache CXF used for validation of WSDL documents ignores a lot of problems with WSDLs. We should consider switching to a better wsdl validator.
Additionaly we should store WSDL's in security server to avoid the problem when WSDL is changed after passing validation.
There's an issues regarding updating the WSDL validator in the X-Road backlog:
All the issues from the Joint Development backlog are transferred to new X-Road backlog. Before enhancement requests are accepted to the backlog they are evaluated by the Working Group.
If this enhancement request is still valid, please sign up for an account first, and then submit it to the X-Road Service Desk. You will be notified by email once the Working Group has processed your request.
Affected components: wsdl-validator Affected documentation: - Estimated delivery: - External reference: -
Problem Often service description wsdls don't compile to X-Road Message Protocol and some even not valid as wsdl. Seems, that included wsdl-validator is too lax and not working correctly.
Examples:
Also seen errors like <element name="Elukoht " (space in element name) and validator tolerates soap-encoding array type as element type. After complaining service owner already fixed them.
Acceptance criteria