Issue with JIRA Jelly SOAP Script Implementation - Need Help Debugging

Other Questions Jira
1

I’m having trouble with a JIRA Jelly script that uses SOAP calls and can’t figure out what’s going wrong. The WSDL file itself is fine because it works when I test it with SOAP directly, but something in my Jelly implementation is broken.

<JiraJelly xmlns:jira="jelly:com.atlassian.jira.jelly.enterprise.JiraTagLib" xmlns:core="jelly:core" xmlns:soap="jelly:soap">
<core:new var="serviceEndpoint" className="java.lang.String">
    <core:arg type="java.lang.String" value="http://myserver:8080/testWSDLService/testWSDLPort"/>
</core:new>
<core:new var="actionHeader" className="java.lang.String">
    <core:arg type="java.lang.String" value="POST http://myserver:8080/testWSDLService/testWSDLPort HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: text/xml;charset=UTF-8
SOAPAction: ''
User-Agent: Jakarta Commons-HttpClient/3.1
Host: myserver:8080
Content-Length: 308"/>
</core:new>
<soap:invokeRaw endpoint="${serviceEndpoint}" soapAction="${actionHeader}" var="response">
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:test="http://example.com/wsdl/TestModule/testWSDL">
       <soapenv:Header/>
       <soapenv:Body>
          <test:testWSDLOperation>
             <message>World</message>
          </test:testWSDLOperation>
       </soapenv:Body>
    </soapenv:Envelope>
</soap:invokeRaw>
</JiraJelly>

Any ideas what might be causing the problem?

2

hey bob, it seems ur soapAction is off. you should just use soapAction=‘’ on its own and remove that long header. try that and let me know if it helps!

3

Looking at your code, the main issue isn’t just the soapAction parameter - you’re mixing HTTP headers with SOAP parameters, which causes problems. I’ve worked with JIRA implementations before, and soap:invokeRaw works much better when you stick to clean SOAP parameters instead of throwing in raw HTTP header stuff. You can drop that actionHeader variable completely. Also, double-check your SOAP envelope namespaces - inconsistencies there will break things. I’ve had better luck using the default namespace without prefixes. Focus on getting the SOAP structure right instead of trying to manage HTTP headers manually.

4

Your soap:invokeRaw setup is the problem. You’re passing the entire HTTP header as the soapAction parameter - that’s wrong. The soapAction should only be the actual SOAP action value, not the full HTTP headers. I’ve dealt with similar JIRA Jelly SOAP integrations before. You need to separate the endpoint config from the SOAP action. Ditch the actionHeader variable completely and just use soapAction="" directly in your invokeRaw tag since your WSDL shows an empty SOAPAction. Also double-check that your namespace declarations in the SOAP envelope match your WSDL exactly. I’ve seen tiny namespace mismatches cause silent failures in Jelly SOAP calls, even when the same request works fine in other SOAP clients.