Flex/Jira SOAP Webservice issue resolved

I guess I just needed to put this aside for a day and come back with fresh eyes. Another look at the log files gave me what I needed. There was an exception in the log about a NumberFormatException indicating that the String NaN couldn't be parsed into a number. A breakpoint in the SOAPEncoder.as file indicated that the NaN was being passed as the value of the "votes" property. So explicitly setting that value to "0" fixed the problem.

I would never have expected that I needed to set that property when creating a new issue.

But... it is working now, so expect to see a simpler way to submit bugs and feature requests coming soon.

Flex/Jira SOAP Webservice Problems continues - any suggestions?

Well... since my last post I have been trying to successfully create and issue in Jira from Flex. Desipite the problem I found in my last post, which allowed me to retrieve data successfully from Flex, I am stumped when it comes to creating issues. Here is what I am doing... if you happen to have any suggestions, please comment here or email me directly.

  var req:CreateIssue_request = new CreateIssue_request();
req.in0 = token; //from login request (which works fine)

  var issue:RemoteIssue = new RemoteIssue();
issue.project = "KLOK";
issue.summary = "My new defect";
issue.type = "2";
issue.assignee = "rmckeown";
issue.description = "this is a description on the new defect";
issue.priority = "3";
issue.status = "1";

      req.in1 = issue;

jira.createIssue_request_var = req; //jira is an instance of my SOAP service.
jira.createIssue_send();

Any ideas?

Jira/Flex SOAP Webservice Problem

If you have been following my latest posts about Klok, you know that I am evaluating Jira as my tool to track bugs. I thought it would be cool to have an area of the Klok website show some statistics regarding the open defects as well as a way to quickly submit a defect. I figured this would be easy to implement but it is taking longer than I thought.

If you are developer the solution is shown below. 

So I enabled the SOAP service and figured it would be simple to hook up Flex to the Jira SOAP Webservice. Using the tools to generate all the necessary code in FlexBuilder I assumed I would just implement the calls to get the data and I would be off an running. Unfortunately that was not the case. 

I started with trying to just list the projects from Jira and was confused when the only data coming back was the project description. After about 5 painful hours of digging into how the generated code works. I noticed that there was code in the Base[servicename]Schema that defines the complex type for RemoteProject... which defined the sequence of properties in a different order that they are being returned by the Jira SOAP webservice. 

If you change the order in the definition to match the order in which they are being returned all seems to work.

After fighting this for so long I decided I would submit the defect to the Flex bug site only to find out that it was already there. UGH!