Pending Review
Last Updated: 29 Apr 2016 19:08 by Benny
Imported User
Created on: 07 Mar 2012 22:47
Category: Data Source
Type: Feature Request
7
Web Service Javascript Proxy generator(JSON and SOAP)
Visual Studio plugin to generate javascript proxy classes for communicating with web services. 

Normally in ASP.Net the .Net proxy classes would be generated for me, but since I am now moving towards building RIA applications most of the WS calls now take place client side. The process of manually setting up service calls is a bit cumbersome so if KendoUI could include a tool for this it would be great.
2 comments
Benny
Posted on: 29 Apr 2016 19:08
Robert McGill, the generator that you created, is it capable of connecting to a WCF service hosted in a Windows application or Windows Service and generate a JavaScript proxy for it? If so, I would be very interested in it for a small project that I'm working on.
Robert
Posted on: 15 Dec 2012 21:15
Well I ended up building my own javascript/json proxy generator. I can generate a full Javascript proxy for WCF Web Services. It will build up prototypes, requests, responses for all datacontracts and operations.The proxy peforms basic validation for .Net types, and set defaults in the prototypes for .net types.(ex: nullable ints are defaulted to null, and ints are default to 0). It also automatically handles epoch date conversions on send/receive for known types. Since prototypes are generated for datacontracts I also get intellisense for all datamembers when typing in Javascript.

Underneath the hood is uses jquery for the XMLHttpRequest, and JSONP for older browsers that can't stringify. All requests are posts so that the data is encrypted when using HTTPS.

I've got several line of business SPA applications nearly ready to go live using this approach. It ties into KendoUi relatively well. 

It has been extremely useful since now we can maintain one WCF service that supports both JSON and SOAP. So a client(Banks/Insurance Companies) may use our interface or consume the SOAP service direcly. We use a message inspector to handle the security. In the case of SOAP content it will verify the SOAP headers, and in the case of JSON content it verifies the HTTP headers. 

Even if Telerik built a code generator I would be unlikely to adopt it at this point, however I just wanted to share my solution since my original post in March. Hopefully you can appreciate the value in this feature and possibly add it for your other subscribers.