Click here to Skip to main content
65,938 articles
CodeProject is changing. Read more.
Articles
(untagged)

Calling Cross Domain WCF service using Jquery/JavaScript

0.00/5 (No votes)
18 Jul 2011 1  
Calling Cross Domain WCF service using Jquery/JavaScript

Introduction

This article is about to call the cross domain WCF service from your page, i.e., calling WCF service hosted on one domain and calling the service form jquery/JavaScript of page which is hosted on some other domain.

But before we start, it's better to get understand about the format of the data get exchange from one server to another.

JSONP - JSON with Padding

Ajax allows to get data in the background without interfering with the display. Ajax call done by using XMLHttpRequest object allows the client side JavaScript code to make HTTP connections.
But Ajax call does not allow to get data from cross-domain because of restrictions imposed by the browser. Security error gets issued when requesting data from another domain. One way to avoid security errors is to control remote server where data resides and every request goes to the same domain. That gives rise to the question, what's the fun if data comes from own server only? What to do if data is required to get from the other server?

There is one way to come out from this limitation - to insert a dynamic script element in the Web page, one whose source is pointing to the service URL in the other domain and gets the data in the script itself. When the script loads, it executes. It works because the same-origin policy doesn't prevent dynamic script insertions and treats the scripts as if they were loaded from the domain that provided the Web page. But if this script tries to load a document from yet another domain, it will fail. Fortunately, you can improve this technique by adding JavaScript Object Notation (JSON) to the mix.

JSONP or "JSON with padding" is a complement to the base JSON data format, a pattern of usage that allows a page to request data from a server in a different domain. As a solution to this problem, JSONP is an alternative to a more recent method called Cross-Origin Resource Sharing.

Under the same origin policy, a web page served from server1.example.com cannot normally connect to or communicate with a server other than server1.example.com. An exception is the HTML <script> element. Taking advantage of the open policy for <script> elements, some pages use them to retrieve JavaScript code that operates on dynamically-generated JSON-formatted data from other origins. This usage pattern is known as JSONP. Requests for JSONP retrieve not JSON, but arbitrary JavaScript code. They are evaluated by the JavaScript interpreter, not parsed by a JSON parser.

Calling Cross Domain WCF service

Now in the following discussion, I am going to show you how easily you can call the WCF service hosted on the other domain from the page hosted on the other domain.
Following is list of articles you should look at first before moving further:

To start, first create a new solution and Add new Project which is WCF service and follow the below steps.

Step 1

In the new release of .NET 4.0, the WCF developer team added support for JSONP. There is a new property added which enables to call WCF service from other domain by setting it to true.
CrossDomainScriptAccessEnabled - Gets or sets a value that determines if cross domain script access is enabled.

Change your WCF service config file as below:

<configuration>
  <system.web>
    <compilation debug="true" targetframework="4.0">
    <authentication mode="None">
  </authentication></compilation></system.web>
  <system.webserver>
    <modules runallmanagedmodulesforallrequests="true">
  </modules></system.webserver>
  <system.servicemodel>
    <servicehostingenvironment aspnetcompatibilityenabled="true">
    <standardendpoints>
      <webscriptendpoint>
        <standardendpoint crossdomainscriptaccessenabled="true">
      </standardendpoint></webscriptendpoint>
    </standardendpoints>
  </servicehostingenvironment></system.servicemodel>
</configuration>

As you can see in the above config code, I have set crossdomainscriptaccessenabled to true and aspnetcompatibilityenabled to true so that the WCF service works as a normal ASMX service and supports all existing ASP.NET features.

Step 2

SVC file of the service should be as below:

<%@ ServiceHost Language="C#" Debug="true" 
Service="WcfService1.Service1" 
CodeBehind="Service1.svc.cs"
Factory="System.ServiceModel.Activation.WebScriptServiceHostFactory"  %> 

Don't forget to add Factory attribute because it causes an error if you remove it. Following are the reasons to add Factory attribute:

  1. Service host factory is the mechanism by which we can create the instances of service host dynamically as the request comes in.
  2. This is useful when we need to implement the event handlers for opening and closing the service.
  3. WCF provides ServiceFactory class for this purpose.

Step 3

CS file for the WCF file is:

using System.Runtime.Serialization;
using System.ServiceModel;
using System.ServiceModel.Activation;
using System.ServiceModel.Web;

namespace WcfService1
{
    [DataContract]
    public class Customer
    {
        [DataMember]
        public string Name;

        [DataMember]
        public string Address;
    }

    [ServiceContract(Namespace = "JsonpAjaxService")]
    [AspNetCompatibilityRequirements(RequirementsMode =   
			AspNetCompatibilityRequirementsMode.Allowed)]
    public class Service1
    {
        [WebGet(ResponseFormat = WebMessageFormat.Json)]
        public Customer GetCustomer()
        {
            return new Customer() { Name = "Pranay", Address = "1 Ahmedabad" };
        }
    }
}

As you can see in the above code, I have created Service class which is a service contract which serves data and Customer class is DataContract which get served as response.
In the service class, GetCustomer method services data in Json format.
Once the WCF service is created, to move further Add new project >> ASP.NET service. So that both the WCF service and website run on two different ones like are both hosted on different domains.
There are two solutions to call the Cross Domain WCF service.

Solution 1: Call WCF service by using JQuery

Jquery already has support to handle the jsonp. Jquery library provided function ajax and getJson which can allow to call the WCF service which sends jsonp data in response.

CallService - Generic function is used to call the WCF service, which gets called by other JavaScript function to get and display data.

var Type;
        var Url;
        var Data;
        var ContentType;
        var DataType;
        var ProcessData;
        var method;
        //Generic function to call WCF  Service
        function CallService() {
            $.ajax({
                type: Type, //GET or POST or PUT or DELETE verb
                url: Url, // Location of the service
                data: Data, //Data sent to server
                contentType: ContentType, // content type sent to server
                dataType: DataType, //Expected data format from server
                processdata: ProcessData, //True or False
                success: function (msg) {//On Successful service call
                    ServiceSucceeded(msg);
                },
                error: ServiceFailed// When Service call fails
            });
        }

ServiceFailed - gets called when call to service fails.

function ServiceFailed(xhr) {
            alert(xhr.responseText);
            if (xhr.responseText) {
                var err = xhr.responseText;
                if (err)
                    error(err);
                else
                    error({ Message: "Unknown server error." })
            }
            return;
        }

ServiceSucceeded - gets called when the service successfully returns a response. As you can see in the function, I am checking DataType is jsonp which is just to demonstrate that service is returning jsonp data.

function ServiceSucceeded(result) {
            if (DataType == "jsonp") {
                
                    resultObject = result.GetEmployeeResult;
                    var string = result.Name + " \n " + result.Address ;
                    alert(string); 
            }
        }

GetEmployee - is a function that gets called to request data from WCF service hosted on other domain. As you can see in code, DataType value gets set to jsonp.

function GetEmployee() {
            var uesrid = "1";
            Type = "GET";
            Url = "http://localhost:52136/Service1.svc/GetCustomer"; 
            DataType = "jsonp"; ProcessData = false;
            method = "GetCustomer";
            CallService();
        }

        $(document).ready(
         function () {
            
             GetEmployee();
         }
);

Solution 2: Call WCF Service by JavaScript

To call the service using JavaScript, make use of ScriptManager:

 <asp:scriptmanager id="ScriptManager1" runat="server">
        <services>
            <asp:servicereference path="http://localhost:52136/Service1.svc">        
 </services>  

In the above code, I set the servicereference to the WCF service hosted on other domain.

makeCall - function that gets called to request data from WCF service hosted on another domain.

function makeCall() {
                      var proxy = new JsonpAjaxService.Service1();
                     proxy.set_enableJsonp(true);
                     proxy.GetCustomer(onSuccess, onFail, null);
                 }

onSuccess - is called when the result from the service call is received and displays data.

function onSuccess(result) {
                     alert( result.Name + " " +result.Address);
                 }

onFail - is called if the service call fails.

function onFail(){
                     alert("Error");
                 } 

Summary

So after the addition to the special property by the WCF team, it's quite easy to call cross domain WCF service.

References

License

This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here