Frontier and SOAP

Part of the SOAP website. Updated: 4/1/98; 10:30:34 AM.

SOAP: Frontier and SOAP
Requirements
Here's what you need to get to run this software:

Frontier 5.0.2b6 or greater.

The latest version of builtins.soap, the glue that connects Frontier scripts to the SOAP protocol, both client and server.

The latest version of builtins.xml. A SOAP conversation is in XML, so we need the XML compiler.

The latest version of Betty. The SOAP server is a Betty responder.

The latest root update. Always a good idea when installing leading edge stuff. We put fixes into the update process that new stuff builds on.
How to install
After bringing builtins.soap into your root, open the table and run soap.install.
soap.install puts a responder at user.webserver.responders.soap.
It also creates a user.soap table, and a single sub-table called handlers. This is the table where you put scripts that respond to SOAP requests. We've put a single handler in this table, a very simple one that returns the name of one of the 50 states in the United States.
How to test
Open soap.examples.localTest.callGetState.
Click on Run.
A dialog should appear saying "Mississippi".
This gives you a good indication that the SOAP server is running properly on your machine.
Listing
Here's what soap.examples.localTest.callGetStates does:

local (params = {22, 23, 24, 25})

dialog.alert (soap.soapCall (procedureName:"examples.getStateNames", adrparamlist:@params))

wp.newTextObject (params [1], @soap.examples.localTest.soapRequest)

try {delete (@soap.examples.localTest.soapReturn)}

soap.examples.localTest.soapReturn = params [2]
soap.soapCall
soap.soapCall is the current client interface from Frontier.
We're expecting to more deeply integrate SOAP calls in the Frontier kernel in 5.0.2.