soapUI Request Not Processed Correctly

Question

This is a bit obscure but I am at a loss to debug further so hope someone can help.I am creating a rate request to a rating engine but not able to successfully test through soapUI 3.0.1.From soapUI, I am able to cut/paste the input XML payload (IBDOC section) into the engine's testing tool and successfully calculate a return rate.However, from within soapUI I am not able to get a successful response and the nature of the error and the way the inputs are being echoed back indicates it is only processing the outer portion of the input XML (policy section).I believe all the header params are correct as I have used the same format in other requests and it is connecting to the engine properly and processing some of the input XML. Can you please review below and see if you can spot anything that might be the cause?Many thanks!!&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 1&nbsp; &nbsp; &nbsp; 315&nbsp; &nbsp; &nbsp; 56&nbsp; &nbsp; &nbsp; 1&nbsp; &nbsp; &nbsp; TestAuto4&nbsp; &nbsp; &nbsp; GLOBAL&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; NONE&nbsp; &nbsp; &nbsp; true&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0&nbsp; &nbsp; &nbsp; 0&nbsp; &nbsp; &nbsp; 0&nbsp; &nbsp; &nbsp; 0&nbsp; &nbsp; &nbsp; 0&nbsp; &nbsp; &nbsp; 0&nbsp; &nbsp; &nbsp; 0&nbsp; &nbsp; &nbsp; qa&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;br /&gt;&lt;rate lob="1" &gt;&lt;br /&gt;&lt;heading&gt;&lt;br /&gt;&lt;program parent_id="315"&amp;nbsp; program_id="56"&amp;nbsp; program_ver="1" /&gt;&lt;br /&gt;&lt;/heading&gt;&lt;br /&gt;&lt;policy&gt;&lt;br /&gt;&amp;nbsp; &lt;transactionType&gt;NBS&lt;/transactionType&gt;&lt;br /&gt;&amp;nbsp; &lt;policyEffectiveDate&gt;09/01/2009&lt;/policyEffectiveDate&gt;&lt;br /&gt;&amp;nbsp; &lt;LOB&gt;PA&lt;/LOB&gt;&lt;br /&gt;&amp;nbsp; &lt;policyExpirationDate&gt;09/01/2010&lt;/policyExpirationDate&gt;&lt;br /&gt;&amp;nbsp; &lt;transactionEffectiveDate&gt;09/01/2009&lt;/transactionEffectiveDate&gt;&lt;br /&gt;&amp;nbsp; &lt;TempCompanyNum&gt;001&lt;/TempCompanyNum&gt;&lt;br /&gt;&amp;nbsp; &lt;vehicle&gt;&lt;br /&gt;&amp;nbsp; &amp;nbsp; &lt;ratingTerritoryCode&gt;11&lt;/ratingTerritoryCode&gt;&lt;br /&gt;&amp;nbsp; &amp;nbsp; &lt;type&gt;VAN&lt;/type&gt;&lt;br /&gt;&amp;nbsp; &amp;nbsp; &lt;modelYear&gt;2002&lt;/modelYear&gt;&lt;br /&gt;&amp;nbsp; &amp;nbsp; &lt;TempVehicleNum&gt;1&lt;/TempVehicleNum&gt;&lt;br /&gt;&amp;nbsp; &amp;nbsp; &lt;TempCostNewAmt&gt;45000&lt;/TempCostNewAmt&gt;&lt;br /&gt;&amp;nbsp; &amp;nbsp; &lt;TempVehicleUsageCd&gt;PL&lt;/TempVehicleUsageCd&gt;&lt;br /&gt;&amp;nbsp; &amp;nbsp; &lt;TempVehicleStateName&gt;Connecticut&lt;/TempVehicleStateName&gt;&lt;br /&gt;&amp;nbsp; &amp;nbsp; &lt;vehicleCoverage&gt;&lt;br /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &lt;vehicleCoverageCode&gt;BI&lt;/vehicleCoverageCode&gt;&lt;br /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &lt;vehicleLimit1&gt;500&lt;/vehicleLimit1&gt;&lt;br /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &lt;vehicleLimit2&gt;1000&lt;/vehicleLimit2&gt;&lt;br /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &lt;TempVehicleBIInd&gt;1&lt;/TempVehicleBIInd&gt;&lt;br /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &lt;TempVehicleLimitAppliesCd1&gt;BI&lt;/TempVehicleLimitAppliesCd1&gt;&lt;br /&gt;&amp;nbsp; &amp;nbsp; &lt;/vehicleCoverage&gt;&lt;br /&gt;&amp;nbsp; &lt;/vehicle&gt;&lt;br /&gt;&amp;nbsp; &lt;policyOperator&gt;&lt;br /&gt;&amp;nbsp; &amp;nbsp; &lt;TempDateBirth&gt;03/09/1955&lt;/TempDateBirth&gt;&lt;br /&gt;&amp;nbsp; &amp;nbsp; &lt;TempMaritalStatus&gt;M&lt;/TempMaritalStatus&gt; &lt;br /&gt;&amp;nbsp; &amp;nbsp; &lt;TempGenderCd&gt;F&lt;/TempGenderCd&gt;&amp;nbsp; &amp;nbsp;&lt;br /&gt;&amp;nbsp; &amp;nbsp; &lt;TempFirstLicensedDt&gt;03/01/1975&lt;/TempFirstLicensedDt&gt;&lt;br /&gt;&amp;nbsp; &lt;/policyOperator&gt;&lt;br /&gt;&lt;/policy&gt;&lt;br /&gt;&lt;/rate&gt;&lt;br /&gt;&nbsp; &nbsp; &nbsp;

smartbear_suppo · Answer

Hi!hmm.. hard to know what is going on.. only thing that strikes me is the absence of a namespace in the XML payload (in contrary to the header xml).. does that help? If not, can you be more specific about the error messages you are getting?regards,/Oleeviware.com

wesk24 · Answer

This is what I should be getting back. ci1= Vehicle inputs echoed backci0= Policy inputs echoed back along with the last item which is a result-&nbsp; the total calculated policy premium&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; This is what I get. The empty policy inputs are echoed back along with an uncalculated premium and an error message. &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; This shows that the inputs were not parsed-&nbsp; they are echoed back only it there is at least one result for that category. We see the policy category because of an error message that results from a rule violation that all vehicles on a policy cannot be trailers. This happened because trailer is the default vehicle type. Since no vehicle inputs were processed, there were none that were calculated and the default was used resulting in the error.Note&nbsp; in the header that an XSLT mapping is specified 'TestAuto4'. This allows us to use custom input XML and map it to our native XML. I believe that for some reason the mapping is failing. What is strange is that through our application's browser test interface I can paste the same custom input XML from the IBDOC and specify the the same TestAuto4 XSLT and it works fine. soapUI can connect ok and process the request/response but it seems to be failing to pass the payload to the XSLT properly.I am using our WSDL and it does not specify a namespace in the IBDOC. Can you give me an example of where it should be placed?I hope this helps. Please let me know if anything is unclear and thanks!

Forum Discussion

soapUI Request Not Processed Correctly

Recent Discussions

unable to resolve class com...

SOAPUI 5.8.0 breaking charset of project file

Can SoapUI help me determine WSDL errors?

Related Content

REST Request keeps changing, does not save correctly

Function to wait for processing to complete

recommended upgrade process for SoapUI