Inflectra Customer Forums: WSDL outdated? (Thread) Hello! I have a problem with recieving a list of Test cases from a specified TestSetId. When I run the TestCase_RetriveByTestSetId web service I get an error. The current WSDL referres to a schema that does not longer exist (http://schemas.microsoft.com/2003/10/Serialization/Arrays). I use the v4.0 WSDL. Any suggestions on how to solve this? BR John Lunde Flennmark Consafe Logistics en-US(C) Copyright 2006-2024 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spirateam/issues-questions/784.aspxthreadId=784John Lunde Flennmark (john.lundeflenmark@se.consafelogistics.com)wsdl soapWSDL outdated? Hello! I have a problem with recieving a list of Test cases from a specified TestSetId. When I run the TestCase_RetriveByTestSetId web service I get an error. The current WSDL referres to a schema that does not longer exist (http://schemas.microsoft.com/2003/10/Serialization/Arrays). I use the v4.0 WSDL. Any suggestions on how to solve this? BR John Lunde Flennmark Consafe Logistics Fri, 13 Dec 2013 12:15:28 -05002013-12-13T14:57:42-05:00/Support/Forum/spirateam/issues-questions/784.aspxmessageId=1427John Lunde Flennmark (john.lundeflenmark@se.consafelogistics.com) When I do a validation of the WSDL for WS-I compliance I get the following errors. Assertio When I do a validation of the WSDL for WS-I compliance I get the following errors. Assertion: BP2122 Result failed Failure Detail Message Error: s4s-elt-schema-ns: The namespace of element 'import' must be from the schema namespace, 'http://www.w3.org/2001/XMLSchema'. , Error: src-resolve.4.2: Error resolving component 'q1:RemoteAutomationHost'. It was detected that 'q1:RemoteAutomationHost' is in namespace 'http://schemas.datacontract.org/2004/07/Inflectra.SpiraTest.Web.Services.v4_0.DataObjects', but components from this namespace are not referenceable from schema document 'http://sesdw080040.masystem.net/SpiraTeam/Services/v4_0/ImportExport.svc?wsdl'. If this is the incorrect namespace, perhaps the prefix of 'q1:RemoteAutomationHost' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'http://sesdw080040.masystem.net/SpiraTeam/Services/v4_0/ImportExport.svc?wsdl'. Error: src-resolve.4.2: Error resolving component 'q24:ArrayOfint'. It was detected that 'q24:ArrayOfint' is in namespace 'http://schemas.microsoft.com/2003/10/Serialization/Arrays', but components from this namespace are not referenceable from schema document 'http://sesdw080040.masystem.net/SpiraTeam/Services/v4_0/ImportExport.svc?wsdl'. If this is the incorrect namespace, perhaps the prefix of 'q24:ArrayOfint' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'http://sesdw080040.masystem.net/SpiraTeam/Services/v4_0/ImportExport.svc?wsdl'. , Error: s4s-elt-schema-ns: The namespace of element 'import' must be from the schema namespace, 'http://www.w3.org/2001/XMLSchema'. Error: src-resolve.4.2: Error resolving component 'q222:ArrayOfint'. It was detected that 'q222:ArrayOfint' is in namespace 'http://schemas.microsoft.com/2003/10/Serialization/Arrays', but components from this namespace are not referenceable from schema document 'http://sesdw080040.masystem.net/SpiraTeam/Services/v4_0/ImportExport.svc?wsdl'. If this is the incorrect namespace, perhaps the prefix of 'q222:ArrayOfint' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'http://sesdw080040.masystem.net/SpiraTeam/Services/v4_0/ImportExport.svc?wsdl'. Element Location: lineNumber=1 Fri, 13 Dec 2013 13:48:43 -05002013-12-13T14:58:18-05:00/Support/Forum/spirateam/issues-questions/784.aspx#reply1427messageId=1429David J (support1@inflectra.com) Hi John The WSDL is definitely not outdated and should allow you to use the SOAP APIs. The e Hi John The WSDL is definitely not outdated and should allow you to use the SOAP APIs. The error message you are getting sounds like it's due to some of the standard Microsoft collection namespaces not being handled by your SOAP client correctly. I would log a help desk ticket with us, providing information on what tool(s) you are using to connect to the SOAP API since I think there is a configuration error on the client-side in terms of resolving some of these collection namespaces. Regards Adam Fri, 13 Dec 2013 14:53:56 -05002013-12-13T14:58:23-05:00/Support/Forum/spirateam/issues-questions/784.aspx#reply1429