I logged a ticket about the missing XSDs https://issues.apache.org/jira/browse/CAMEL-14239
On Mon, Dec 2, 2019 at 3:07 PM Claus Ibsen <claus.ib...@gmail.com> wrote: > > Hi > > You need to turn on tracing before starting Camel in Camel 3 to have JMX > tracer. > > context.setBacklogTracing(true); > > > And the poor mans debugger is a feature we no longer want to provide > out of the box in Camel and its removed. > > > > On Mon, Dec 2, 2019 at 2:49 PM <k.j.cher...@gmail.com> wrote: > > > > Hello. > > > > Is there any way to trace or debug the camel routes in 3.0.0 when starting > > camel context through OSGi Blueprint? > > I tried looking for BacklogDebugger/BacklogTracer MBeans on JMX without any > > luck (though I can see the context/processor/routes there). > > Debug/trace tabs just gone missing from my hawtio console after update from > > 2.24. I only managed to find an issue > > https://issues.apache.org/jira/browse/CAMEL-13759 > > stating that "There is already the newer backlog debugger that hawtio and > > other tools uses for debugging.", so I believe there must be a way to make > > it work somehow. > > Setting trace=true on camelContext only creates a DefaultTracer, which does > > not seem to be reporting any notifications through JMX. > > > > Using Java 11 + Karaf 4.2.7 + Hawtio 2.8.0 + Camel 3.0.0. > > > > P.S.> It looks like the blueprint xsd for 3.0.0 is missing from the > > http://camel.apache.org/schema/blueprint/ at all. Is there any other place > > where the schemas reside (besides the camel-blueprint jar)? > > > > Thanks in advance, > > Konstantin Chernov. > > > > > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
