WCF JSON implementation

Question

I'm trying to implement a very simple WCF service that returns JSON. I'm trying for 6 hours now and it still doesn't work. I hope you can help me out with this.

Person

using System; using System.Collections.Generic; using System.Linq; using System.Text; using System.Runtime.Serialization; namespace Tcf.AtX.Services { [DataContract] public class Person { [DataMember] public string Name { get; set; } } }

Service Contract

using System; using System.Collections.Generic; using System.Linq; using System.Text; using System.ServiceModel; using System.ServiceModel.Web; namespace Tcf.AtX.Services { [ServiceContract] public interface IBroadcastService { /// <summary> /// Broadcasts the specified message. /// </summary> /// <param name="message">The message.</param> /// <returns></returns> [OperationContract] [WebInvoke(Method="GET", ResponseFormat= WebMessageFormat.Json)] Person Broadcast(string message); } }

Service Implementation

using System; using System.Collections.Generic; using System.Linq; using System.Text; using Tcf.AtX.Broadcasting; namespace Tcf.AtX.Services { public class BroadcastService : IBroadcastService { /// <summary> /// Broadcasts the specified message. /// </summary> /// <param name="message">The message.</param> /// <returns></returns> public Person Broadcast(string message) { return new Person() { Name = message }; } } }

Configuration

<?xml version="1.0"?> <configuration> <system.web> <compilation debug="true"/> </system.web> <system.serviceModel> <services> <service name="Tcf.AtX.Services.BroadcastService"> <endpoint address="" binding="webHttpBinding" contract="Tcf.AtX.Services.IBroadcastService" behaviorConfiguration="json"/> <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" /> <host> <baseAddresses> <add baseAddress="http://localhost:8732/Design_Time_Addresses/Tcf.AtX.Services/BroadcastService/" /> </baseAddresses> </host> </service> </services> <behaviors> <endpointBehaviors> <behavior name="json"> <webHttp /> </behavior> </endpointBehaviors> <serviceBehaviors> <behavior name=""> <serviceMetadata httpGetEnabled="true"/> <serviceDebug includeExceptionDetailInFaults="false" /> </behavior> </serviceBehaviors> </behaviors> </system.serviceModel> <startup><supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/></startup></configuration>

The problem is that i don't see the service inside the test client, so i can't test my method. I also wrote a test client myself, but i can't create an instance of my service when i reference it to my project.

Can someone please explain to me what i'm doing wrong?

Best regards,

Rob

carlosfigueira · Accepted Answer · 2012-03-07 15:15:40Z

3

The test client doesn't work for non-SOAP endpoints (i.e., the one you have, which uses the WebHttpBinding). Try simply creating a program that tries to call the operation you have, something like the code below

WebClient c = new WebClient(); Console.WriteLine( c.DownloadString( "http://localhost:8732/Design_Time_Addresses/Tcf.AtX.Services/Broadcast?message=MyMessage"));

One more thing, you'll need to change the [WebInvoke(Method="GET")] attribute to [WebGet].

answered Mar 7, 2012 at 15:15

carlosfigueira

87.7k14 gold badges137 silver badges176 bronze badges

Sign up to request clarification or add additional context in comments.

5 Comments

Rob Angelier Over a year ago

Ok, i will give it a try. Add web reference does not work. I only get the namespace and can not create a instance of the service

carlosfigueira Over a year ago

Yes, for the same reason as the test client doesn't work. Non-SOAP endpoints do not expose their metadata, so that such tools (test client, add reference) don't know how to consume those endpoints.

Rob Angelier Over a year ago

Ok, good to know! I'm wondering.... i need a webservice so i can use it inside my Mono for Android application, but is this the preffered way to do this?

carlosfigueira Over a year ago

There's no "right" or "wrong" type of service / endpoint, it depends on what tools you have at the client and your preferences. If you have a SOAP stack and like having a typed proxy, then using a SOAP endpoint is a good option. If you want "pure" HTTP (smaller messages), don't want the overhead of a proxy class or simply don't have a good SOAP library in the client, then using a JSON (or POX - Plain Old XML) endpoint is a better option.

Rob Angelier Over a year ago

I know there is no right or wrong way to solve this because it depends on the situation. I will think it over and decide wich implementation to use. Thanks for your replies.

Collectives™ on Stack Overflow

WCF JSON implementation

1 Answer 1

5 Comments

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

5 Comments

Related