Forum Discussion

CMcGlynn's avatar
CMcGlynn
New Contributor
14 years ago

Bad requests after interface definition imported cleanly

When SoapUI extracts the interface information from my web service entry point, the namespaces applied to some of the parameters are not correct. The interface appears to be imported cleanly, however, the requests that are generated are using the incorrect namespaces.

Here is a WSDL section that shows the definition of GetGroupIdList and its parameters
(Note that the GetGroupIdList operation and its parameters are defined in the http://www.qvidian.com/PlaybooksService ... ionService namespace)

<wsdl:message name="UserAdministrationService_GetGroupIdList_InputMessage">
<wsdl:part name="parameters" element="tns:GetGroupIdList" />
</wsdl:message>
<wsdl:message name="UserAdministrationService_GetGroupIdList_OutputMessage">
<wsdl:part name="parameters" element="tns:GetGroupIdListResponse" />
</wsdl:message>
<wsdl:message name="UserAdministrationService_GetGroupIdList_QvidianFaultContractFault_FaultMessage">
<wsdl:part name="detail" xmlns:q12="http://schemas.datacontract.org/2004/07/Qvidian.Common.BusinessEntities" element="q12:QvidianFaultContract" />
</wsdl:message>

<wsdl:operation name="GetGroupIdList">
<wsdl:input wsaw:Action="http://www.qvidian.com/PlaybooksServices/UserAdministrationService/UserAdministrationService/GetGroupIdList" message="tns:UserAdministrationService_GetGroupIdList_InputMessage" />
<wsdl:output wsaw:Action="http://www.qvidian.com/PlaybooksServices/UserAdministrationService/UserAdministrationService/GetGroupIdListResponse" message="tns:UserAdministrationService_GetGroupIdList_OutputMessage" />
<wsdl:fault wsaw:Action="http://www.qvidian.com/PlaybooksServices/UserAdministrationService/UserAdministrationService/GetGroupIdListQvidianFaultContractFault" name="QvidianFaultContractFault" message="tns:UserAdministrationService_GetGroupIdList_QvidianFaultContractFault_FaultMessage" />
</wsdl:operation>

XSD section that shows the definition of GetGroupIdList element.
(Note that the SortDirection data type is defined in the Qvidian.Services.PlaybooksServices.BusinessEntities namespace)


<xs:element name="GetGroupIdList">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="sessionToken" xmlns:q29="http://schemas.microsoft.com/2003/10/Serialization/" type="q29:guid" />
<xs:element minOccurs="0" name="direction" xmlns:q30="http://schemas.datacontract.org/2004/07/Qvidian.Services.PlaybooksServices.BusinessEntities" type="q30:SortDirection" />
</xs:sequence>

</xs:complexType>
</xs:element>
<xs:element name="GetGroupIdListResponse">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="GetGroupIdListResult" nillable="true" xmlns:q31="http://schemas.microsoft.com/2003/10/Serialization/Arrays" type="q31:ArrayOfguid" />
</xs:sequence>
</xs:complexType>
</xs:element>

XML version of the sample request from SoapUI
(Note that the direction parameter is tagged as being a member of the http://www.qvidian.com/PlaybooksService ... ionService namespace)

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:user="http://www.qvidian.com/PlaybooksServices/UserAdministrationService">
<soap:Header/>
<soap:Body>
<user:GetGroupIdList>
<!--Optional:-->
<user:sessionToken>?</user:sessionToken>
<!--Optional:-->
<user:direction>?</user:direction>
</user:GetGroupIdList>
</soap:Body>
</soap:Envelope>
  • Hi,

    thanks for reporting - and sorry for the long response time. I agree it looks like a bug - we'll have to look into it.

    regards,

    /Ole
    SmartBear Software
  • CMcGlynn's avatar
    CMcGlynn
    New Contributor
    Thanks for looking into it. What else do you need from us?
  • CMcGlynn's avatar
    CMcGlynn
    New Contributor
    Hello,

    Requested information was provided on March 14th.
    Can we please get an update on this issue?
    Has the problem been reproduced/Is this confirmed to be a defect?
    If so, what should be our expectation around having this resolved?
    A quick reply would be appreciated as this was reported back on March 7th and this issue now is impacting internal deadlines.

    Respectfully,
    Qvidian Corporation Support
  • CMcGlynn's avatar
    CMcGlynn
    New Contributor
    BUMP!!!! Can we please get an update or some type of response on this issue? Please refer to previous post on 3/22.
  • Hi,

    I've located the support ticket and see that a reply was sent via email on March 26th. In case you did not get it I'll copy the content here:


    I've having some problem linking the WSDL and the schema that you send us.
    Is it possible for you to send your whole project file?

    --
    Regards

    Erik
    SmartBear Sweden


    Regards,
    Dain
    SmartBear Software