We have a native service / daemon in written C++. We are looking to provide a Restful web-service to control / setup the service.
Assuming that the web-service is either implemented in .Net or Java, what is the best way to communicate with the native service / daemon.
Related
If I use a standalone application to interact with a Restful web service I use Apache HttpClient or its Fluent API.
How do I interact with a web service using a web application or from another Restful web service?
Do I again go back to Apache HttpClient?
A web service client is a web service client, no matter if who's doing the consuming is a standalone application, a web application or even another web service. You could consume them how you see fit:
use a JAX-RS aware client like the RESTEasy client framework (I see from your profile you are using JAX-RS);
use a (generic) REST aware client like Resty;
use Apache HTTPClient;
heck, you could even use java.net.URL :)
I have a working JBPM project that i want to expose as a web service so from my server i can call that web-service. So please let me know is there a any way to expose a JBPM project into a web service.
By default, you can use the jbpm-console service to expose the processes you have deployed there as a REST service. You can also expose your project yourself as a web service using for example the camel integration component (and using camel to set up a WS endpoint) or by writing a custom wrapper yourself.
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 would like my Qt app to expose a service to another app written in .Net using WCF.
Is there any support in Qt for implementing WCF services?
AFAIK there is no 'native' Qt support for WCF or extensions; however as you know WCF can consume and expose a web service (in addition to a WCF or remoting service, etc.) All you need to do is expose it as a Web Service for the other .NET app to consume.
But that brings up an interesting aspect; usually you would write a windows service (I presume you are on Windows) which is exposed as a Web service rather than one via Qt. Qt is not ideal as it is a GUI framework (and a very good one); you will get into a few interesting situations as discussed here. It is usually easier to consume a web service with Qt as shown in this example.
Do you have the option to expose your service using some other stack such as ASP.NET or WCF or Java?