Hi Jon, I did a quick fix for the issue of SpringIntegration upgrading. Here are some notes of my changes: 1. Changed to use the DirectChannel for internal message sending and receiving. 2. Using the AsyncProcessor for sending the message into SpringIntegration channel. 3. Using the Event-Driven Consumer API instead of Polling Consumer API to receive message from SpringIntegration channel.
Cheers, Willem Willem Jiang wrote: > Hi Jon, > > Thanks for your upgrade work, it's saving lots of my time. > > After a quick reading of SpringIntegration documents, I found there are > big changes of the Spring Integration APIs which leverage more on async > message handling. Now I am turning the camel-spring-integration into > another asyc module of camel by using the camel AsyncProcessor API. > > It may be a long battle, but it is good to see this big evolution of > SpringIntegration :) > > Willem > Jon Anstey wrote: >> The update didn't go so well :) I've put up the changes so far on CAMEL-1053 >> if anyone wants to continue the battle over night (well, my night anyway). >> >> Willem, maybe you could take a quick look since you have the most exp with >> camel-spring-integration? >> >> On Tue, Nov 4, 2008 at 5:52 PM, Jon Anstey <[EMAIL PROTECTED]> wrote: >> >>> Just discovered that >>> http://www.springsource.org/schema/integration/spring-integration-1.0.xsdwas >>> changed today such that the camel-spring-integration doesn't work >>> anymore. Kinda weird that they would change what looks like a release schema >>> version but anyways... this means that Camel 1.5 spring-integration is >>> busted as well - not good. I think the best option may be to just upgrade to >>> the latest spring-integration release. Looks to be quite a few changes but >>> I'll see if I can get it working now. Will post an update later. >>> >>> -- >>> Cheers, >>> Jon >>> >>> http://janstey.blogspot.com/ >>> >> >> > >
