Issue importing wsdl/xsd containing oasis-200401-wss-wssecurity-secext-1.0.xsd
Hi The error (snippet) is
Info : SchemaLocation: http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd, SchemaDirectory: C:\Users\pais\api-management-schema-import\ApiManagementSchemaImport\Microsoft.Azure.ApiManagement.WsdlProcessor.App\bin\Debug\net5.0 Info : import Info : SchemaLocation: http://www.w3.org/2001/xml.xsd, SchemaDirectory: C:\Users\XXX\api-management-schema-import\ApiManagementSchemaImport\Microsoft.Azure.ApiManagement.WsdlProcessor.App\bin\Debug\net5.0 Info : import Info : SchemaLocation: http://www.w3.org/TR/xmldsig-core/xmldsig-core-schema.xsd, SchemaDirectory: C:\Users\pais\api-management-schema-import\ApiManagementSchemaImport\Microsoft.Azure.ApiManagement.WsdlProcessor.App\bin\Debug\net5.0 Info : XsdImportInclude : Location: 'http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd' TargetNamespace: 'http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd'. Error : The filename, directory name, or volume label syntax is incorrect. : 'C:\Users\pais\api-management-schema-import\ApiManagementSchemaImport\Microsoft.Azure.ApiManagement.WsdlProcessor.App\bin\Debug\net5.0\http:\docs.oasis-open.org\wss\2004\01\oasis-200401-wss-wssecurity-utility-1.0.xsd' Error : Stacktrace: at System.IO.FileStream.ValidateFileHandle(SafeFileHandle fileHandle)
Hi @sanpai2002 , Could you provide more information about the command line that you tried to run?
@sanpai2002 can you share the .wsdl file?
@shinjiDev The problem that @sanpai2002 are talking is because when the app are trying read the xsd file. the class ApiManagementSchemaImport/Microsoft.Azure.ApiManagement.WsdlProcessor.Common/WsdlDocument.cs concatenates two parameters (SchemaDirectory and SchemaLocation). When try to read, the exception is created and the app broken.
To correct this and others problema that I related at my pull request #22
@shinjiDev I think that this pull request can be close.
With my pull request #22 we resolved this and others problems.
FYI @sanpai2002
@shinjiDev This is not a problem at the new version.
This issue can be close!