Last updated Jun 4, 2024

JIRA Developer Documentation : RPC Endpoint Plugin Module

JIRA's SOAP and XML-RPC remote APIs were deprecated in JIRA 6.0.

Read the announcement for more information.

The RPC endpoint plugin modules enable you to publish new SOAP and XML-RPC endpoints within JIRA.

These endpoints allow you to expose your own remote web services to the outside world.

Here are two example RPC endpoint descriptors:

<rpc-soap key="soap" name="System SOAP Services"
    <description>The standard JIRA SOAP services.</description>

<rpc-xmlrpc key="xmlrpc" name="System XML-RPC Services"
    <description>The standard JIRA XML-RPC services.</description>

The first defines a SOAP service, the second an XML-RPC service. These objects (class="x") will be published via Glue or Apache XML-RPC respectively. The service-path element defines where in the URL namespace the services will be published. The published-interface element for the SOAP module defines which interface will be published (XML-RPC publishes all methods of the object).

Please take note that you also have to create a Component Plugin Module to avoid the client getting NullPointerException, e.g.

<component key="component-FoobarSoapService" name="Foobar SOAP Service Component" class="com.atlassian.jira.rpc.FoobarSoapServiceImpl">

<rpc-soap key="soap-foobar" name="Foobar SOAP Service" class="com.atlassian.jira.rpc.FoobarSoapServiceImpl">
    <description>Foobar SOAP service.</description>

You can learn more about RPC plugins from looking at JIRA's system RPC plugin. The source to this plugin is also freely available, and serves as an excellent learning resource.

You may also wish to see the Creating an XML-RPC Client and Creating a JIRA SOAP Client if you're interested in creating a JIRA remote client.

Rate this page: