Thanks, My scenario now works. But I still have one interesting question.
When I deploy my component to ServiceMix the quartz-su starts first then my jms-su and then camel-su. As soon as my quartz starts it fires an event, and of course as my camel-su is not started now, an exception is thrown. As soon as the camel-su also starts the scenario works fine. Is there some mechanism in Servicemix, where I can specify that my camel-su should start before my quartz-su, so that no error occurs when I deploy my component? Greetings Robert -----Ursprüngliche Nachricht----- Von: James Strachan [mailto:[EMAIL PROTECTED] Gesendet: Montag, 17. Dezember 2007 15:06 An: [email protected] Betreff: Re: Usage of Camel On 17/12/2007, Guillaume Nodet <[EMAIL PROTECTED]> wrote: > On Dec 17, 2007 2:48 PM, Robert Thullner <[EMAIL PROTECTED]> wrote: > > > Where can I dowload the 3.3-SNAPSHOT? I only found some 3.2.x > > versions on the project website. > > > I'm working on enabling nightly builds for 3.3 (trunk) and weekly > builds for > 3.2 and 3.1 (branches). > In the mean time, you can download the sources and build those locally. > > > > > > > > How do I disable the JMX support? > > > No idea :-( > If I find something, I'll tell you. :) Try <camelContext useJmx="false" xmlns="http://activemq.apache.org/camel/schema/spring";> ... -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://open.iona.com
