wsdd/examples/chaining_examples/ch_wsddScenario2.wsdd

<?xml version="1.0" encoding="UTF-8"?>
<deployment 	name="wsddScenario2" 
				xmlns="http://xml.apache.org/axis/wsdd/" 
				xmlns:java="http://xml.apache.org/axis/wsdd/providers/java/"
				xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance" 
				xsi:schemaLocation="http://xml.apache.org/axis/wsdd/ D:\Schemas\WSDD\WSDD.xsd">
	<documentation>
		A simple serviceDeployment descriptor is used to describe the service.
    		The type is not needed either, as it reflects the default choice (simpleTargetedChain).
    		This defines a simple input chain of 2 handlers, a simple output chain of 2 handlers.
    		This shows use of parm to configure options on inputHandler2.
  </documentation>
	<service name="wsddScenario2-service1" type="java:org.apache.axis.SimpleTargetedChain">
		<requestFlow>
			<documentation>
				The input chain does not need to define type, as this is default
    				when more than one handler is specified within the flow
   			 </documentation>
			<handler name="inputHandler1" type="java:samples.handlers.testHandler1"/>
			<handler name="inputHandler2" type="java:samples.handlers.testHandler1">
				<parameter name="parm1">inputHandler2</parameter>
			</handler>
		</requestFlow>
		<provider>
			<java:provider className="samples.wsdd.wsddScenario2" />
		</provider>
		<responseFlow>
			<documentation>
				The even though no type is specified, the default chain type is taken
      				because more than one handler is specified
    			</documentation>
			<handler name="outputHandler1" type="java:samples.handlers.testHandler2"/>
			<handler name="outputHandler2" type="java:samples.handlers.testHandler2"/>
		</responseFlow>
	</service>
</deployment>