I used SOA Client extension for test my websevices and see results of webservices, but two days ago I cannot use SOA Client extension in firefox, it doesnt work.
There is any addon for soap webservices like SOA Client in firefox?
I want to see fields in webservices like textbox not xml.
Related
How can I perform test queries using SOAP web service? Which tools or something I should to use? I'm newbie on this topic. I have url, password, login name and I would like to see result of queries in XML format.
As far as I know the most commonly used tool for testing web services is SOAP UI. This allows you to test just about all aspects of a soap API. From just a basic test request to complete Test Suites
SOAP UI can be found here.
I am looking at SharePoint web services and would like to know the best way to work with web parts. I have figured out most of the other stuff we will need but the functionality around web parts and the SharePoint Web Services seems complicated. So how do I
Retrieive a particular web part with HTML content? Is this possible?
Find out what web parts are on what pages?
I know that I can get the rendered html for an entire page through web services (although why that is exactly useful when you can retrieve the web page directly I'm not sure.) but would like to know if it is possible to embed web parts in external web sites through SharePoint Web Services.
"Web parts" are a means of "programming" Sharepoint. They are to Sharepoint much like "controls" are to Visual Basic, or "views" are to Android.
They're a creature of Sharepoint - I can't imagine you'd use them on an Apache server on a Linux host, for example.
Sharepoint web services, however, are intended to be a good way for Sharepoint to communicate with non-Microsoft technologies (like Java, for example).
If your "application" involves a heterogeneous mix of web servers and platforms, then Web Services is probably the way to go.
If your "application" resides exclusively on the Sharepoint server, and your "clients" just browse to it (preferably, browse to it with IE), then web parts might be a good choice.
I am familiar with SOAP web services, and have done some PUT/GET/POST verbs in REST web services. Somewhere I read that your REST web service can return a code if something goes wrong at the web service, but can it return twice?
By that I mean: supposed your REST web service is querying a database and it is doing a lazy load, so it is taking a while. You intend to return an array of values from the database back to the client that called the REST web service. But while the REST web service is working on your database query, can it return a string that says "Query is 10% complete, please wait" or something like that? Can the REST web service call another web service that somehow communicates back to the client this information?
I doubt this is possible, otherwise I would have seen it, but I ask anyway.
Target platform is Visual Studio 2010 Professional with C# and MS Sql Server 2008
You could look at COMET, which according to wikipedia:
...is a programming technique that enables web servers to send data to the client without having any need for the client to request it. It allows creation of event-driven web applications which are hosted in the browser.
There are a number of articles on the web about doing this plus a couple of frameworks on sourceforge and github. However this is not trivial. I know it is possible with REST because a previous employer of mine has several real-time feeds based on RESTfull endpoints using COMET for push.
See here:
http://www.aaronlerch.com/blog/2007/07/08/creating-comet-applications-with-aspnet/
http://sourceforge.net/projects/emergetk/
https://github.com/Oyatel/CometD.NET
What is the difference between using a "Web Service" and calling a server page such as JSP/ASPX?
To me it looks like a Web Service is just a framework around the server pages. For e.g. I can have a JSP page that takes:
mypage.jsp?method=getupdate¶m1=23¶m=44
(I can also send these variables through POST)
In my JSP page I can call the appropriate method based on the value of "method" and return a value back to the caller client app. Is this the raw form how a Web Service actually works? OR is there more to a Web Service call like someone told me that when you call a page, it is rendered but a Web Service is not rendered. But What if I remove the HTML code from JSP page then?
So when we say XML Web Service, the difference is that the client and the server both wrap/unwrap the requests/responses using XML and POST it to the Web Service page.
Web Services are a well defined set of standards defined by the W3C and other relevant bodies, which mostly define an architecture that runs over a network to communicate diverse applications while ensuring interoperability, discoverability and some other relevant criteria.
You can certainly create a server page just for your application without SOAP or XML-RPC. It's just that you shouldn't call it a "Web Service" unless it outputs SOAP or XML-RPC and provides a WSDL description for itself, because that leads to confusion and show you don't know what the "standard Web Services" mean.
You are correct to say that web services are a layer on top of the server pages. One of the common types of web services are SOAP web services that wrap requests and response into XML to achieve interoperability between different platforms/frameworks.
Sites like Facebook and Flickr that have much the same kind of public APIs are calling them 'web services' and I don't see that you're doing anything different.
Vinko seems to have some objection to polluting the 'Web Service' moniker but there's plenty of room under the W3 definition of a web service to include what you're doing.
As for Web services having to output SOAP or XML and provide a WSDL? I think there's a few REST advocates that would argue that point.
Im making mobile application in java me and I want to have server side from where Ill get some information for the application (not to have much information in xml file in the application).
I dont have much experience with servers, so I would like to know how to deal with it.
Probably I should make some web services.
Im working in NetBeans 6.7
Thanks in advance!
Milan
Assuming you want to stick with Java, I would implement your server side as a simple Servlet. If all you want to do is send an XML file to the client I think using a proper web services stack is probably overkill and will over complicate things.
Using this approach your mobile app simply makes an HTTP connection to your Servlet, which responds with your XML file.
In fact, if it's a static XML file you don't need any kind of server side code, any web server would suffice.
The Glassfish application server that probably comes with Netbeans will let you run a Java servlet on your local computer.
Accessing it from a J2ME emulator running on the same computer is easy.
Accessing a servlet from a MIDlet running on a real mobile phone is more complicated.
I would suggest looking at Google App Engine for easy deployment of a test server that can be accessed from a mobile phone.
I recommend you to use Http Post instead of Web services. Some mobile devices does not support web services (defined in JSR 172)