I need to develop a web services and it needs to be hosted in Adobe CQ. I knew that CQ consume web services from other systems. We will need to create a OSGI bundle for this. I heard that Adobe not recommended to develop web services in CQ. Is it good approach to develop a web services in CQ itself? What happens if we host it in CQ?
Please share your feedback.
Thanks,
Related
I am new to Web development. And hence, if the question is dumb, please be polite. For creating my application, I had to take a decision of whether writing a web service or a web application. After searching a few questions in stackoverflow, I came to know that, web service is something which doesn't involve human interaction. And web application is what human uses ( the UI/web page kind of stuffs ).
But lately, I saw gmail is a web service ( email service ). But I was confused from here on, because, gmail provides a UI, and human interactions do occur. And from there on, I got confused again.
So what I figured out from this is, gmail website is like a web application for users to use directly. The web application in turn uses the web service provided by Google for email. Is my understanding right? So can a web application be a client for web service?
If I am wrong somewhere, please do correct me. I hope to be clear after someone throws light on this with some good example. Thanks in advance.
You are quite right. Basically a Web Service has several endpoints over HTTP (normally) that provides data (generally in JSON or XML) and are meant to be consumed by Web Clients. Sometimes the are also called Web API's (Application Program Interface).
A Web Application is quite similar to a Web Service but it provides an interface where the user can interact with. Usually Web Applications are consumers of Web Services or Web APIs.
Following your example, Google email is could be considered as both, a Web Service and a Web Application. It is a Web Service because it provides a set of HTTP endpoints that works independently of its Web UI Application (GMail). In fact, you can find third party Web Apps that interact with the Google email Web API.
This concept is very important when designing Web Solutions. Ideally you want to design and implement a good Web API, usually a RESTful Service (in JSON/XML). Then you or others will be able to implement different types of applications (Web, Mobile, etc.) because of this API.
I just started learning web services. In bottom up approach, I have found some examples without being deployed in any application server. I mean a standalone web service application.
Here is an example of such type.
I have also given a try and done a walk-through of deployable simple web service examples.
So far to my learning of web services, I got to know that firstly, bottom-up- approach is not recommended. Now, in bottom-up approach, this standalone web service. When is it applicable to follow standalone web service procedure?
Endpoint.publish();
I guess, this approach is provided just for beginners and not to follow as a real-time practice. Is my interpretation correct?
I would make my application as a standalone web service if it will have multiple clients like:
Web Client via a web browser
Mobile App Client
Desktop Client
Then I could build every one of them alone using whatever the technology I prefer, and make it consumes my standalone web service.
For example, You could imagine the guys behind Twitter started developing it by building their core system as web service, then they build an independent web interface application for it, then they built the Twitter Android and iPhone APP, and another one came and introduced a Twitter Desktop client like Tweetbot and TweetDeck ... etc
I need to develop a secure web services that could be used by SSIS. The web service expose data from a SQL server.
Where should I start?
Any suggestion for technology to use? (I am a C# developer.)
I quite didnt get the difference between a regular web service implemented either through spring or axis versus Remoting.
If my question is not at all related, I am just confused between spring web services vs spring remoting. When to go for remoting and when to go with a web service.
Appreciate your answer
Spring Web Services is a dedicated Spring Project (using Spring's own Web Service technology), whereas Spring Remoting is a common approach of integrating different third party remoting technologies.
Spring-WS is always contract-first, while Spring Remoting is often code-first.
Your choice of using Spring remoting or web services depends on whether you want to use SOAP or not.
All Spring services should start life as interface-based POJO services, of course. That way you can worry only about implementation and interface; remote access can be an afterthought that way.
Once your Spring POJO service is tested and running, you can choose between a myriad of remoting choices: EJB (RMI-based; Java-only clients), HTTP (any client that can create an HTTP client), web services (SOAP and WSDL), etc. Your choice depends on the types of clients you anticipate and the wire protocol you'd like to use.
I want to connect from a .Net Micro Framework application to an existing web service hosted in WCF on a Windows Service / IIS. Is this possible and could someone please point me in the right direction with regard to the documentation on how to do this?
Thanks
Maybe this articles can help you
"Implementing Web Services on Your Devices" (.Net Micro):
http://msdn.microsoft.com/en-us/library/hh423016.aspx
"Connected Devices Using the .NET Micro
Framework": http://msdn.microsoft.com/en-us/magazine/gg232761.aspx