Re: stand-alone problem

Wow, it works. I have been struggling for two days as to why it would all of a sudden stop working. And to make matter worse, the connect/reconnect from spring that I reported in this post also started working. Thanks a log Claus. Cam

Re: stand-alone problem

Did you look here for an example for how to keep it running forever as a standalone app? http://camel.apache.org/running-camel-standalone-and-have-it-keep-running.html On Thu, Dec 1, 2016 at 4:29 PM, sa_james [via Camel] < ml-node+s465427n5790889...@n5.nabble.com> wrote: > So If I ditch spring an

Re: stand-alone problem

Use the run method instead of start. On Thu, Dec 1, 2016 at 4:07 PM, sa_james wrote: > Here I am again with a simple test: > > /from("jms:queue").to("log:test")/ > > / class="org.springframework.jms.connection.CachingConnectionFactory"> > ref="webSphereConnectionFactory" /> > > / >

Re: stand-alone problem

So If I ditch spring and go back to using setters, everything will be fine? -- View this message in context: http://camel.465427.n5.nabble.com/stand-alone-problem-tp5790885p5790889.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: stand-alone problem

I am not experienced with spring but it seems your context is started and then there is nothing to keeps it going to so it dies straight away. Normally with a Main() you need to add code to keep it running forever. Via blueprint or spring the context is injected.. On Thu, Dec 1, 2016 at 4:23 PM, s

Re: stand-alone problem

If I set a breakpoint at the last statement, it will consumes messages from the queue. -- View this message in context: http://camel.465427.n5.nabble.com/stand-alone-problem-tp5790885p5790887.html Sent from the Camel - Users mailing list archive at Nabble.com.