<?xml version="1.0" encoding="UTF-8"?>
<m:deployment xmlns:m="urn:VASTWebServiceDeployment600"
	targetNamespace="urn:VASTWebServices600"
	xmlns:tns="urn:VASTWebServices600">

<!-- Create definitions with 'container' visibility.  Elements below can be shared by all services
deployed to a container -->
<container name="VastSampleClientContainer">

	<!-- The Smalltalk ICs that should be loaded before attempting deployment.  Urls must resolve to a local file. -->
	<imageComponentUrls>
	  <!--  <imageComponentUrl>.\myContainer.IC</imageComponentUrl> -->
	</imageComponentUrls>

	<schemaUrls>
<!--		<schemaUrl>d:\workspce\webservices\ws-security\secext.xsd</schemaUrl>
 -->
	</schemaUrls>

	<!-- The mapping specifications that are required to marshall XML for the services defined by this deployment descriptor -->
	<mappingSpecUrls>
		<!-- <mappingSpecUrl>http://mappingUrl</mappingSpecUrl> -->
	</mappingSpecUrls>

	<configuration>
		<globalNamespace>urn:VASTWebServices600</globalNamespace>
		<defaultServiceInterfaceClass>SstWSService</defaultServiceInterfaceClass>
		<deploymentManager>SstWSDeploymentManager</deploymentManager>
		<messageContextFactory>SstWSMessageContextFactory</messageContextFactory>
		<handlerFactory>SstWSHandlerFactory</handlerFactory>

		<!-- Specify the actor roles that this node supports during processing -->
		<actorRoles>
			<actorRole>http://schemas.xmlsoap.org/soap/actor/next</actorRole>
			<actorRole>vast:anonymous</actorRole>	
		</actorRoles>

		<!--	These will be instantiated and added in order as managers in the container
				Manager should have a class associated with them.  
				Manager name attributes will be converted to an EsAtom when they are added to
				the container.  For the entries below, pool constancts have been declared that 
				match the EsAtoms, e.g. SstWSConstants::WSEngineFactory will resolve to ##wsEngineFactory."-->
		<managers>
			<manager name="wsEngineFactory" 			class="SstWSEngineFactory"/>
			<manager name="wsPortManager" 				class="SstWSPortManager"/>
			<manager name="wsSerializationManager"	class="SstWSXmlObjectCache"/>
			<manager name="wsServiceDefinitionsManager" 	class="SstWSDefinitionsManager"/>
			<manager name="wsServiceManager"			class="SstWSServiceManager"/>
			<manager name="wsActorManager"			class="SstWSActorManager"/>
		</managers>
		<transportMappings>
			<transportMapping urlScheme="http" transportScheme="httpl"  />
			<transportMapping urlScheme="https"  transportScheme="httpsl" />
		
		</transportMappings>
	</configuration>

	<!--	Handlers specified in the container section are 'global' relative to the container
	 		and will be placed in the handler registry by their name and the container's namespace.
	 		The handlers specified below are equivalent to the default handlers specified for the 
	 		VAST Web services framework.  
	 		Notes:
				Handlers specified in the deployment descriptor take precidence.

				Handlers should have a type OR a class associated with them.  If both are 
				specified the class takes precedence

	 			The framework will attempt to perform these handler name against the 
	 			handler factory if it is not present in the handler factory's registry.
	
		 		Client handlers are present in the container because the container may have only service 'proxies' -->

    <handlers namespace="urn:VASTWebServices600">
		<handler name="wsGlobalClientInputHandler"				class="SstWSSecurityHeaderGenerationHandler"/>
		<handler name="wsGlobalRequestServerHandler"				class="SstWSHeaderProcessor"/>
		<handler name="wsSoapEnvelopeGenerationHandler"    		class="SstWSSoapEnvelopeGenerationHandler"/>
		<handler name="wsSoapInputPayloadGenerationHandler"  	class="SstWSSoapInputPayloadGenerationHandler"/>
		<handler name="wsSoapFaultPayloadGenerationHandler"	class="SstWSSoapFaultPayloadGenerationHandler"/>
		<chain name="wsClientInputMessageConstructor" class="SstWSSimpleChain">
			<handler type="tns:wsSoapEnvelopeGenerationHandler"/>
			<handler type="tns:wsSoapInputPayloadGenerationHandler"/>
		</chain>
		<handler name="wsServiceFaultServerHandler"			class="SstWSNoOperationHandler"/>
		<handler name="wsGlobalResponseClientHandler"			class="SstWSHeaderProcessor"/>
    	 <handler name="wsHttpClientRequestHandler"	 			class="SstWSHttpDispatchHandler"/>
   	     <handler name="wsHttpServerFaultHandler"  	 				class="SstWSHttpResponseHandler"/>
		<handler name="wsHttpServerRequestHandler"  				class="SstWSHttpSoapActionHandler"/>	
		<handler name="wsHttpServerResponseHandler" 			class="SstWSHttpResponseHandler"/>	

<!--	Uncomment this handler to activate a handler that writes container information to the SOAP header.
	    By default, the wsGlobalResponseServerHandler does nothing.
		<handler name="wsGlobalResponseServerHandler" 		class="SstWSSampleContainerHeaderOutputHandler"/>	 -->
	</handlers>


	<!-- 	The service imports section represent service descriptions external to this document. Currently,
		  	the external document can be either a service deployment descriptor or a WSDL.  Processing of
		  	the service imports occurs after the container is deployed and started.-->
	<serviceUrls>
		<serviceUrl>http://vasthost:63001/SstWSInsurancePolicyClientInterface.xml</serviceUrl>
	</serviceUrls>  


	<extensions></extensions>
</container>

</m:deployment>
