My preference is 2); In the meantime I'll start a Camel 1.3.0 release ASAP - am sure we'll have reason to release another ServiceMix release soonish...
On 28/11/2007, Guillaume Nodet <[EMAIL PROTECTED]> wrote: > It seems like a bug in camel which has been fixed (by chance ?) a few weeks > ago > in this commit > http://svn.apache.org/viewvc?diff_format=h&view=rev&revision=591400. > However camel-1.3.0 has not been released, and we now have a few solutions: > 1) remove the camel sample > 2) let it in this state (maybe add something in the README.txt about using > a more recent > version of the camel-se instead with a 1.3.0-SNAPSHOT version of > camel inside ?) > 3) wait for a camel release. > > Imho, we should go for 2. Thoughts ? > > On Nov 27, 2007 11:40 PM, Gert Vanthienen <[EMAIL PROTECTED]> wrote: > > > Gert Vanthienen wrote: > > > Another thing: when I deploy the Camel example, I was expecting to see > > > the message 'Hello world!' appear in the logging, but it just says > > > Exchange[null]. I suppose this is more related to Camel than it is to > > > ServiceMix though, because the Route that is being deployed doesn't > > > really integrated with the JBI container or use any of the JBI > > > specific classes. > > On second thought, if I run the same Camel route outside ServiceMix, in > > a simple Java application, it does produce the expected output > > (Exchange[Message: Hello World!]). > > > > > > > > > > Gert > > > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://open.iona.com
