The AbstractWebServiceHandler is now an endpoint instead of a MessageHandler implementation. The <ws-handler/> element has been replaced with <ws-service-activator/>, and it is now a "standalone" component (i.e. it is no longer necessary to provide its id as a reference within another separate <service-activator/> element).

This commit is contained in:
Mark Fisher
2008-09-05 19:22:10 +00:00
parent b2db1c0b16
commit 9fc031e4f4
6 changed files with 54 additions and 47 deletions

View File

@@ -11,15 +11,12 @@
<channel id="fahrenheitChannel"/>
<!-- The service activator receives from the 'fahrenheitChannel',
invokes the handler, and sends the reply Message to the 'celsiusChannel'. -->
<service-activator input-channel="fahrenheitChannel"
ref="temperatureConverter"
output-channel="celsiusChannel"/>
<!-- The handler invokes the WebService for the given URI and returns a reply Message. -->
<ws-handler id="temperatureConverter"
uri="http://www.w3schools.com/webservices/tempconvert.asmx"/>
<!-- The service activator receives from the 'fahrenheitChannel', invokes the
Web Service for the given URI, and sends the reply Message to the 'celsiusChannel'. -->
<ws-service-activator id="temperatureConverter"
input-channel="fahrenheitChannel"
output-channel="celsiusChannel"
uri="http://www.w3schools.com/webservices/tempconvert.asmx"/>
<!-- The response from the service is logged to the console. -->
<channel-adapter id="celsiusChannel" target="console"/>