I am using Atlassian JIRA™ (Professional Edition, Version: 3.0.3-#75 and Netbeans IDE 7.1
But when trying to validate a connection to Jira from netbeans it gave me this error "Jira RPC services are not enabled"
while I have enabled it and also I enabled allow remote calls in Jira
To be more specific "RPC JIRA Plugin" that I have installed is
The standard JIRA RPC services, both SOAP and XML-RPC.
Plugin Version: 1.1
JIRA version: 3.0
It has
System XML-RPC Services (xmlrpc)
The standard JIRA XML-RPC services.
RPC Field Coordinator (rpcFieldCoordinator)
Issue Service (issueService)
User Service (userService)
Token Manager (tokenManager)
System SOAP Services (soap)
The standard JIRA SOAP services.
Magic Field Validator (magicFieldValidator)
Project Service (projectService)
My global configurations are:
Allow users to vote on issues ON
Allow users to watch issues ON
Allow unassigned issues ON
Cache issues ON
External user management OFF
Logout Confirmation Never
Use Gzip Compression OFF
Accept remote API calls ON
BTW, it is not just netbeans, I got same problem with other tools as well to connect to jira
I will apreciate if my answer be found ASAP .
Thanks
Answering an old question, but I thought someone else might find this useful.
I got the same error today setting up an issue tracker in NetBeans 7.2 and I eventually tracked it down to NetBeans not being able to correctly resolve (using DNS) the (local) host name that was running our JIRA server. When I changed NetBeans to use 'No Proxy' in the main settings, it worked fine.
EDIT: Note that as of version 7.0 of the JIRA server, Atlassian have depracated the SOAP/XML-RPC API, so the JIRA Plugin for Netbeans no longer works. :-(
Related
Can some one please help me connecting to JIRA 7 in SonarQube JIRA plugin ?
After giving correct inputs for
server url, username, password, JIRA Project key
Its not working and show error as "Impossible to connect to the JIRA server ".
sonar log also does not show any error related to this.
SOAP base url in JIRA plugin setting in SonarQube is blank and also accessing http://{my jira url}/rpc/soap/jirasoapservice-v2 give 404 error.
even though its enabled in my JIRA 7.
In below SonarQube page, it seems its last update is in December related to version descriptions.
http://docs.sonarqube.org/display/PLUG/JIRA+Plugin#JIRAPlugin-Requirements
http://docs.sonarqube.org/pages/diffpagesbyversion.action?pageId=1442016&selectedPageVersions=101&selectedPageVersions=102
Searching on Google finding few post where it says
"The JIRA Plugin is not compatible with JIRA 7 or newer."
SonarQube cannot connect to JIRA 7 with REST API
"Jira SOAP API has been removed in Jira 7"
https://github.com/SonarSource/sonar-jira/issues/3
So please let me know if anyone khows how to connect to JIRA 7 in SonarQube JIRA plugin.
My SonarQube verion is 5.2 and also checked with 5.4.
SonarQUbe JIRA plugin version is 1.2.
My JIRA version is 7.2.0-OD-05-030.
Thanks,
Sandeep
You found out the answer already: Jira Plugin is not compatible with Jira 7. There is no workaround/fix, otherwise it would already be mentioned in the related GitHub issue.
Note that the underlying functionality of linking SonarQube issues to 3rd-party ticketing systems is being dropped altogether (SONAR-6717). Equivalent grouping/planning of issues can be done using tags and filters, see this blog post for more details.
Mule id plugin Url is not working. Can any one help to get an alternate url for the same plugin.
http://dist.muleforge.org/mule-ide/updates-2.1.x/
This url is also mentioned in the below tutorial.
http://www.mulesoft.org/documentation-3.2/display/32X/Installing+Mule+ESB+3+and+the+Mule+IDE
Below is the error which i am receiving after accessing this url in browser.
Network Error (tcp_error)
A communication error occurred: "Connection refused"
The Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time.
For assistance, contact your network support team.
Mule version 2X uses the url :- http://dist.muleforge.org/mule-ide/updates-2.1.x/ and for Mule version 3X the url :- http://www.mulesoft.org/documentation-3.2/display/32X/Installing+Mule+ESB+3+and+the+Mule+IDE is being used.
You need to check the version of Mule you are using and need to use the url that matches your Mule version.
If you are using Mule Enterprise edition you can take support from the MuleSoft Support, else if you are not using Enterprise you can post the issue in their forum
I seriously doubt there is still support for the Mule IDE, it was deprecated in favour of Mule Studio (that then became Anypoint Studio).
Do you really need to do a new development on Mule 2.x? If not, please consider using the much better Anypoint studio. If you need to stick to the 2.x version, you could just use a vanilla version of eclipse that will take care of the the autocompletion and then export to the apps directory of a running mule container for a hot deployment.
I've always used eclipse before, but I'm using Netbeans for the first time because of it's integration with Web Service clients.
However, after following multiple tutorials, the way to add a web service client is to:
https://netbeans.org/kb/docs/websvc/flower_swing.html
Make a new project
Right click on your project, New->Other->Other->Web Service Client
However, I do not have the web service client option available, not sure what I am doing wrong.
Please mention the net beans version you have. You should use newer version of the IDE to use latest features.
For other developers who will face this problem like me, I will leave my answer here.
I'm currently using Apache NetBeans IDE 11.0 and it's in Web Services -> Web Service Client. If you still cannot find it, just use filter feature. I found it with filter.
I am new to Web Services. I was trying to publish a JAX-WS Web Service to apache juddiv3 using eclipse(indigo) Web Service Explorer. But each time I try to publish it following error is produced:
IWAB0135E An unexpected error has occurred.
UDDIException
Message part {urn:uddi-org:api_v2}get_authToken was not recognized. (Does it exist in service WSDL?)
I am using following components:
(i) Eclipse Indigo (EE version).
(ii) juddi-portal-bundle-3.1.2
(iii) Windows 7
While publishing the web service I am using following entries under the 'actions' section of the eclipse 'Web Service Explorer':
Publish=Business
Publication Format=Simple
Publish URL= "http://localhost:8080/juddiv3/services/publish"
UserID = root
Password = Root
Name = Business1
Many times when I press 'Go' button then 'Please wait. The operation is still in progress' message is also displayed even after a long time.
Kindly help me with this issue.
Kindly suggest if there is any other framework other than juddiv3 which could be used to create private UDDIs on local machines.
Thanks
Its a known issue the eclipse plugin. A bug has been filed.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=307202
FYI, the jUDDI team is working on adding v2 endpoints to the v3 server. This use case is one of the drivers. It's almost in a working state now and will be released with the 3.2 version of jUDDI.
I'm trying to host nuget on my Amazon EC2 VPS, and I'm having issues.
I've followed the instructions here ( Hosting your own NuGet Feeds )
I've read this thread ( NuGet: remote server returned an Error(403) Forbidden ) along the same lines.
I'm not running TFS
It "could" be a proxy issue, but I'm not entirely sure how to check.
My NuGet feed is located at http://nuget.infinitas.ws. You'll notice that both http://nuget.infinitas.ws/nuget/Packages and http://nuget.infinitas.ws/Packages are throwing errors.
Any help with this will be greatly appreciated.
You are probably running the NuGet.Server in a Web Site-project. Try to run it via an ASP.NET Web Application instead (in Visual Studio you can create one via File -> New -> Project -> ASP.NET Web Application)
Have you tried the latest version (1.5)?
The release notes include some changes related to proxy authentication:
Support for Proxies that require authentication
When using NuGet behind a proxy that requires authentication, NuGet will now prompt for proxy credentials. Entering credentials allows NuGet to connect to the remote repository.
I realize I'm a little late to the party but I've just spent a frustrating couple of hours with the same problem.
I found that switching the Application Pool from "Classic" to "Integrated" fixed the problem