I'll be gratefull if you can help me with the following error: When I try to import a WSDL file in Azure API management I have the next error:
WsdlImportRuleImportNotSupported : WSDL Import is currently not supported
Is there a way to solve it ?
thank you!
If you look in the WSDL file you are trying to import there is a wsdl:Import element that references an external file. We don't support importing WSDLs that are split into multiple files. We can import eternal references XSD schemas though.
If your wsdl is coming from a later WCF service you can request the wsdl using a query parameter ?singleWSDL and it will merge the WSDL into a single file for you. There are also OSS tools on GitHub for doing a WSDL merge.
Related
When I use the XSLT to transform XML source file then got the below exception in Logic APP. This below URL is avail in the XSLT file.
How to resolve this issue in logic apps?
XSD schema is valid and working fine. At TransformXML place got this issue.
"Code": "InvalidXsltContent", "Message": "An error occurred while
processing map. 'Cannot find a script or an extension object
associated with namespace
'http://schemas.microsoft.com/BizTalk/2003/ScriptNS0'.'",
According to the error message, it seems the logic app can't find the external assembly from the integration account. So could you please check if you have upload the assembly to your integration account ? You can refer to this tutorial to know how to upload the assembly.
By the way, it seems you want to use custom extension in your xslt map. Here I provide two links for your reference:
https://learn.microsoft.com/en-us/biztalk/core/technical-reference/custom-extension-xml-grid-property?redirectedfrom=MSDN
https://blog.vertica.dk/2013/03/20/using-custom-xslt-in-biztalk/
When I try to create a connector in Logic App Custom Connector, with endpoint SOAP to Rest, i'm getting the following error:
The provided WSDL import method'NotSpecified' is not valid. The supported import methods are 'SoapToRest, SoapPassThrough'.
I already has done this before, and worked, but now, I cant do anymore.
Anyone knows what is happening?
Thank you
I'm trying to retrieve properties like Operation name, method type, request-response parameters etc. from a WSDL file/url through nodejs. I tried using an npm package 'wsdlrdr' which does return the operation name but does not retrieve the parameters the same way if I import the wsdl file in SOAP UI.
Is there a way to retrieve all the elements using nodejs?
Thanks
Please try SOAP npm package to retrive details from WSDL file/url. It works well with WSDL files
I'm trying to import schema files in the WSO2 Governance Registry (4.6.0) which include an import to other xsd's. The import happens using the include element.
Eg:
<xs:include schemaLocation="OtherSchemaToImport.xsd"/>
When uploading the XSD I receive following error:
Unable to upload file File upload failed. Failed to add resource
/_system/governance/myXsd.xsd.
Could not read the XML Schema Definition file. this.schema.needs
When removing the include, and specifying all elements in one XSD, the problem disappears, this is however not an acceptable solution.
Could you please give me some advice, things to try or a solution.
You can overcome this when you upload all resources as *.gar file. Where, you have to edit import definition with the location where you keep the imported resources and make a archive file and upload.
I have a couple of XSD's in my application. Something like the below,
XSD
common
common.xsd
request
request.xsd
response
response.xsd
I have to use the common.xsd in the request and response xsd's. So I have used import statement. The config is as below,
<xsd:import namespace="www.some.namespace.com" schemaLocation="../common/common.xsd"/>
The problem here is, this works absolutely fine in Tomcat. But when I deploy the same application in WebSphere, it is throwing error as file not found. In the logs, I could see WebSpher is looking for the xsd in the IBM installation folder. The path it is looking is, "C:/IBM installation folder/common/common.xsd".
Can anyone help ?
Thanks in advance.
Just remove the schemaLocation attribute of the import element. Just keep the namespace attribute alone and be sure that you are importing the correct namespace.