« Agile Business Methodology | Main | Windows Workflow Foundation »



TrackBack URL for this entry:

Listed below are links to weblogs that reference Using Commons Chain in a Spring Framework Application:


Feed You can follow this conversation by subscribing to the comment feed for this post.

Hmmm "not Springy"... I thought that the default behaviour of Spring was to use singleton bean instances, unless otherwise specified in the bean definition.
There is some sample code at the link below where spring beans are used in the chain so that they can be IoC configured. That would seem more springy than naming the concrete class to use which is the default way that chains does it as shown in step 3 of this blog. http://www.drummondsoftware.com/WhitePapers/SpringChain/SpringChain.htm
Could this not be much simpler and a lot more 'springy' by simply defining your commands and chains in the application context itself rather than using a seperate config file:
<bean name="myCommand1" class="MyCommand1"/> <bean name="myCommand2" class="MyCommand2"/> <bean name="batchSendChain" class="MyCommandChain"> <property name="commands"> <list> <ref bean="myCommand1"/> <ref bean="myCommand2"/> </list> </property> </bean>

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Your comment could not be posted. Error type:
Your comment has been saved. Comments are moderated and will not appear until approved by the author. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.


Post a comment

Comments are moderated, and will not appear until the author has approved them.

Your Information

(Name and email address are required. Email address will not be displayed with the comment.)