Bear Bibeault wrote:If it uses SOAP, it's not REST.
Agree. This is just a POC. And What i wanted to know was that is it feasible? I am running into some issues which I had not seen till i added the web service layer over my application
It's as feasible as trying to sell a red car as blue. If it's a SOAP web service, it can't be (honestly) called a REST web service.
So I'm not even sure what the "is this feasible?" is referring to? If you have a red car, sure, you can call it blue, but that's doesn't make it blue.
Tim Moores
Rancher
Joined: Sep 21, 2011
Posts: 2407
posted
0
You're writing a REST service which in turn accesses a SOAP service; is that correct? if so, it's most certainly still a REST service. Why wouldn't it be? And where do you see problems implementing it?
Ah...... horse of a different color! So you're writing a translation layer to create a REST API that leverages an existing SOAP service?
As Tim asked, why do you think there's a feasibility issue? Although I'd likely say that unless the existing processes are highly complicated, it'd likely be easier and cleaner to recreate the services from scratch as to perform a lot of translation code.
H Paul
Ranch Hand
Joined: Jul 26, 2011
Posts: 299
posted
0
Language is the source of misunderstandings.
The way I try read the OP's question:
1. I'm Restful webservice provider.
2. Upon recieve the request from the client, I being now a SOAPful Client, call a SOAPful web service provider.
I agree. Here's the link: http://ej-technologies/jprofiler - if it wasn't for jprofiler, we would need to
run our stuff on 16 servers instead of 3.
0
