Forum Discussion

goutamgujjar's avatar
14 years ago

Getting error while hitting the mock service in soapUI

Hi,

I trying to do a POC for using the SOAPUI for mocking the webservice for our application, but was facing the issue while i try to hit the mock service through the application.

The is issue is when try to the Mock service with in the soapUI, with request which is generated by the soapUI, everything works fine. But the same thing when we try to hit for the application we are getting following exception.
"com.eviware.soapui.impl.wsdl.mock.DispatchException: Missing operation for soapAction [] and body element [{http://csi.cingular.com/CSI/Namespaces/Container/Public/InquireBundledAccountServicesRequest.xsd}InquireBundledAccountServicesRequest] with SOAP Version [SOAP 1.1]"

I have verify the request in both the cases, everything looks same apart for the namespace. is there some that i am missing here. do in need to change any of the setting in soapUI to get this work????

I have attached both the request below. If anyone could help me resolving this it would be very helpful.

With below request xml, which is generted by the soapUI. I was able to successfully hit the server and get respone back
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:mes="http://csi.cingular.com/CSI/Namespaces/Types/Public/MessageHeader.xsd" xmlns:cin="http://csi.cingular.com/CSI/Namespaces/Types/Public/CingularDataModel.xsd" xmlns:inq="http://csi.cingular.com/CSI/Namespaces/Container/Public/InquireServiceAvailabilityForLocationRequest.xsd">
<soapenv:Header>
<mes:MessageHeader>
<mes:TrackingMessageHeader>
<cin:version>v56</cin:version>
<cin:messageId>10.9.33.173:65bee80d:135a77752ca:-7fbe</cin:messageId>
<cin:originatorId>PEPS</cin:originatorId>
<cin:conversationId>11234123521235112341235212351123</cin:conversationId>
<cin:dateTimeStamp>2012-02-23T00:18:43.936Z</cin:dateTimeStamp>
</mes:TrackingMessageHeader>
<mes:SecurityMessageHeader>
<cin:userName>pepstore</cin:userName>
<cin:userPassword>testpepstore</cin:userPassword>
</mes:SecurityMessageHeader>
<mes:SequenceMessageHeader>
<cin:sequenceNumber>1</cin:sequenceNumber>
<cin:totalInSequence>1</cin:totalInSequence>
</mes:SequenceMessageHeader>
</mes:MessageHeader>
</soapenv:Header>
<soapenv:Body>
<inq:InquireServiceAvailabilityForLocationRequest>
<inq:ServiceAvailabilitySelector>
<inq:LocationDetails>
<cin:FieldedAddress>
<cin:addressLine1>1701 NOVATO BL</cin:addressLine1>
<cin:addressLine2/>
<cin:city>NOV</cin:city>
<cin:state>CA</cin:state>
<cin:Zip>
<cin:zipCode>94947</cin:zipCode>
<cin:zipGeoCode/>
</cin:Zip>
<cin:country>US</cin:country>
</cin:FieldedAddress>
</inq:LocationDetails>
</inq:ServiceAvailabilitySelector>
<inq:AvailabilityPortabilityOption>
<inq:ProductAvailabiltySelection>
<inq:UversePotsDslSelection>
<inq:dsl>true</inq:dsl>
</inq:UversePotsDslSelection>
<inq:UversePotsDslSelection>
<inq:pots>true</inq:pots>
</inq:UversePotsDslSelection>
<inq:UversePotsDslSelection>
<inq:uverse>true</inq:uverse>
</inq:UversePotsDslSelection>
<inq:BvoipMisSelection>
<inq:bvoipAndMIS>true</inq:bvoipAndMIS>
</inq:BvoipMisSelection>
</inq:ProductAvailabiltySelection>
</inq:AvailabilityPortabilityOption>
</inq:InquireServiceAvailabilityForLocationRequest>
</soapenv:Body>
</soapenv:Envelope>


the request that is getting generated by the applicaton is as below. and there is no issue in application since we are able to get the respone with below request.

<?xml version="1.0" encoding="UTF-8"?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Header>
<ns2:MessageHeader
xmlns="http://csi.cingular.com/CSI/Namespaces/Types/Public/CingularDataModel.xsd"
xmlns:ns2="http://csi.cingular.com/CSI/Namespaces/Types/Public/MessageHeader.xsd"
xmlns:ns3="http://csi.cingular.com/CSI/Namespaces/Container/Public/InquireServiceAvailabilityForLocationRequest.xsd"
xmlns:ns4="http://csi.cingular.com/CSI/Namespaces/Container/Public/InquireServiceAvailabilityForLocationResponse.xsd"
xmlns:ns5="http://csi.cingular.com/CSI/Namespaces/Types/Public/ErrorResponse.xsd" xmlns:ns6="http://csi.cingular.com/CSI/Namespaces/Types/Public/SoapFaultDetails.xsd">
<ns2:TrackingMessageHeader>
<version xmlns="">v56</version>
<messageId xmlns="">10.9.33.173:65bee80d:135a77752ca:-7fbe</messageId>
<originatorId xmlns="">PEPS</originatorId>
<conversationId xmlns="">11234123521235112341235212351123</conversationId>
<dateTimeStamp xmlns="">2012-02-23T00:18:43.936Z</dateTimeStamp>
</ns2:TrackingMessageHeader>
<ns2:SecurityMessageHeader>
<userName xmlns="">pepstore</userName>
<userPassword xmlns="">testpepstore</userPassword>
</ns2:SecurityMessageHeader>
<ns2:SequenceMessageHeader>
<sequenceNumber xmlns="">1</sequenceNumber>
<totalInSequence xmlns="">1</totalInSequence>
</ns2:SequenceMessageHeader>
</ns2:MessageHeader>
</S:Header>
<S:Body>
<ns3:InquireServiceAvailabilityForLocationRequest
xmlns="http://csi.cingular.com/CSI/Namespaces/Types/Public/CingularDataModel.xsd"
xmlns:ns2="http://csi.cingular.com/CSI/Namespaces/Types/Public/MessageHeader.xsd"
xmlns:ns3="http://csi.cingular.com/CSI/Namespaces/Container/Public/InquireServiceAvailabilityForLocationRequest.xsd"
xmlns:ns4="http://csi.cingular.com/CSI/Namespaces/Container/Public/InquireServiceAvailabilityForLocationResponse.xsd"
xmlns:ns5="http://csi.cingular.com/CSI/Namespaces/Types/Public/ErrorResponse.xsd" xmlns:ns6="http://csi.cingular.com/CSI/Namespaces/Types/Public/SoapFaultDetails.xsd">
<ns3:ServiceAvailabilitySelector>
<ns3:LocationDetails>
<FieldedAddress xmlns="">
<addressLine1>1701 NOVATO BL</addressLine1>
<addressLine2/>
<city>NOV</city>
<state>CA</state>
<Zip>
<zipCode>94947</zipCode>
<zipGeoCode/>
</Zip>
<country>US</country>
</FieldedAddress>
</ns3:LocationDetails>
</ns3:ServiceAvailabilitySelector>
<ns3:AvailabilityPortabilityOption>
<ns3:ProductAvailabiltySelection>
<ns3:UversePotsDslSelection>
<ns3:dsl>true</ns3:dsl>
</ns3:UversePotsDslSelection>
<ns3:UversePotsDslSelection>
<ns3:pots>true</ns3:pots>
</ns3:UversePotsDslSelection>
<ns3:UversePotsDslSelection>
<ns3:uverse>true</ns3:uverse>
</ns3:UversePotsDslSelection>
<ns3:BvoipMisSelection>
<ns3:bvoipAndMIS>true</ns3:bvoipAndMIS>
</ns3:BvoipMisSelection>
</ns3:ProductAvailabiltySelection>
</ns3:AvailabilityPortabilityOption>
</ns3:InquireServiceAvailabilityForLocationRequest>
</S:Body>
</S:Envelope>
No RepliesBe the first to reply