Page 1 of 1

Jade and Web Services

Posted: Tue Dec 03, 2013 4:20 am
by M45HY
Hi Guys,

The company that I work for have decided to try and separate Jade from the Web Browser as we currently have web pages for clients that have been generated by Jade. We are planning to have Jade coding talk to a Web Service and HTML retrieving the data it needs from that Web Service. I just wanted more insight on this, as I'm not that familiar with Web Services or the capabilities of Jade and Web Services.

I was wondering whether someone could describe how you or your employer have linked Jade with Web Services, such as what the process involves, what the best way to do this is (etc)?

Kind Regards,
Omash

Re: Jade and Web Services

Posted: Tue Dec 03, 2013 7:39 am
by murray
Hi Omash,

There are some white papers on Web Services, on Jade's website <http://www.jade.co.nz/jade/whitepapers.htm> that will give you a good overview. Start with "Web Wervices in Jade", which will get you started. Then have a read of Chapter 16 ("Building Web Services Applications") in the the Jade Developers manual (DevRef.pdf). These will give you a good overview of what Jade can provide for Web Services. You may find it helpful to work through a very simple proof of concept to see how it all works in practice.

Re: Jade and Web Services

Posted: Tue Dec 03, 2013 7:40 am
by ghosttie
We wrote a web application that used conventional web technologies for the client UI and only used JADE as a database - they communicated using Web Services. The only real down side of this is that JavaScript doesn't provide the WS client functionality that other languages (.NET, JAVA, JADE) do, so you'll need to create XML for the messages you send and parse the XML to get the data from the responses you receive.

We've recently started a new web project, and instead of using Web Services we're using a C# exposure from JADE which is used by a WCF REST service which is in turn consumed by the JS in the browser. The advantages of this is that REST is lighter than SOAP and JSON objects can be converted directly to JS, which eliminates some client-side work. The down side is that there's an extra layer involved, in a third language.