How and which web service can I call to create a new profile in SonarQube?
I've checked both api/profiles and api/qualityprofiles but could not find it. I am using Sonarqube 4.4.
This is currently not possible, but this web service will definitely be created when we work on the redesign of the Quality Profiles page.
You can watch and vote for the following ticket: SONAR-5851
Related
I am new to developing web services using java. I have an academic project where I need to do dynamic service composition. For that I can't directly create a service-client for a particular service because if I do so then that client will call that particular service only. Client need to search various web services and then out of those services select any one at run time and also call that service at run time.
I was able to develop the web service(JAX-WS) using Eclipse(indigo), I also created the client for that web service and every thing is working fine. Now my problem is that while creating the client I am hard coding the client to call that particular web service only(since I am creating the client using the WSDL file of the service). However I actually need to call any one of the searched service, but for that I need to publish the service some where then discover it and then call it.
I tried publishing the service to juddiv3. But on juddiv3 I could only publish the sample service supplied with the juddiv3. When I try to publish service created by me then it is not getting displayed in the group of published services.
Is there any other UDDI server which I could install on my local machine and then publish and discover the service from that. Also I was not able to figure out how to create a client that will modify itself at run time to call any one service out of various searched services.
Kindly provide the necessary steps and code.
Thanks
You can use jUDDI (http://juddi.apache.org/ ).
juddi is based on UDDI v2.0, v 3.0 .
Here, you can publish as well as discover your web service.
For integration, you have to make some application which integrates with jUDDI.
But I think for your academic project, and for your purpose, jUDDI is best suitable! ( :) )
jUDDI has a boat load of examples in the source code trunk. You may want to check them out. It's difficult to guess what the problem is from the little information you've provided. Consider contacting the jUDDI team for further assistance. http://svn.apache.org/repos/asf/juddi/trunk/juddi-examples/. There's also additional document for working with UDDI in the jUDDI user's guide, which is at the jUDDI web site
You cannot directly publish on jUDDI. You need to create publisher entities in jUDDI server also. You'll find Rename4Sales and Rename4Marketing examples in 'Classes' folder in the standalone server's juddi application. Use these XMLs as your basis and create your own entity. You also need to configure the server's login credentials.
I suggest you follow the tutorials on jUDDI blog.
DNN Ver 5.6.7
.NET 3.5
Anyone know of a way to access/update user accounts on a DNN site from another web application?
My goal is to allow customer service to update an employee's DNN password from an intranet app (that includes some other employee related, non-DNN data), but I'm not having any luck. I tried adding a simple web service to a virtual directory (as described here) to the DNN site, hoping the web service would then have access to all things DNN, but I'm not able to create instances of the UserInfoController - it's not instantiating the MemberProvider object.
UserController objUserController = new UserController();
UserInfo objUser = objUserController.GetUser(portalId, userId);
Each time, the objUserController object shows null for DotNetNuke.Security.Membership.MembershipProvider
Both the DNN site and our internal web app are hosted on the same server. Any suggestions are appreciated.
EDIT: In addition to all the DLLs in the DNN bin folder, I also copied everything from the DNN web.config into my web service web.config that looked DNN related
if your WebService is inside DNN, this code must work:
UserInfo objUser = UserController.GetUserById(DotNetNuke.Entities.Portals.PortalSettings.Current.PortalId, userId);
If your intranet app is running on ActiveDirectory, I would look at some of the available ActiveDirectory integration modules.
If you can wait until DotNetNuke 6.2 comes out, it will include a built-in services layer which will allow you to authenticate and interact with DotNetNuke objects like users.
I did this via http://iweb.adefwebserver.com/.
I added a web service method that took advantage of all the user related features in the DNN API (UserInfo, UserController, RoleController, etc.).
We have a need to add sitecore items programmmtically. To achieve this we are basically creating new WCF Service as the standard webservice provided by sitecore is not serving our purpose. The new WCF service created in VS2010 is pushed/published to same folder as standard webservice(sitecore/shell/webservice). For some reason the service doesn't work at all throws configuration errors.
Could anyone let me know where exactly this custom service should be deployed.
I had lots of issues deploying both WCF and old-style (.ASCX) web services in a Sitecore-controlled application. I never was able to find a satisfactory solution, even after speaking with their tech support. I ended up creating my own HTTP handlers to accept POST data and used those instead of WCF. I know it's not the best solution, but it worked.
Background:
I'm building a small application that will be run daily, pulling data from our own in-house databases and sending it over to our corporate Salesforce instance. I've built a custom object (called Marqui_Instance) in our Salesforce instance to house the data. The app will be creating a couple hundred of these, and attaching them to various Account records.
The Problem:
Our Salesforce instance is Professional edition, which means I can't generate the WSDL for our instance, which makes me think I'm not going to be able to develop code that can create/edit/delete Marqui_Instance objects.
Before I start floundering around in the dark, I thought I'd post on here for advice. The only thing I can think of is to create an identical object in a Salesforce developer account, and use the WSDL from there... but then when I go to deploy the code in production, will it work? I'm scared that the WSDL from my dev account will have some guids or something similar, and my code will only work against the dev account.
If you get your application certified by Salesforce they will provide you with a "Partner Application API" token. Using this when establishing the Salesforce API session will allow your application to work with a professional edition org.
Alternatively, you can also obtain API access to a Professional Edition org by paying an additional fee. You will need to contact your salesforce.com sales person.
Update: Apparently the functionality is enabled by Salesforce internally using the informally named "Black Tab".
See also: Re: Use of the API and Salesforce.com Professional Version
Access to the web services API for Salesforce is only available in Developer, Enterprise, and Unlimited Editions.
I believe that you aren't allowed to login to the API, so even if you managed to generate a WSDL it wouldn't work.
See the full edition comparison chart [PDF].
I'm getting an error when attempting to call SharePoint's webservices on one of our platforms. To start, we have Development (DEV), Testing (QA) and Production (PROD) SharePoint servers. The QA and PROD servers are pretty much identical. We have an ASP.NET web service that sits out as a seperate application on each of them. Our data entry forms hit the web services to insert/update into a SQL database and in some cases make calls to some of SharePoints web services (lists, dws).
We’re having trouble calling SharePoint’s web services on PROD from our web services however, have no problems on QA(or DEV). In our web service code we have a web reference to the SharePoint web services (lists and dws). We attempt to call these web services to create list items/folders when a new entry is made through one of our forms. On QA, there is no problem creating the list items/folder. The form is filled out, calls our web services – which call the SharePoint web services and the list item/folder is created.
On PROD we get the following error when we attempt to call the SharePoint web services:
Unable to connect to the remote server
at System.Net.HttpWebRequest.GetRequestStream()
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
...
However, to make it more interesting, if I call the PROD SharePoint web services directly from my personal computer I have no problem creating the list items/folders. We only have the problem when our web service attempts to call the PROD SharePoint web services. We’ve looked through many different web.config files looking for differences on QA and PROD and are yet to come up with anything.
If anyone has any pointers, they would be greatly apppreciated. Thanks.
Update: I just attempted to refactor the above method to use the SharePoint Object Model API and I'm getting an unauthorized error. When using the Object Model API the credentials do not seemed to be passed properly, because it's attempting to use the MOSS Server credentials. Is there any way to tell it which credentials to use as you do with the web service api?
docLibList.Credentials = System.Net.CredentialCache.DefaultCredentials;
Thanks.
Sean,
I'm not sure I completely understand your calling pattern, but if you are indeed looping back to web services on the same box, you might be running into the infamous loopback issue:
https://serverfault.com/questions/32345/ie-8-authentication-denied-on-local-sharepoint-site/32485#32485
In short: executing hostname-based HTTP calls that loopback to the server from which they're issued can get blocked. If the loopback issue is in-play, you'll be able to call the web services in PROD from another box ... but not from the PROD box itself (i.e., looping back). I think this is consistent with the behavior you described above.
If Windows patch levels are different between your environments, it might explain why your code is failing in PROD but not in your other environments.
I hope this helps!
This probably is not the problem, but is your reference to the web service pointing to the production server correctly. I had a problem before when trying to access a SP service that was referenced incorrectly. The dev server I was pointing to was on a seperate domain and could not be found.
Regarding the update to your question about the unauthorized error using the object model:
Depending on the context that your code runs in you will sometimes need to elevate privileges. See this Elevation of Privilege MSDN article for details (also note the community comment at the end). There's also a Visual How-To.
Another method is to create a new SPSite object using a SPUserToken object. There is more information in this blog post by Daniel Larson. For the system account this would be done with the code:
SPSite site = new SPSite(SPContext.Current.Site.ID,
SPContext.Current.Site.SystemAccount.UserToken);
By the way, this would be better in its own question next time so that it can be correctly voted and answered.