I'm not sure how did you remove the Jetty endpoint? >From the camel route configuration, I can just tell that the Jetty endpoint is used to accept the request from http://localhost:8081/msgs, just like the file endpoint does.
If you want to remove the Jetty endpoint, you need remove the this whole route. from("jetty:http://localhost:8081/msgs"). process(new AddSourceProcessor('file3')). to("seda:logmsgs?size=10000&concurrentConsumers=5") Willem koevet3 wrote: > > Hi, > I have stumbled across a blog post recently that shows how to monitor a > file using Camel and display the file content on a browser using Comet > (using Groovy). > Actually a > http://www.andrejkoelewijn.com/wp/2009/10/27/simple-log-console-with-camel-and-cometd/ > pretty cool example . > > There is something that I don't quite understand in the Camel routing of > this example and I'd like to ask for clarification. This is a snippet from > the code: > > ============================== > void configure(){ > > // inputs > > from("stream:file?fileName=/Users/test/dude.log&scanStream=true&scanStreamDelay=50"). > process(new AddSourceProcessor('file1')). > to("seda:logmsgs?size=10000&concurrentConsumers=5") > > from("jetty:http://localhost:8081/msgs"). > process(new AddSourceProcessor('file3')). > to("seda:logmsgs?size=10000&concurrentConsumers=5") > > // output: http://localhost:8082 > from("seda:logmsgs?size=10000&concurrentConsumers=5"). > to("cometd://127.0.0.1:8082/service/logs?baseResource=file:webapp") > } > > def camelCtx = new DefaultCamelContext() > camelCtx.addRoutes(new SampleRoute()); > camelCtx.start(); > ============================== > > If I remove the "Jetty" route from the Groovy script it will no longer > run. What is exactly doing the jetty route? > Is it there just to start the jetty server? And why the input endpoint is > set to "http://localhost:8081/msgs"? > > Thanks > Luciano > -- View this message in context: http://camel.465427.n5.nabble.com/Newbie-question-regarding-Comet-Jetty-tp4257988p4258156.html Sent from the Camel - Users mailing list archive at Nabble.com.