wsSOAPServer

Home > Books > NetKernel API and Services Reference > Accessor Listing > SOAP Service Infrastructure > wsSOAPServer

Module

The wsSOAPServer accessor is exported by the urn:org:ten60:netkernel:mod:ws module. Import this module to gain access to the accessor.

Syntax

URI

active:wsSOAPServer

Argument	Rules	Description
endpoint	Mandatory	The endpoint of the SOAP service
action	Optional	An optional (as of SOAP 1.2) action URI for the SOAP service
message	Optional	An optional (as of SOAP 1.2 GET) SOAP message
config	Mandatory	A SOAPServiceMap document

Example Usage

DPML

<instr>
  <type>wsSOAPServer</type>
  <endpoint>http://1060.org/services/example/</endpoint>
  <action>urn:org:ten60:netkernel:ws:example</action>
  <message>var:message</message>
  <config>ffcpl:/etc/SOAPServiceMap.xml</config>
  <target>this:response</target>
</instr>

NetKernel Foundation API

req=context.createSubRequest("active:wsSOAPServer");
req.addArgument("endpoint", [resource representation, aspect, or URI] );
req.addArgument("config", [resource representation, aspect, or URI] );
result=context.issueSubRequest(req);

Purpose

The wsSOAPServer receives a SOAP message and endpoint and action URIs. Using the supplied config SOAPServiceMap it locates the port corresponding with the received endpoint and action URIs. The port specifies an internal URI to which the SOAPserver issues the request. The incoming arguments (message, endpoint and action) are passed as arguments with the internal request.

wsSOAPServer does not interrogate SOAP headers. It is the responsibility of the application-level internal service to comply with any SOAP header processing directives (such as mustUnderstand etc).

wsSOAPServer supports both SOAP1.1 and SOAP1.2 document-based Web-Services.

The wsSOAPServer accessor implements the mapper pattern.