Fix Service Catalog not publishing SOAP Proxy #2979
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The specific problem arises when the WSDLReader component in APIM attempts to read the WSDL content with a schemaLocation attribute set to 'proxy2?xsd=sample.xsd'. Upon parsing, WSDLReader treats this schemaLocation as a file path rather than as a query string, leading to a failure in resolving the actual schema location. So changed the schemaLocation into actual URL. Fixes: wso2#2967
rosensilva
approved these changes
Sep 22, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
The specific problem arises when the WSDLReader component in APIM attempts to read the WSDL content with a schemaLocation attribute set to 'proxy2?xsd=sample.xsd'. Upon parsing, WSDLReader treats this schemaLocation as a file path rather than as a query string, leading to a failure in resolving the actual schema location. So changed the schemaLocation into actual URL.
Fixes: #2967