soapUI Request Not Processed Correctly
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 s...
Forum Discussion
This is what I should be getting back.
ci1= Vehicle inputs echoed back
ci0= Policy inputs echoed back along with the last item which is a result- the total calculated policy premium
This is what I get. The empty policy inputs are echoed back along with an uncalculated premium and an error message.
This shows that the inputs were not parsed- 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 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!
ci1= Vehicle inputs echoed back
ci0= Policy inputs echoed back along with the last item which is a result- the total calculated policy premium
This is what I get. The empty policy inputs are echoed back along with an uncalculated premium and an error message.
This shows that the inputs were not parsed- 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 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!