Remote Deployment
The last screen of the web services example, shown below, starts the http server, deploys the service into a containter and invokes the SstWSInsurancePolicyInterface service.
It is laid out the same way that the local deployment screen was. The example specifies a URL of 'vasthost'. the check box serves as a reminder.
Note:
The examples in this guide specify URL resources using a host name of 'vasthost'. You must add a line to your 'hosts' file, or use any hostname valid for your environment in place of 'vasthost', in order to successfully execute the described examples.
ie)
ie)
127.0.0.1 vasthost
The generate "Start HTTP Server" button starts the server; the "start web service Container" button starts a container; the "Deploy Service" button deploys the SstWSInsurancePolicyInterface service into the container.
The tree view at the bottom lists the public interface. Double clicking on any of these invokes the service. If additional information is needed, you will be prompted to enter it. The results of the invocation are viewed in a Smalltalk inspector.
Since this is not recognized as a local invocation, the service utilizes the SOAP stack and sends the request over the wire. Since the example does not provide any mapping of the objects involved, strings are returned.
It is possible to have Smalltalk objects retuened for simple types such as the float returned fro the reatePolicy. In order to this, you must shut down the example, edit the SstWSInsurancePolicyInterface-interface.wdsl file, and restart the example. The line of interest reads as follows:
<message name="ratePolicy">
<part name="ratePolicy" type="xsd:string"/>
</message>
<message name="ratePolicyResponse">
<part name="outMsg" type="xsd:string"/>
Changing string to float will allow the SOAP value to be converted into a Smalltalk Float.
In general, mapping SOAP to Smalltalk objects is beyond the 10 minute limit set for this example.
Last modified date: 04/21/2020