mulesoft/jira-connector — Issue #21: Allow username to be specified later
Author: dougbass
Created: 2012-01-24 20:19:04+00:00
State: open

According to this page from MuleSoft:

http://blogs.mulesoft.org/devkit-feature-spotlight-connection-management/?mkt_tok=3RkMMJWWfF9wsRonvaXJZKXonjHpfsX57%2BgrUaG%2FlMI%2F0ER3fOvrPUfGjI4ASMZjI%2FqLAzICFpZo2FF1D%2ByQb49G7g%3D%3D

You can specify the connection parameters such as as username and password on a later call (like create issue). The reason I'm being forced to do this is in my flow I use spring to load a class of connection settings like this:

And then I call the jira-config like this:

But for some reason the jira address is not set correctly. I've even set a breakpoint in my getUrl method to ensure the return value is correct, but it still fails with the error:

Root Exception stack trace:
javax.xml.rpc.ServiceException: java.net.MalformedURLException: no protocol: #[groovy:ConnectAllConfig.getApplication().getUrl()]/rpc/soap/jirasoapservice-v2
at com.atlassian.jira.rpc.soap.jirasoapservice_v2.JiraSoapServiceServiceLocator.getJirasoapserviceV2(JiraSoapServiceServiceLocator.java:58)
at org.mule.module.jira.api.DefaultAxisPortProvider.getService(DefaultAxisPortProvider.java:35)
at org.mule.module.jira.api.AxisJiraClient.getService(AxisJiraClient.java:891)
+ 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything)