Skip navigation

JIRA Transport Release Notes

JIRA Transport is a transport provider that allows your Mule and other integrated services to communicate with one or more JIRA systems easily.

This is the major release of this project, version 1.0. It is released on 3rd December 2007.

These release notes below cover: the major features and changes, system requirements, download guide, etc. Please use the navigation at the right hand side of this page to browse other topics. If you want to file any bugs issues or requests, please proceed to our JIRA.

What's New

JIRA Transport is simply an easy-to-use transport provider to enable integration between Mule and JIRA systems. These are the new features supported by this version:

SOAP without crap

To configure an endpoint to send a SOAP request usually requires you to define a number of parameters such as SOAP style, type binding and namespaces, this transport has gotten rid all of these unnecessary concerns so that you only have to care about the name of the method and the parameters (in JSON format).

See Transport Configurations#Endpoint Properties to quickly learn how easy it is.

Service Component and Transformers

The point of SOA and ESB is to enable a simple approach to services and data. This version is shipped with a JiraSoapServiceComponent and the following transformers:

  • HttpRequestToMethodInvocation
  • JsonToObject
  • JsonToXmlString
  • ObjectToJsonString
  • ObjectToMethodInvocation

You can have some play with these features. For instance, you can easily expose an HTTP endpoint to receive requests and return results in JSON format, if you are writing some front-end web components, this can be very useful.

See Transport Configurations#Configuring HTTP Receiver, Service Components and Transformers for more information.

Requirements

System and Environments

JIRA transport runs on Mule 1.4.x and it requires Java artifacts generated from your JIRA WSDL (via Axis WSDL2Java) to be in the classpath.

This ant script helps you to do the job of WSDL2Java.

Libaries

To ensure that this transport functions properly, JIRA transport requires the following libraries:

Downloading and Installing

You can obtain the binary distribution of this transport from the Downloads link at the left navigator. Once you have gathered all the required JAR artifacts:

Copy them to the classpath, e.g. $MULE_HOME/lib/opt and you will now be able to use them in your Mule configuration file.

Download the binary and source distributions from our repository.
See Transport Configurations to learn about how the connector is configured.

Other Changes

These are no other changes as this is the first release.

Known Issues

These are the known issues in this release, please report to our issue tracker if you discover any new ones:

  • ObjectToJsonString transformer returns an Exception payload at its best effort for the cause stack. There is also a harmless bug related to this transform reported at JIRA-6.

Frequently Asked Questions

See Frequently Asked Questions instead.

Other Resources and Links

The following links contain useful information about this transport:

If you have discovered a bug or want to raise a feature request, we welcome you to create an issue at our JIRA. The page also provides information on our development road-map, past and present issues, etc.

You are also welcome to read our Blogs and comment on them.

Adaptavist Theme Builder Powered by Atlassian Confluence