JIRA 5.07 textfields in response XML

XMLWordPrintable

    • Type: Support Request
    • Resolution: Handled by Support
    • Priority: Medium
    • None
    • Affects Version/s: 5.0.7
    • Component/s: None
    • None

      Hi experts,

      we using JIRA 5.07 in our company and use the webservice method getIssuesFromJqlSearch( ).
      If there is an illegal character in some of the description fields we receive the following response:

      AXIS error
      Sorry, something seems to have gone wrong... here are the details:
      Fault - ; nested exception is:
      java.io.IOException: java.lang.IllegalArgumentException: The char '0xb' after 'Enable the maintenance side of the business
      Install and geo-tag equipment, including meters
      View asset schematics, history, dependencies
      Execute to guided workflows
      Generate notifications and work orders' is not a valid XML character.
      AxisFault
      faultCode:

      {http://schemas.xmlsoap.org/soap/envelope/}

      Server.userException
      faultSubcode:
      faultString: java.io.IOException: java.lang.IllegalArgumentException: The char '0xb' after 'Enable the maintenance side of the business
      Install and geo-tag equipment, including meters
      View asset schematics, history, dependencies
      Execute to guided workflows
      Generate notifications and work orders' is not a valid XML character.
      faultActor:
      faultNode:
      faultDetail:

      {http://xml.apache.org/axis/}

      hostname:coevi11

      So I expect that JIRA not support to save illegal characters or it should convert it to legal ones before it is send to the AXIS framework.
      At the moment we have so the problem that we can't continue with the data read because we didn't receive an useable response.

      Please provide a solution for that.

      Best regards,
      Martin

            Assignee:
            Unassigned
            Reporter:
            Martin Lindner
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: