Debugging and tracing camel-3.0.0 on OSGi
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.
Re: Debugging and tracing camel-3.0.0 on OSGi
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 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
Re: Debugging and tracing camel-3.0.0 on OSGi
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 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 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
AW: [ANNOUNCEMENT] Apache Camel 3.0.0 Released
Hi, But camel-spring-boot-starter is still 3.0.0-RC3 ? -Ursprüngliche Nachricht- Von: Grzegorz Grzybek Gesendet: Freitag, 29. November 2019 15:37 An: users@camel.apache.org Cc: d...@camel.apache.org Betreff: Re: [ANNOUNCEMENT] Apache Camel 3.0.0 Released Congratulations! Time to celebrate - amazing work! regards Grzegorz Grzybek pt., 29 lis 2019 o 03:56 Tadayoshi Sato napisał(a): > Congratulations! It's an epic release indeed! > > Thanks everyone for making it happen! > > Best regards, > Tadayoshi > > On Thu, Nov 28, 2019 at 11:13 PM Gregor Zurowski > > > wrote: > > > It's finally here - after four release candidates and three > > milestone releases, the Camel community announces the immediate > > availability of Camel 3.0.0, a new major release with over 1000 new > > features, improvements and fixes. > > > > Please read our migration guide [1] that describes how to upgrade > > Camel 2.x applications to Camel 3.0. > > > > The artifacts are published and ready for you to download [2] either > > from the Apache mirrors or from the Central Maven repository. For > > more details please take a look at the release notes [3, 4]. > > > > Many thanks to all who made this release possible. > > > > On behalf of the Camel PMC, > > Gregor Zurowski > > > > [1] > > https://camel.apache.org/manual/latest/camel-3-migration-guide.html > > [1] http://camel.apache.org/download.html > > [2] https://camel.apache.org/blog/release-3-0-0.html > > [3] > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=1231569 > 1&projectId=12311211 > > > > > -- > Tadayoshi Sato >
Re: [ANNOUNCEMENT] Apache Camel 3.0.0 Released
The groupId of the starters has been changed from org.apache.camel to org.apache.camel.springboot https://search.maven.org/search?q=g:org.apache.camel.springboot Il giorno lun 2 dic 2019 alle ore 15:23 ha scritto: > Hi, > > But camel-spring-boot-starter is still 3.0.0-RC3 ? > > -Ursprüngliche Nachricht- > Von: Grzegorz Grzybek > Gesendet: Freitag, 29. November 2019 15:37 > An: users@camel.apache.org > Cc: d...@camel.apache.org > Betreff: Re: [ANNOUNCEMENT] Apache Camel 3.0.0 Released > > Congratulations! > > Time to celebrate - amazing work! > > regards > Grzegorz Grzybek > > pt., 29 lis 2019 o 03:56 Tadayoshi Sato > napisał(a): > > > Congratulations! It's an epic release indeed! > > > > Thanks everyone for making it happen! > > > > Best regards, > > Tadayoshi > > > > On Thu, Nov 28, 2019 at 11:13 PM Gregor Zurowski > > > > > > wrote: > > > > > It's finally here - after four release candidates and three > > > milestone releases, the Camel community announces the immediate > > > availability of Camel 3.0.0, a new major release with over 1000 new > > > features, improvements and fixes. > > > > > > Please read our migration guide [1] that describes how to upgrade > > > Camel 2.x applications to Camel 3.0. > > > > > > The artifacts are published and ready for you to download [2] either > > > from the Apache mirrors or from the Central Maven repository. For > > > more details please take a look at the release notes [3, 4]. > > > > > > Many thanks to all who made this release possible. > > > > > > On behalf of the Camel PMC, > > > Gregor Zurowski > > > > > > [1] > > > https://camel.apache.org/manual/latest/camel-3-migration-guide.html > > > [1] http://camel.apache.org/download.html > > > [2] https://camel.apache.org/blog/release-3-0-0.html > > > [3] > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=1231569 > > 1&projectId=12311211 > > > > > > > > > -- > > Tadayoshi Sato > > >
Re: [ANNOUNCEMENT] Apache Camel 3.0.0 Released
It's in the migration guide by the way https://camel.apache.org/manual/latest/camel-3-migration-guide.html#_spring_boot_starters_maven_coordinate_change Il giorno lun 2 dic 2019 alle ore 15:24 Andrea Cosentino ha scritto: > The groupId of the starters has been changed > from org.apache.camel to org.apache.camel.springboot > > https://search.maven.org/search?q=g:org.apache.camel.springboot > > Il giorno lun 2 dic 2019 alle ore 15:23 ha > scritto: > >> Hi, >> >> But camel-spring-boot-starter is still 3.0.0-RC3 ? >> >> -Ursprüngliche Nachricht- >> Von: Grzegorz Grzybek >> Gesendet: Freitag, 29. November 2019 15:37 >> An: users@camel.apache.org >> Cc: d...@camel.apache.org >> Betreff: Re: [ANNOUNCEMENT] Apache Camel 3.0.0 Released >> >> Congratulations! >> >> Time to celebrate - amazing work! >> >> regards >> Grzegorz Grzybek >> >> pt., 29 lis 2019 o 03:56 Tadayoshi Sato >> napisał(a): >> >> > Congratulations! It's an epic release indeed! >> > >> > Thanks everyone for making it happen! >> > >> > Best regards, >> > Tadayoshi >> > >> > On Thu, Nov 28, 2019 at 11:13 PM Gregor Zurowski >> > > > > >> > wrote: >> > >> > > It's finally here - after four release candidates and three >> > > milestone releases, the Camel community announces the immediate >> > > availability of Camel 3.0.0, a new major release with over 1000 new >> > > features, improvements and fixes. >> > > >> > > Please read our migration guide [1] that describes how to upgrade >> > > Camel 2.x applications to Camel 3.0. >> > > >> > > The artifacts are published and ready for you to download [2] either >> > > from the Apache mirrors or from the Central Maven repository. For >> > > more details please take a look at the release notes [3, 4]. >> > > >> > > Many thanks to all who made this release possible. >> > > >> > > On behalf of the Camel PMC, >> > > Gregor Zurowski >> > > >> > > [1] >> > > https://camel.apache.org/manual/latest/camel-3-migration-guide.html >> > > [1] http://camel.apache.org/download.html >> > > [2] https://camel.apache.org/blog/release-3-0-0.html >> > > [3] >> > > >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=1231569 >> > 1&projectId=12311211 >> > > >> > >> > >> > -- >> > Tadayoshi Sato >> > >> >
AW: [ANNOUNCEMENT] Apache Camel 3.0.0 Released
A. Thanks. Didn't expect this from 3.0.0-RC3 to 3.0.0 -Ursprüngliche Nachricht- Von: Andrea Cosentino Gesendet: Montag, 2. Dezember 2019 15:25 An: users@camel.apache.org Cc: dev Betreff: Re: [ANNOUNCEMENT] Apache Camel 3.0.0 Released The groupId of the starters has been changed from org.apache.camel to org.apache.camel.springboot https://search.maven.org/search?q=g:org.apache.camel.springboot Il giorno lun 2 dic 2019 alle ore 15:23 ha scritto: > Hi, > > But camel-spring-boot-starter is still 3.0.0-RC3 ? > > -Ursprüngliche Nachricht- > Von: Grzegorz Grzybek > Gesendet: Freitag, 29. November 2019 15:37 > An: users@camel.apache.org > Cc: d...@camel.apache.org > Betreff: Re: [ANNOUNCEMENT] Apache Camel 3.0.0 Released > > Congratulations! > > Time to celebrate - amazing work! > > regards > Grzegorz Grzybek > > pt., 29 lis 2019 o 03:56 Tadayoshi Sato > napisał(a): > > > Congratulations! It's an epic release indeed! > > > > Thanks everyone for making it happen! > > > > Best regards, > > Tadayoshi > > > > On Thu, Nov 28, 2019 at 11:13 PM Gregor Zurowski > > > > > > wrote: > > > > > It's finally here - after four release candidates and three > > > milestone releases, the Camel community announces the immediate > > > availability of Camel 3.0.0, a new major release with over 1000 > > > new features, improvements and fixes. > > > > > > Please read our migration guide [1] that describes how to upgrade > > > Camel 2.x applications to Camel 3.0. > > > > > > The artifacts are published and ready for you to download [2] > > > either from the Apache mirrors or from the Central Maven > > > repository. For more details please take a look at the release notes [3, > > > 4]. > > > > > > Many thanks to all who made this release possible. > > > > > > On behalf of the Camel PMC, > > > Gregor Zurowski > > > > > > [1] > > > https://camel.apache.org/manual/latest/camel-3-migration-guide.htm > > > l [1] http://camel.apache.org/download.html > > > [2] https://camel.apache.org/blog/release-3-0-0.html > > > [3] > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12315 > > 69 > > 1&projectId=12311211 > > > > > > > > > -- > > Tadayoshi Sato > > >
RE: Debugging and tracing camel-3.0.0 on OSGi
Hi.
Thank you very much, I managed to turn the debugger on using:
public class DebuggerEnablerBean {
public DebuggerEnablerBean(CamelContext camelContext) {
camelContext.setDebugging(true);
}
}
and instantiating this bean in xml:
and it even works now in hawtio!
But is there any way to do this directly from blueprint xml, without using
java? The way I did it looks like a very dirty hack for me.
Maybe there should be an option like "trace=true" (say, "debug=true") on
camelContext?
Konstantin Chernov.
-Original Message-
From: Claus Ibsen
Sent: Monday, December 2, 2019 9:13 PM
To: users@camel.apache.org
Subject: Re: Debugging and tracing camel-3.0.0 on OSGi
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 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 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
Re: Debugging and tracing camel-3.0.0 on OSGi
Hi
Yeah you are welcome to create a JIRA to add backlogTracing=true|false
to spring and blueprint xml
On Mon, Dec 2, 2019 at 3:34 PM wrote:
>
> Hi.
>
> Thank you very much, I managed to turn the debugger on using:
>
> public class DebuggerEnablerBean {
> public DebuggerEnablerBean(CamelContext camelContext) {
> camelContext.setDebugging(true);
> }
> }
>
> and instantiating this bean in xml:
>
>
>
>
> and it even works now in hawtio!
>
> But is there any way to do this directly from blueprint xml, without using
> java? The way I did it looks like a very dirty hack for me.
> Maybe there should be an option like "trace=true" (say, "debug=true") on
> camelContext?
>
>
> Konstantin Chernov.
>
> -Original Message-
> From: Claus Ibsen
> Sent: Monday, December 2, 2019 9:13 PM
> To: users@camel.apache.org
> Subject: Re: Debugging and tracing camel-3.0.0 on OSGi
>
> 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 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 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
>
--
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Configuring Jackson for java.time
Hi Ron,
for Jackson you need to add support for Java 8+ features explicitly.
Have a look at how to do it here:
https://github.com/FasterXML/jackson-modules-java8
Jackson JSON data format has a `objectMapper`[2] property that you can
use to set the customized ObjectMapper.
zoran
[2] https://camel.apache.org/components/latest/json-jackson-dataformat.html
On Mon, Dec 2, 2019 at 6:21 AM Ron Cecchini wrote:
>
> TL;DR: unmarshalling JSON to POJO with Jackson is no longer working on a
> java.time.OffsetDateTime since migrating to Camel 3.0. java.util.Date still
> works fine though.
>
> Ok, after 2 days of googling and trying all manner of sorcery (except for
> sacrificing a chicken... maybe I should?), I'm waving the white flag on this
> one...
>
> Basically, I had worked through all the migration stuff. I also updated
> Spring Boot to 2.2.1.RELEASE, and updated all the *-starter dependencies,
> etc. Everything was working great.
>
> Eventually I uncommented some code I hadn't been using for a while - and
> that's when the "fun" began...
>
> The input to the route in question is a JSON array upon which I do a
> .split().jsonpathWriteAsString("$") and eventually an .unmarshal(pojoJson)
> where 'pojoJson' is:
>
> JacksonDataFormat pojoJson = new JacksonDataFormat(MyPojo.class);
>
> Things were working fantastic before the migration, but now I get:
>
> com.fasterxml.jackson.databind.exc.InvalidDefinitionException:
> Cannot construct instance of `java.time.OffsetDateTime` (no Creators,
> like default construct, exist):
> no String-argument constructor/factory method to deserialize from String
> value ('2019-11-14T04:41:33.302711Z')
>
> Googling revealed all kinds of stuff related to Jackson and Java 8 date/times
> posted over the last few years.
>
> I tried a few of the suggestions, including adding several Jackson-specific
> dependencies (to go along with
> 'org.apache.camel.springboot:camel-jackson-starter') - and adding the
> dependencies in different orders (someone said that could be a factor) - and
> nothing worked.
>
> Based on a few suggestions, I even created the following @PostConstruct
> method in my @SpringBootApplication class, and again got the same "no
> Creators" error:
>
> @PostConstruct
> public void setUp ()
> {
> context.getGlobalOptions().put("CamelJacksonEnableTypeConverter",
> "true");
> context.getGlobalOptions().put("CamelJacksonTypeConverterToPojo",
> "true");
>
> objectMapper.registerModule(new JavaTimeModule());
> objectMapper.registerModule(new JSR310Module());
> objectMapper.registerModule(new Jdk8Module());
> objectMapper.findAndRegisterModules();
> }
>
> I even tried switching jsonpathWriteAsString("$") to jsonpath("$"), setting
> pojoJson.useMap(), and passing the Map from jsonpath() to unmarshal, and this
> time got:
>
> Caused by: org.apache.camel.NoTypeConversionAvailableException:
> No type converter available to convert from type: java.util.LinkedHashMap
> to the required type:
> java.io.InputStream with value [...]
>
> I finally hit on a temporary workaround - going back to using a
> java.util.Date instead of a java.time.OffsetDateTime - and it again all works
> great with Camel 3.0. But eventually I'll probably need to figure out how to
> use the newer Java date/times.
>
> Thanks for reading this far and helping me figure out where I went wrong...
>
> > On November 28, 2019 at 2:09 PM Ron Cecchini
> > wrote:
> >
> >
> > Christmas has come early!
> >
> > There's so much new stuff I'm not even sure what I should be excited about
> > at the moment - but I'm excited!
> >
> > Thank you for all your efforts, guys!
> >
> > (and now I can spend pre-Thanksgiving feasting working through the
> > Migration and eliminating the run-time crashes...)
> >
> > > On November 28, 2019 at 9:12 AM Gregor Zurowski
> > > wrote:
> > >
> > >
> > > It's finally here - after four release candidates and three milestone
> > > releases, the Camel community announces the immediate availability of
> > > Camel 3.0.0, a new major release with over 1000 new features,
> > > improvements and fixes.
> > >
> > > Please read our migration guide [1] that describes how to upgrade
> > > Camel 2.x applications to Camel 3.0.
> > >
> > > The artifacts are published and ready for you to download [2] either
> > > from the Apache mirrors or from the Central Maven repository. For more
> > > details please take a look at the release notes [3, 4].
> > >
> > > Many thanks to all who made this release possible.
> > >
> > > On behalf of the Camel PMC,
> > > Gregor Zurowski
> > >
> > > [1] https://camel.apache.org/manual/latest/camel-3-migration-guide.html
> > > [1] http://camel.apache.org/download.html
> > > [2] https://camel.apache.org/blog/release-3-0-0.html
> > > [3]
> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12315691&projectId=12311211
--
Zoran Regvart
RE: Debugging and tracing camel-3.0.0 on OSGi
Thanks!
https://issues.apache.org/jira/browse/CAMEL-14240
Konstantin Chernov.
-Original Message-
From: Claus Ibsen
Sent: Monday, December 2, 2019 10:01 PM
To: users@camel.apache.org
Subject: Re: Debugging and tracing camel-3.0.0 on OSGi
Hi
Yeah you are welcome to create a JIRA to add backlogTracing=true|false to
spring and blueprint xml
On Mon, Dec 2, 2019 at 3:34 PM wrote:
>
> Hi.
>
> Thank you very much, I managed to turn the debugger on using:
>
> public class DebuggerEnablerBean {
> public DebuggerEnablerBean(CamelContext camelContext) {
> camelContext.setDebugging(true);
> }
> }
>
> and instantiating this bean in xml:
>
>
>
>
> and it even works now in hawtio!
>
> But is there any way to do this directly from blueprint xml, without using
> java? The way I did it looks like a very dirty hack for me.
> Maybe there should be an option like "trace=true" (say, "debug=true") on
> camelContext?
>
>
> Konstantin Chernov.
>
> -Original Message-
> From: Claus Ibsen
> Sent: Monday, December 2, 2019 9:13 PM
> To: users@camel.apache.org
> Subject: Re: Debugging and tracing camel-3.0.0 on OSGi
>
> 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 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 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
>
--
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
file component to access doneFileName option
I have one requirement to transfer file depends on the done file name
for example, in the drop folder inputDir, if there is file named
123456.done dropped, I need to move all the file whose name including
123456 to outputDir. if there is file named 456789.done dropped, I need to
move all the files whose name including 456789 to outputDir.
I know that we have doneFileName=${filel.name}.done, but how to reuse this
${file.name} in the include regular expression to filter file name?
file://inputDir?delete=true&include=^.*_ ${file.name
}_[0-9]{5}.dat$&doneFilenName=${file.name}.ready
thanks
--
~
Weiquan Yuan
Located in Ottawa, Canada
Re: file component to access doneFileName option
Hi
Instead of using doneFileName which AFAIR is a 1:1 with file and done
file, then you can implement a custom file filter and configure on the
file endpoint, and then return true|false whether you can find a done
file name yourself via the java api.
On Mon, Dec 2, 2019 at 9:41 PM WEIQUAN YUAN wrote:
>
> I have one requirement to transfer file depends on the done file name
>
> for example, in the drop folder inputDir, if there is file named
> 123456.done dropped, I need to move all the file whose name including
> 123456 to outputDir. if there is file named 456789.done dropped, I need to
> move all the files whose name including 456789 to outputDir.
>
> I know that we have doneFileName=${filel.name}.done, but how to reuse this
> ${file.name} in the include regular expression to filter file name?
>
> file://inputDir?delete=true&include=^.*_ ${file.name
> }_[0-9]{5}.dat$&doneFilenName=${file.name}.ready
>
>
> thanks
>
> --
> ~
> Weiquan Yuan
> Located in Ottawa, Canada
--
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
