Just found a google project with code that we can use a foundation: http://code.google.com/p/camelinaction/source/browse/trunk/appendixE/
On Mon, Oct 31, 2011 at 9:12 AM, Richard Hirsch <[email protected]> wrote: > True. > > What about agreeing on a first step in the integration. What about an > Akka/Camel-based action that allows a user to send a message to a JMS > queue? > > D. > > > On Mon, Oct 31, 2011 at 8:46 AM, Ethan Jewett <[email protected]> wrote: >> Hi Dick, >> >> I'd suggest just keeping it small at first and starting with actions and >> implementing Akka's Camel integration there. >> >> I think we need to have a longer discussion about some of the difficulties >> with scaling this. I'm not sure that Akka's remoting features will really >> help us scale ESME under the current architecture, but I also don't know >> that scaling is really something we need to be worried about all that much. >> Camel integration is probably the most immediately attractive feature. >> >> Thanks, >> Ethan >> >> On Mon, Oct 31, 2011 at 6:47 AM, Richard Hirsch <[email protected]>wrote: >> >>> How should we proceed with Akka in 1.4? Do we want to replace all the >>> lift actors with akka actors? I don't think so. I was reading a thread >>> in the lift google group and I saw David talking about some possible >>> drawbacks. For me, the most aspect is the camel integration. >>> >>> Thoughts? >>> >>> D. >>> >> >
