Forum Discussion
gherr
14 years agoOccasional Contributor
Hi Amit,
we encountered the same problem and yes it is a bug in soapUI. The JMS transport always uses the operation name as soap action instead of the one specified in the WSDL.
I've fixed this issue in 3.6.1 and submitted a patch in this post http://www.eviware.com/forum/viewtopic.php?f=13&t=5759 to SoapUI Bugs.
Unfortunately, it has not been included into the main release yet. But now, there is at least one more user who would need this patch...
Regards.
Gabor
we encountered the same problem and yes it is a bug in soapUI. The JMS transport always uses the operation name as soap action instead of the one specified in the WSDL.
I've fixed this issue in 3.6.1 and submitted a patch in this post http://www.eviware.com/forum/viewtopic.php?f=13&t=5759 to SoapUI Bugs.
Unfortunately, it has not been included into the main release yet. But now, there is at least one more user who would need this patch...
Regards.
Gabor