Error while integrating JIRAExtendedWebService with the JIRA Soap Client

24 views
Skip to first unread message

Rajpal

unread,
Jan 16, 2011, 2:44:50 PM1/16/11
to jira-extended-webservice
I followed the instructions for the JIRAExtendedWebService and set up
the source for the plugin and compiled it using the atlassian
tools ..

I was now trying to connect my SOAP Client ( which I got from
http://confluence.atlassian.com/display/JIRA/Creating+a+SOAP+Client
)to the JIRAExtendedWebService by importing the package "import
org.sharedSpace.jira.webservice.* " , but while doing the command
"atlas-mvn -Pbuilclient", I am getting the following error ..

<snip>

ERROR BUILD FAILURE
INFO
INFO Compilation failure

/Users/rajpalparyani/Documents/Thesis/plugin1/jira-soapclient/src/main/
java/com/atlassian/jira_soapclient/SOAPClient.java:11,0 package
org.sharedSpace.jira.webservice does not exist

/Users/rajpalparyani/Documents/Thesis/plugin1/jira-soapclient/src/main/
java/com/atlassian/jira_soapclient/SOAPClient.java:219,34 cannot find
symbol
symbol : class SoapExtension
location: class com.atlassian.jira_soapclient.SOAPClient

/Users/rajpalparyani/Documents/Thesis/plugin1/jira-soapclient/src/main/
java/com/atlassian/jira_soapclient/SOAPClient.java:243,36 cannot find
symbol
symbol : class SoapExtension
location: class com.atlassian.jira_soapclient.SOAPClient

/Users/rajpalparyani/Documents/Thesis/plugin1/jira-soapclient/src/main/
java/com/atlassian/jira_soapclient/SOAPClient.java:84,3 cannot find
symbol
symbol : class SoapExtension
location: class com.atlassian.jira_soapclient.SOAPClient

</snip>

Could someone please tell me what I am doing wrong here ? Any
Responses will be highly appreciated ..

THanks,
Raj

Ath

unread,
Jan 17, 2011, 2:40:19 AM1/17/11
to jira-extended-webservice
You don't need the source of the plugin to connect to it's SOAP
interface. Please update your knowledge on SOAP and how to use it.
As it's not part of the Atlassian SDK you won't be able to import the
classes of this plugin, that's what all these errors are about.

/Ath

On Jan 16, 8:44 pm, Rajpal <rajpalpary...@gmail.com> wrote:
> I followed the instructions for the JIRAExtendedWebService and set up
> the source for the plugin and compiled it using the atlassian
> tools ..
>
> I was now trying to connect my SOAP Client ( which I got fromhttp://confluence.atlassian.com/display/JIRA/Creating+a+SOAP+Client

Rajpal

unread,
Jan 18, 2011, 12:59:49 AM1/18/11
to jira-extended-webservice
Hi Ath,

I actually did not understand all the things you said .. could you
please explain a little bit ..

After reading a little bit, it looks like I have to publish the plugin
and create a wsdl for the same which would have to be queried first by
the soap client. For that to happen the jira side should have some
knowledge about the extended JIRA webservice... I just don't know how
to do that .. Could you please shed some light on this ..

I already have run my soap client ( just some new functions which
query the existing functions provided by JIRA soap server ) .. so all
the things are not new to me ..

Please help me out and let me know you want more information from
me ..

Looking forward to your response.

Thanks,
Raj

Ath

unread,
Jan 18, 2011, 2:28:21 AM1/18/11
to jira-extended-webservice
This is a Jira plug-in, that needs to be installed on your Jira
server. The instruction on the wiki page say: "Simply drop this jar
file in the WEB-INF/lib directory of your Jira installation." The wiki
can be found here: http://code.google.com/p/shared-space
After the installation-part the Jira service needs to be restarted.
(Be sure that the RPC service in Jira is enabled, or another restart
is required after enabling that) The plugin is tested by myself (and
others) on Jira versions 4.0 to 4.2, and some others have been using
it on Jira 3.13, afaics, but I never used that version of Jira.
Then the SOAP interface is available at http://<your-jira-url>/rpc/soap/sharedspace-s1v1
and the WSDL can be seen bij adding ?wsdl to that url (use internet
explorer on Windows for a usable display, don't know what linux
browser displays it correctly)
There is no need to create a WSDL, as the SOAP interface is published
using Axis2 that auto-generates the WSDL for you.
Your client-development environment needs to connect to that url to
create a local stub that you can call the methods on.

What are the methods you need to use this plug-in for?

HTH
Reply all
Reply to author
Forward
0 new messages