ClientControllerApplet is an applet designed to provide limited bidirectional XML-RPC support to other applets on the same page.
A client can ask ClientControllerApplet to perform two kinds of XML-RPC to the server. The first ("responseCall") is an ordinary XML-RPC which expects
a data response. The second ("actionCall") is an XML-RPC where ClientControllerApplet should expect the server to respond with a list of strings, each
of which is the XML of an XML-RPC the server wishes to make to an applet on the same page. (The applets also need to have the same "codebase" attribute
as ClientControllerApplet in the HTML of the web page).
In this way, the applet by making an actionCall is permitting the server to make a bunch of XML-RPC calls to the applets in reply.
On this page, the modified Jade applet and the ClientControllerApplet are hooked up. Because there is no XML-RPC server (I haven't set one up for public
access), the ClientControllerApplet is in debug-no-server mode. The javascript link at the foot of the page can force it to behave as if it has just
received an XML-RPC response from a server. The second area at the foot of the page will report the last XML-RPC Jade attempted to make.
testResponseCall(String response)
The applet will react as if it has received the response from an XMLRPC, even though no XMLRPC has been called. Used to
demonstrate the processing of responses as lists of XMLRPC calls
The following xml (for a single XMLRPC call) is used as the "server's response" in this example:
<?xml version="1.0"?>
<methodCall>
<methodName>jade.setValue</methodName>
<params>
<param>
<value></value>
</param>
<param>
<value>instance[@name="Q1"]/terminal[@name="B"]/property[@name="i"]/@value</value>
</param>
<param>
<value>2</value>
</param>
</params>
</methodCall>
Go!
The following details the last outgoing XMLRPC made from Jade
Name: none yet
Args: none yet