Non-annotation driven Cafe example?

[william_ferguson_au@yahoo]

While using annotations to configure the ESB components makes for very little config, I have found it difficult to infer where particular components are. I also don't get an overview of the overall process flow. It feels to me that if I let my team develop services using annotations we would quickly end up with a ball of spaghetti services.

So what I'd like to do is to ensure that most of the components are clearly defined. What I'm lacking is details on how to define some of the components without using annotations.

For instance, how do you define a router and link it into the process flow such as that defined in the Cafe example?

Could someone post a non-annotation driven config for the cafe example? Seeing the annotation driven and non-annotation driven side by side would be really useful.

[Mark Fisher]

In M4, we added namespace support for the <router/> and <splitter/> elements. They are not yet documented in the reference manual, but it is fairly straightforward. Here's a simple example:

<router id="router" ref="somePojo" method="someMethod"/>

Thanks for the suggestion - I think we should provide a parallel version of the cafe demo that uses only XML.

[william_ferguson_au@yahoo]

Thanks Mark. I had spotted the <router/> and <splitter/> elements and in fact thats what led to my post.

How do I configure the input-channel for the router/splitter?

Using annotations its

@MessageEndpoint(input="someChannel")

but I can't see how it can be done using XML config

<splitter ref="splitter" method="split" output-channel="drinks"/>
		
<router ref="drinkRouter" method="resolveDrinkChannel"/>

[Mark Fisher]

The <router/> and <splitter/> elements actually create instances that implement MessageHandler, so to supply the "input-channel", you just need to register them within a <handler-endpoint/> element. For example (from routerParserTests.xml):

<handler-endpoint handler="router" input-channel="input"/>

<router id="router" ref="pojo" method="route"/>

[william_ferguson_au@yahoo]

Mark, is the following config the correct way to specify the cafe example without using annotations?

NB I can't check because I can't find spring-integration-core-1.0.0.M4 in the SpringSource bundle repository. Is there a way to browse the repository?

<?xml version="1.0" encoding="UTF-8"?>
<beans:beans xmlns="http://www.springframework.org/schema/integration"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xmlns:beans="http://www.springframework.org/schema/beans"
	xmlns:context="http://www.springframework.org/schema/context"
	xsi:schemaLocation="http://www.springframework.org/schema/beans
			http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
			http://www.springframework.org/schema/integration
			http://www.springframework.org/schema/integration/spring-integration-1.0.xsd
			http://www.springframework.org/schema/context
			http://www.springframework.org/schema/context/spring-context-2.5.xsd">

	<message-bus/>
	<!--annotation-driven/ -->

	<channel id="orders"/>
	<channel id="drinks"/>
	<channel id="coldDrinks"/>
	<channel id="hotDrinks"/>
	
	<handler-endpoint handler="drink-splitter" input-channel="orders" />
	<splitter id="drink-splitter" ref="splitter" method="split" output-channel="drinks"/> 
	
	<handler-endpoint handler="drinkRouter" input-channel="drinks"/>
	<router ref="drinkRouter" method="resolveDrinkChannel"/>
		
	<target-endpoint target="barista" method="prepareColdDrink" input-channel="coldDrinks"/>
	
	<target-endpoint target="barista" method="prepareHotDrink" input-channel="hotDrinks">
		<concurrency core="5" max="25" queue-capacity="0"/>
	</target-endpoint>
	
	
	<!-- Beans -->
			
	<beans:bean id="cafe" class="org.springframework.integration.samples.cafe.Cafe">
		<beans:property name="orderChannel" ref="orders"/>
	</beans:bean>
	
	<beans:bean id="barista" class="org.springframework.integration.samples.cafe.Barista">
		<!--beans:property name="hotDrinkDelay" value="1000"/-->
		<!--beans:property name="coldDrinkDelay" value="700"/-->
	</beans:bean>
	
	<beans:bean id="drinkRouter" class="org.springframework.integration.samples.cafe.DrinkRouter"/>
	
	<beans:bean id="splitter" class="org.springframework.integration.samples.cafe.OrderSplitter"/>
	
</beans:beans>

[william_ferguson_au@yahoo]

Or perhaps even possible to contract the orders and drinks channel consumers to:

<handler-endpoint handler="splitter" method="split" 
                  output-channel="drinks" input-channel="orders"/>
	
<handler-endpoint handler="drinkRouter" method="resolveDrinkChannel" 
                  input-channel="drinks"/>