Comments on: WCF POX, JSON and SOAP Coexist

By: Admin

Admin — Wed, 14 Jul 2010 21:27:32 +0000

It should be the same way to handle the exceptions.
There is no difference at the code level( c# ), the difference is at the configuration level. e.g. which endpoint, binding do you use for talking to the webservice.

By: Bunty

Bunty — Wed, 14 Jul 2010 18:42:37 +0000

What is the best way to handle exceptions for both SOAP and REST together?

How do you differentiate between SOAP call and REST call to a specific operation? so that we can handle them appropriately and send proper response back such as custom fault for SOAP and some standard Http response back for REST type of request.

This is something very urgent and quick help would be really appreciated.

Thanks in advance.

By: admin

admin — Fri, 09 Jul 2010 22:33:59 +0000

you will need TestService.svc file for your service implementation and the baseAddress=”http://localhost:81/TestService.svc”
So the endpoints are
http://localhost:81/TestService.svc/soap
http://localhost:81/TestService.svc/pox
http://localhost:81/TestService.svc/json

By: Bunty

Bunty — Fri, 09 Jul 2010 20:02:46 +0000

What would be difference if I am looking to host this service with multiple endpoints in IIS? A quick answer to this would be really helpful.

Thanks in advance.

By: Zaro

Zaro — Fri, 12 Mar 2010 08:48:20 +0000

Great article, helps me with error:
HTTP Error 405 Method not allowed – I’ve changed the client proxy interface decorated methods with [System.ServiceModel.Web.WebGet].
To make example work for me, I’ve changed the config paths:
/I’ve received error like: has zero application (non-infrastructure) endpoints./
from: /service config/

and: /client config/
to

Thanks for the post!

By: Web Design, Manchester

Web Design, Manchester — Sun, 28 Feb 2010 09:14:03 +0000

Great article – keep them coming please

By: Database Consultant

Database Consultant — Thu, 31 Dec 2009 11:15:39 +0000

Very nice post. WCF is pretty versatile. I’ve been able to get SOAP and REST working together nicely now.

By: Joan

Joan — Mon, 09 Nov 2009 10:53:19 +0000

Thanks that helped to understand a bit more.

Finally I got the array doing this eventhough I don’t really get why should work this way . . .

var jsonstring = xmlHttp.responseText;
var comboitem = eval(‘ (‘ + jsonstring + ‘ ) ‘);

$(‘#resp_DGO’).empty();

$.each(comboitem.d, function(i) { $(‘#resp_DGO’).append(‘ ‘ + comboitem.d[i].Name + ”);
})

Thanks for the great post!

By: admin

admin — Fri, 06 Nov 2009 20:00:04 +0000

@Joan, The "d" is an array with one element try this


var result = {”d”:[{"__type":"ComboItem","Id":"ECL","Name":"Es-----ro"}]};
alert(result.d[0].Id);

By: Joan

Joan — Fri, 06 Nov 2009 12:58:23 +0000

Sorry but I am stucked in trying to get the info out of this data: {"d":[{"__type":"ComboItem:http:\/\/schemas.---------------\/2009\/07\/30\/ComboItem","Id":"ECL","Name":"Es-----ro"}]} what should I use in the javascript to get my ComboItem.id and .Name fullfiled with values. Thanks a lot!

By: admin

admin — Tue, 21 Jul 2009 23:44:44 +0000

Hi Dave, I think what AllanC wants to do is to make the url a lot more nicer. In your case, if UriTemplated, it could look like

../RecordMetric/1/123/40

By: Dave

Dave — Tue, 21 Jul 2009 15:32:37 +0000

Wow it really killed my URL… let me try that again:

mysever:someportnumber/service/RecordMetric?learnerId=1&metricId=123&value=40

By: Dave

Dave — Tue, 21 Jul 2009 15:28:04 +0000

You shouldn’t need UriTemplate. I was trying to use it to format a query string but all i need to do was this:

[OperationContract]
[WebInvoke(BodyStyle = WebMessageBodyStyle.WrappedRequest,
Method = "GET",
RequestFormat = WebMessageFormat.Json,
ResponseFormat = WebMessageFormat.Json)]
Result RecordMetric(int learnerId, string metricId, decimal value);

I can then call my service like this:

http://myserver:someport/service/RecordMetric?learnerId=1&metricId=123&value=40

By: AllanC

AllanC — Wed, 08 Jul 2009 23:17:24 +0000

Thanks! This gave me enough pieces to get my SOAP and REST working together. Too bad that you cannot use UriTemplate and JSON (web scripting) together (it violates some WCF constraint).

By: admin

admin — Wed, 01 Apr 2009 02:23:24 +0000

Thanks Cheeso and your reply, I copied the server’s program.cs code onto the blog. My bad.

Content type negotiation is a very good idea, I’ve seen an example of it from Codeplex. However, one important issue with it is users are not able to modify http header field easily in the web browsers. In contrast, by expressing it at the endpoint level, you can easily control what kind of message you expect in the response by jsut altering the URL.

By: Cheeso

Cheeso — Tue, 31 Mar 2009 21:43:50 +0000

Very interesting and useful.

one problem? The client program.cs seems to be wrong – you actually show the server program.cs.

Also, one question: what about content negotiation? Rather than exposing different content types for the same resource at different URIs, why not have a single URI, and then allow the content type (json, pox, more?) to be negotiated at request time. HTTP allows this.

Of course if you are using WsTcpBinding then you don’t have the content type negotiation of HTTP, but I suppose you could default to SOAP in that case.

By: Nestor

Nestor — Tue, 20 Jan 2009 16:15:27 +0000

Very nice post, self explanatory and easy to follow and understand.
Exactly what I was looking for about this possibility within WCF.

Thanks heaps, much appreciated.

Keep up your good posting.

Nestor.

By: Steve

Steve — Fri, 05 Dec 2008 16:25:56 +0000

Great post and examples. Really appreciate it!

-Steve

By: admin

admin — Sun, 26 Oct 2008 09:15:45 +0000

Thanks for pointing out the typo. I have changed the ‘pox’ to ‘json’

By: Steve

Steve — Fri, 24 Oct 2008 15:25:08 +0000

Great post, thanks!

I was able to setup my own service to do these three formats all at once based on this. Noticed a typo in your post though, when you’re talking about the JSON request, the GET request should be:

// REST request with parameters in the URL
GET /TestService/json/GetFoo?name=wall-e&age=256&numberOfFoo=2 HTTP/1.1
Content-Type: application/xml; charset=utf-8
Host: localhost:81