The endpoint is being started while spring is starting up as well, and that causes spring to fuckup.
We should defer starting the endpoint while the app is in the starting process. Those other endpoints are simpler and do not contain custom start logic like quartz does. On Fri, Apr 1, 2016 at 11:11 AM, Hubertus.Willuhn <hubertus.will...@dinsoftware.de> wrote: > Ok, this seems weird because i got other routes doing the same thing (calling > endpoint() method) > for the file, direct, or seda component of spring and non of them having > this issue. > > And shouldn't do the Endpoint instance the same as a URI-String? > > Any clearification would be nice..if its not to long though ^^ > Maybe i should report this to spring then? > > Best regards > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Quartz2-Endpoint-Exception-tp5780221p5780226.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
