[
https://issues.jboss.org/browse/JBIDE-15314?page=com.atlassian.jira.plugi...
]
Brian Fitzpatrick commented on JBIDE-15314:
-------------------------------------------
After quite a bit of head bashing, it seems there were two issues underlying this problem.
First - soapAction is not required, it just can't be null. So setting the WS Tester
code internally to use an empty string for it worked great.
Second, the operation name was namespace prefixed - like "ns2:myoperation" - and
when I'm looking through the WSDL for the various bits I need to invoke the service on
the server, I just need to strip off the namespace prefix and try comparing it that way.
WS Tester fails to execute test if SOAPAction value is null
-----------------------------------------------------------
Key: JBIDE-15314
URL:
https://issues.jboss.org/browse/JBIDE-15314
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 4.1.0.Final
Reporter: Brian Fitzpatrick
Assignee: Brian Fitzpatrick
Fix For: 4.1.1.Final
Discovered while testing the bpm-service quickstart for SwitchYard via the WS Tester. If
the SOAP operation in the WSDL includes a SOAP action, the test works just fine. But if
it's missing and the WSDL is not SOAP 1.2, it fails.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira