I see it twice! Once for the root application context (which is correct, because its the context where the camel context is defined in) and a second time for the web application context (which I think is incorrect because it's the child context of the root).
I don't know if it would work in all cases if the applicationContext instance of the refresh event would be evaulated and only refresh events for the applicationContext of the camel context is processed ... -- View this message in context: http://www.nabble.com/How-to-prevent-routes-from-started-twice--tp23983653p23997647.html Sent from the Camel - Users mailing list archive at Nabble.com.
