DefaultComponent
Hi, I got this error. What is missing? java.lang.NoClassDefFoundError: org/apache/camel/impl/DefaultComponent Stacktrace: java.lang.NoClassDefFoundError: org/apache/camel/impl/DefaultComponent at java.base/java.lang.ClassLoader.defineClass1(Native Method) ~[na:na] at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1016) ~[na:na] at java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:174) ~[na:na] at java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:802) ~[na:na] at java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:700) ~[na:na] at java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:623) ~[na:na] at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581) ~[na:na] at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) ~[na:na] at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) ~[na:na] at org.apache.camel.util.ObjectHelper.doLoadClass(ObjectHelper.java:474) ~[camel-util-3.0.0.jar:3.0.0] at org.apache.camel.util.ObjectHelper.loadClass(ObjectHelper.java:378) ~[camel-util-3.0.0.jar:3.0.0] at org.apache.camel.util.ObjectHelper.loadClass(ObjectHelper.java:355) ~[camel-util-3.0.0.jar:3.0.0] at org.apache.camel.impl.engine.DefaultClassResolver.loadClass(DefaultClassResolver.java:140) ~[camel-base-3.0.0.jar:3.0.0] at org.apache.camel.impl.engine.DefaultClassResolver.resolveClass(DefaultClassResolver.java:55) ~[camel-base-3.0.0.jar:3.0.0] at org.apache.camel.impl.engine.DefaultFactoryFinder.doNewInstance(DefaultFactoryFinder.java:120) ~[camel-base-3.0.0.jar:3.0.0] at org.apache.camel.impl.engine.DefaultFactoryFinder.lambda$findClass$0(DefaultFactoryFinder.java:77) ~[camel-base-3.0.0.jar:3.0.0] at org.apache.camel.impl.engine.DefaultFactoryFinder$1.apply(DefaultFactoryFinder.java:155) ~[camel-base-3.0.0.jar:3.0.0] at org.apache.camel.impl.engine.DefaultFactoryFinder$1.apply(DefaultFactoryFinder.java:151) ~[camel-base-3.0.0.jar:3.0.0] at java.base/java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1705) ~[na:na] at org.apache.camel.impl.engine.DefaultFactoryFinder.addToClassMap(DefaultFactoryFinder.java:151) ~[camel-base-3.0.0.jar:3.0.0] at org.apache.camel.impl.engine.DefaultFactoryFinder.findClass(DefaultFactoryFinder.java:74) ~[camel-base-3.0.0.jar:3.0.0] at org.apache.camel.impl.engine.DefaultFactoryFinder.findClass(DefaultFactoryFinder.java:66) ~[camel-base-3.0.0.jar:3.0.0] at org.apache.camel.impl.engine.DefaultComponentResolver.findComponent(DefaultComponentResolver.java:83) ~[camel-base-3.0.0.jar:3.0.0] at org.apache.camel.impl.engine.DefaultComponentResolver.resolveComponent(DefaultComponentResolver.java:56) ~[camel-base-3.0.0.jar:3.0.0] at org.apache.camel.impl.engine.AbstractCamelContext.initComponent(AbstractCamelContext.java:568) ~[camel-base-3.0.0.jar:3.0.0] at org.apache.camel.impl.engine.AbstractCamelContext.access$000(AbstractCamelContext.java:165) ~[camel-base-3.0.0.jar:3.0.0] at org.apache.camel.impl.engine.AbstractCamelContext$2.apply(AbstractCamelContext.java:496) ~[camel-base-3.0.0.jar:3.0.0] at org.apache.camel.impl.engine.AbstractCamelContext$2.apply(AbstractCamelContext.java:492) ~[camel-base-3.0.0.jar:3.0.0] at java.base/java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1705) ~[na:na] at org.apache.camel.impl.engine.AbstractCamelContext.getComponent(AbstractCamelContext.java:492) ~[camel-base-3.0.0.jar:3.0.0] at org.apache.camel.impl.engine.AbstractCamelContext.getComponent(AbstractCamelContext.java:468) ~[camel-base-3.0.0.jar:3.0.0] at org.apache.camel.impl.engine.AbstractCamelContext.getEndpoint(AbstractCamelContext.java:745) ~[camel-base-3.0.0.jar:3.0.0] at org.apache.camel.support.CamelContextHelper.getMandatoryEndpoint(CamelContextHelper.java:55) ~[camel-support-3.0.0.jar:3.0.0] at org.apache.camel.impl.engine.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:120) ~[camel-base-3.0.0.jar:3.0.0] at org.apache.camel.reifier.RouteReifier.doCreateRoute(RouteReifier.java:363) ~[camel-core-engine-3.0.0.jar:3.0.0] at org.apache.camel.reifier.RouteReifier.createRoute(RouteReifier.java:108) ~[camel-core-engine-3.0.0.jar:3.0.0] at org.apache.camel.impl.DefaultModel.start(DefaultModel.java:356) ~[camel-core-engine-3.0.0.jar:3.0.0] at org.apache.camel.impl.DefaultModel.startRoute(DefaultModel.java:330) ~[camel-core-engine-3.0.0.jar:3.0.0] at org.apache.camel.impl.DefaultModel.startRouteDefinitions(DefaultModel.java
Re: DefaultComponent
In Camel 3 the DefaultComponent is located at org.apache.camel.support It is reported in the migration guide https://camel.apache.org/manual/latest/camel-3-migration-guide.html#_migrating_custom_components Il giorno mar 3 dic 2019 alle ore 12:59 ha scritto: > Hi, > > I got this error. What is missing? > > java.lang.NoClassDefFoundError: org/apache/camel/impl/DefaultComponent > > Stacktrace: > > java.lang.NoClassDefFoundError: org/apache/camel/impl/DefaultComponent > at java.base/java.lang.ClassLoader.defineClass1(Native Method) > ~[na:na] > at > java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1016) ~[na:na] > at > java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:174) > ~[na:na] > at > java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:802) > ~[na:na] > at > java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:700) > ~[na:na] > at > java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:623) > ~[na:na] > at > java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581) > ~[na:na] > at > java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) > ~[na:na] > at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) > ~[na:na] > at > org.apache.camel.util.ObjectHelper.doLoadClass(ObjectHelper.java:474) > ~[camel-util-3.0.0.jar:3.0.0] > at > org.apache.camel.util.ObjectHelper.loadClass(ObjectHelper.java:378) > ~[camel-util-3.0.0.jar:3.0.0] > at > org.apache.camel.util.ObjectHelper.loadClass(ObjectHelper.java:355) > ~[camel-util-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.DefaultClassResolver.loadClass(DefaultClassResolver.java:140) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.DefaultClassResolver.resolveClass(DefaultClassResolver.java:55) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.DefaultFactoryFinder.doNewInstance(DefaultFactoryFinder.java:120) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.DefaultFactoryFinder.lambda$findClass$0(DefaultFactoryFinder.java:77) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.DefaultFactoryFinder$1.apply(DefaultFactoryFinder.java:155) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.DefaultFactoryFinder$1.apply(DefaultFactoryFinder.java:151) > ~[camel-base-3.0.0.jar:3.0.0] > at > java.base/java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1705) > ~[na:na] > at > org.apache.camel.impl.engine.DefaultFactoryFinder.addToClassMap(DefaultFactoryFinder.java:151) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.DefaultFactoryFinder.findClass(DefaultFactoryFinder.java:74) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.DefaultFactoryFinder.findClass(DefaultFactoryFinder.java:66) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.DefaultComponentResolver.findComponent(DefaultComponentResolver.java:83) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.DefaultComponentResolver.resolveComponent(DefaultComponentResolver.java:56) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.AbstractCamelContext.initComponent(AbstractCamelContext.java:568) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.AbstractCamelContext.access$000(AbstractCamelContext.java:165) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.AbstractCamelContext$2.apply(AbstractCamelContext.java:496) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.AbstractCamelContext$2.apply(AbstractCamelContext.java:492) > ~[camel-base-3.0.0.jar:3.0.0] > at > java.base/java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1705) > ~[na:na] > at > org.apache.camel.impl.engine.AbstractCamelContext.getComponent(AbstractCamelContext.java:492) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.AbstractCamelContext.getComponent(AbstractCamelContext.java:468) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.AbstractCamelContext.getEndpoint(AbstractCamelContext.java:745) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.support.CamelContextHelper.getMandatoryEndpoint(CamelContextHelper.java:55) > ~[camel-support-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:120) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.reifier.RouteReifier.doCreateRoute(RouteReifier.java:363) > ~[camel-core-engine-3.0.0.jar:3.0.0] > at > org.apach
RE: Debugging and tracing camel-3.0.0 on OSGi
Hi,
Looks like setting backlogTracing on context only turns on the tracing
possibility.
Shouldn't there be another option backlogDebugging=true|false ?
Konstantin Chernov.
-Original Message-
From: k.j.cher...@gmail.com
Sent: Monday, December 2, 2019 10:13 PM
To: users@camel.apache.org
Subject: 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
AW: DefaultComponent
Yes. I know and my own components use this. But it seems spring or flowable needs this class there. -Ursprüngliche Nachricht- Von: Andrea Cosentino Gesendet: Dienstag, 3. Dezember 2019 13:01 An: users@camel.apache.org Cc: dev Betreff: Re: DefaultComponent In Camel 3 the DefaultComponent is located at org.apache.camel.support It is reported in the migration guide https://camel.apache.org/manual/latest/camel-3-migration-guide.html#_migrating_custom_components Il giorno mar 3 dic 2019 alle ore 12:59 ha scritto: > Hi, > > I got this error. What is missing? > > java.lang.NoClassDefFoundError: org/apache/camel/impl/DefaultComponent > > Stacktrace: > > java.lang.NoClassDefFoundError: org/apache/camel/impl/DefaultComponent > at java.base/java.lang.ClassLoader.defineClass1(Native Method) > ~[na:na] > at > java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1016) ~[na:na] > at > java.base/java.security.SecureClassLoader.defineClass(SecureClassLoade > r.java:174) > ~[na:na] > at > java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinCl > assLoader.java:802) > ~[na:na] > at > java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathO > rNull(BuiltinClassLoader.java:700) > ~[na:na] > at > java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(Built > inClassLoader.java:623) > ~[na:na] > at > java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClas > sLoader.java:581) > ~[na:na] > at > java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(Cl > assLoaders.java:178) > ~[na:na] > at > java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) > ~[na:na] > at > org.apache.camel.util.ObjectHelper.doLoadClass(ObjectHelper.java:474) > ~[camel-util-3.0.0.jar:3.0.0] > at > org.apache.camel.util.ObjectHelper.loadClass(ObjectHelper.java:378) > ~[camel-util-3.0.0.jar:3.0.0] > at > org.apache.camel.util.ObjectHelper.loadClass(ObjectHelper.java:355) > ~[camel-util-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.DefaultClassResolver.loadClass(DefaultCla > ssResolver.java:140) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.DefaultClassResolver.resolveClass(Default > ClassResolver.java:55) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.DefaultFactoryFinder.doNewInstance(Defaul > tFactoryFinder.java:120) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.DefaultFactoryFinder.lambda$findClass$0(D > efaultFactoryFinder.java:77) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.DefaultFactoryFinder$1.apply(DefaultFacto > ryFinder.java:155) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.DefaultFactoryFinder$1.apply(DefaultFacto > ryFinder.java:151) > ~[camel-base-3.0.0.jar:3.0.0] > at > java.base/java.util.concurrent.ConcurrentHashMap.computeIfAbsent(Concu > rrentHashMap.java:1705) > ~[na:na] > at > org.apache.camel.impl.engine.DefaultFactoryFinder.addToClassMap(Defaul > tFactoryFinder.java:151) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.DefaultFactoryFinder.findClass(DefaultFac > toryFinder.java:74) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.DefaultFactoryFinder.findClass(DefaultFac > toryFinder.java:66) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.DefaultComponentResolver.findComponent(De > faultComponentResolver.java:83) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.DefaultComponentResolver.resolveComponent > (DefaultComponentResolver.java:56) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.AbstractCamelContext.initComponent(Abstra > ctCamelContext.java:568) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.AbstractCamelContext.access$000(AbstractC > amelContext.java:165) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.AbstractCamelContext$2.apply(AbstractCame > lContext.java:496) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.AbstractCamelContext$2.apply(AbstractCame > lContext.java:492) > ~[camel-base-3.0.0.jar:3.0.0] > at > java.base/java.util.concurrent.ConcurrentHashMap.computeIfAbsent(Concu > rrentHashMap.java:1705) > ~[na:na] > at > org.apache.camel.impl.engine.AbstractCamelContext.getComponent(Abstrac > tCamelContext.java:492) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.AbstractCamelContext.getComponent(Abstrac > tCamelContext.java:468) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.impl.engine.AbstractCamelContext.getEndpoint(Abstract > CamelContext.java:745) > ~[camel-base-3.0.0.jar:3.0.0] > at > org.apache.camel.support.CamelContextHelper.getMandatoryEndpoint(Came
Re: Debugging and tracing camel-3.0.0 on OSGi
Hi
Ah okay yeah lets added an option to set this easy in
On Tue, Dec 3, 2019 at 1:07 PM wrote:
>
> Hi,
>
> Looks like setting backlogTracing on context only turns on the tracing
> possibility.
> Shouldn't there be another option backlogDebugging=true|false ?
>
> Konstantin Chernov.
>
> -Original Message-
> From: k.j.cher...@gmail.com
> Sent: Monday, December 2, 2019 10:13 PM
> To: users@camel.apache.org
> Subject: 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
>
>
--
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: DefaultComponent
Hi If you have custom components you need to source code migrate them to Camel 3 and rebuild them. Camel 3 does not run with Camel 2 components. On Tue, Dec 3, 2019 at 1:21 PM wrote: > > Yes. I know and my own components use this. But it seems spring or flowable > needs this class there. > > > -Ursprüngliche Nachricht- > Von: Andrea Cosentino > Gesendet: Dienstag, 3. Dezember 2019 13:01 > An: users@camel.apache.org > Cc: dev > Betreff: Re: DefaultComponent > > In Camel 3 the DefaultComponent is located at > > org.apache.camel.support > > It is reported in the migration guide > > https://camel.apache.org/manual/latest/camel-3-migration-guide.html#_migrating_custom_components > > Il giorno mar 3 dic 2019 alle ore 12:59 ha > scritto: > > > Hi, > > > > I got this error. What is missing? > > > > java.lang.NoClassDefFoundError: org/apache/camel/impl/DefaultComponent > > > > Stacktrace: > > > > java.lang.NoClassDefFoundError: org/apache/camel/impl/DefaultComponent > > at java.base/java.lang.ClassLoader.defineClass1(Native Method) > > ~[na:na] > > at > > java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1016) ~[na:na] > > at > > java.base/java.security.SecureClassLoader.defineClass(SecureClassLoade > > r.java:174) > > ~[na:na] > > at > > java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinCl > > assLoader.java:802) > > ~[na:na] > > at > > java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathO > > rNull(BuiltinClassLoader.java:700) > > ~[na:na] > > at > > java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(Built > > inClassLoader.java:623) > > ~[na:na] > > at > > java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClas > > sLoader.java:581) > > ~[na:na] > > at > > java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(Cl > > assLoaders.java:178) > > ~[na:na] > > at > > java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) > > ~[na:na] > > at > > org.apache.camel.util.ObjectHelper.doLoadClass(ObjectHelper.java:474) > > ~[camel-util-3.0.0.jar:3.0.0] > > at > > org.apache.camel.util.ObjectHelper.loadClass(ObjectHelper.java:378) > > ~[camel-util-3.0.0.jar:3.0.0] > > at > > org.apache.camel.util.ObjectHelper.loadClass(ObjectHelper.java:355) > > ~[camel-util-3.0.0.jar:3.0.0] > > at > > org.apache.camel.impl.engine.DefaultClassResolver.loadClass(DefaultCla > > ssResolver.java:140) > > ~[camel-base-3.0.0.jar:3.0.0] > > at > > org.apache.camel.impl.engine.DefaultClassResolver.resolveClass(Default > > ClassResolver.java:55) > > ~[camel-base-3.0.0.jar:3.0.0] > > at > > org.apache.camel.impl.engine.DefaultFactoryFinder.doNewInstance(Defaul > > tFactoryFinder.java:120) > > ~[camel-base-3.0.0.jar:3.0.0] > > at > > org.apache.camel.impl.engine.DefaultFactoryFinder.lambda$findClass$0(D > > efaultFactoryFinder.java:77) > > ~[camel-base-3.0.0.jar:3.0.0] > > at > > org.apache.camel.impl.engine.DefaultFactoryFinder$1.apply(DefaultFacto > > ryFinder.java:155) > > ~[camel-base-3.0.0.jar:3.0.0] > > at > > org.apache.camel.impl.engine.DefaultFactoryFinder$1.apply(DefaultFacto > > ryFinder.java:151) > > ~[camel-base-3.0.0.jar:3.0.0] > > at > > java.base/java.util.concurrent.ConcurrentHashMap.computeIfAbsent(Concu > > rrentHashMap.java:1705) > > ~[na:na] > > at > > org.apache.camel.impl.engine.DefaultFactoryFinder.addToClassMap(Defaul > > tFactoryFinder.java:151) > > ~[camel-base-3.0.0.jar:3.0.0] > > at > > org.apache.camel.impl.engine.DefaultFactoryFinder.findClass(DefaultFac > > toryFinder.java:74) > > ~[camel-base-3.0.0.jar:3.0.0] > > at > > org.apache.camel.impl.engine.DefaultFactoryFinder.findClass(DefaultFac > > toryFinder.java:66) > > ~[camel-base-3.0.0.jar:3.0.0] > > at > > org.apache.camel.impl.engine.DefaultComponentResolver.findComponent(De > > faultComponentResolver.java:83) > > ~[camel-base-3.0.0.jar:3.0.0] > > at > > org.apache.camel.impl.engine.DefaultComponentResolver.resolveComponent > > (DefaultComponentResolver.java:56) > > ~[camel-base-3.0.0.jar:3.0.0] > > at > > org.apache.camel.impl.engine.AbstractCamelContext.initComponent(Abstra > > ctCamelContext.java:568) > > ~[camel-base-3.0.0.jar:3.0.0] > > at > > org.apache.camel.impl.engine.AbstractCamelContext.access$000(AbstractC > > amelContext.java:165) > > ~[camel-base-3.0.0.jar:3.0.0] > > at > > org.apache.camel.impl.engine.AbstractCamelContext$2.apply(AbstractCame > > lContext.java:496) > > ~[camel-base-3.0.0.jar:3.0.0] > > at > > org.apache.camel.impl.engine.AbstractCamelContext$2.apply(AbstractCame > > lContext.java:492) > > ~[camel-base-3.0.0.jar:3.0.0] > > at > > java.base/java.util.concurrent.ConcurrentHashMap.computeIfAbsent(Concu > > rrentHashMap.java:1705) > > ~[na:na] > > at > > org.apache.camel.impl.engine.AbstractCamel
AW: DefaultComponent
Its not my components. Its spring boot or flowable. But I cannot see in dependeny tree where flowble-camel uses camel-core or camel-support. When I patch the classes DefaultComponent /-Consumer etc. it works. -Ursprüngliche Nachricht- Von: Claus Ibsen Gesendet: Dienstag, 3. Dezember 2019 13:29 An: users@camel.apache.org Betreff: Re: DefaultComponent Hi If you have custom components you need to source code migrate them to Camel 3 and rebuild them. Camel 3 does not run with Camel 2 components. On Tue, Dec 3, 2019 at 1:21 PM wrote: > > Yes. I know and my own components use this. But it seems spring or flowable > needs this class there. > > > -Ursprüngliche Nachricht- > Von: Andrea Cosentino > Gesendet: Dienstag, 3. Dezember 2019 13:01 > An: users@camel.apache.org > Cc: dev > Betreff: Re: DefaultComponent > > In Camel 3 the DefaultComponent is located at > > org.apache.camel.support > > It is reported in the migration guide > > https://camel.apache.org/manual/latest/camel-3-migration-guide.html#_m > igrating_custom_components > > Il giorno mar 3 dic 2019 alle ore 12:59 ha > scritto: > > > Hi, > > > > I got this error. What is missing? > > > > java.lang.NoClassDefFoundError: > > org/apache/camel/impl/DefaultComponent > > > > Stacktrace: > > > > java.lang.NoClassDefFoundError: org/apache/camel/impl/DefaultComponent > > at java.base/java.lang.ClassLoader.defineClass1(Native > > Method) ~[na:na] > > at > > java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1016) ~[na:na] > > at > > java.base/java.security.SecureClassLoader.defineClass(SecureClassLoa > > de > > r.java:174) > > ~[na:na] > > at > > java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(Builtin > > Cl > > assLoader.java:802) > > ~[na:na] > > at > > java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPat > > hO > > rNull(BuiltinClassLoader.java:700) > > ~[na:na] > > at > > java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(Bui > > lt > > inClassLoader.java:623) > > ~[na:na] > > at > > java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinCl > > as > > sLoader.java:581) > > ~[na:na] > > at > > java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass( > > Cl > > assLoaders.java:178) > > ~[na:na] > > at > > java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) > > ~[na:na] > > at > > org.apache.camel.util.ObjectHelper.doLoadClass(ObjectHelper.java:474 > > ) > > ~[camel-util-3.0.0.jar:3.0.0] > > at > > org.apache.camel.util.ObjectHelper.loadClass(ObjectHelper.java:378) > > ~[camel-util-3.0.0.jar:3.0.0] > > at > > org.apache.camel.util.ObjectHelper.loadClass(ObjectHelper.java:355) > > ~[camel-util-3.0.0.jar:3.0.0] > > at > > org.apache.camel.impl.engine.DefaultClassResolver.loadClass(DefaultC > > la > > ssResolver.java:140) > > ~[camel-base-3.0.0.jar:3.0.0] > > at > > org.apache.camel.impl.engine.DefaultClassResolver.resolveClass(Defau > > lt > > ClassResolver.java:55) > > ~[camel-base-3.0.0.jar:3.0.0] > > at > > org.apache.camel.impl.engine.DefaultFactoryFinder.doNewInstance(Defa > > ul > > tFactoryFinder.java:120) > > ~[camel-base-3.0.0.jar:3.0.0] > > at > > org.apache.camel.impl.engine.DefaultFactoryFinder.lambda$findClass$0 > > (D > > efaultFactoryFinder.java:77) > > ~[camel-base-3.0.0.jar:3.0.0] > > at > > org.apache.camel.impl.engine.DefaultFactoryFinder$1.apply(DefaultFac > > to > > ryFinder.java:155) > > ~[camel-base-3.0.0.jar:3.0.0] > > at > > org.apache.camel.impl.engine.DefaultFactoryFinder$1.apply(DefaultFac > > to > > ryFinder.java:151) > > ~[camel-base-3.0.0.jar:3.0.0] > > at > > java.base/java.util.concurrent.ConcurrentHashMap.computeIfAbsent(Con > > cu > > rrentHashMap.java:1705) > > ~[na:na] > > at > > org.apache.camel.impl.engine.DefaultFactoryFinder.addToClassMap(Defa > > ul > > tFactoryFinder.java:151) > > ~[camel-base-3.0.0.jar:3.0.0] > > at > > org.apache.camel.impl.engine.DefaultFactoryFinder.findClass(DefaultF > > ac > > toryFinder.java:74) > > ~[camel-base-3.0.0.jar:3.0.0] > > at > > org.apache.camel.impl.engine.DefaultFactoryFinder.findClass(DefaultF > > ac > > toryFinder.java:66) > > ~[camel-base-3.0.0.jar:3.0.0] > > at > > org.apache.camel.impl.engine.DefaultComponentResolver.findComponent( > > De > > faultComponentResolver.java:83) > > ~[camel-base-3.0.0.jar:3.0.0] > > at > > org.apache.camel.impl.engine.DefaultComponentResolver.resolveCompone > > nt > > (DefaultComponentResolver.java:56) > > ~[camel-base-3.0.0.jar:3.0.0] > > at > > org.apache.camel.impl.engine.AbstractCamelContext.initComponent(Abst > > ra > > ctCamelContext.java:568) > > ~[camel-base-3.0.0.jar:3.0.0] > > at > > org.apache.camel.impl.engine.AbstractCamelContext.access$000(Abstrac > > tC > > amelContext.java:165) > > ~[camel-base-3.0.0.jar:3.0.0] >
Re: DefaultComponent
Hi Oh didnt know so much about flowable-camel as its 3rd party and not ASF. Same thing, its likely not Camel 3 compatible, so they need to do a new release that supports Camel 3. On Tue, Dec 3, 2019 at 1:36 PM wrote: > > Its not my components. > Its spring boot or flowable. But I cannot see in dependeny tree where > flowble-camel > uses camel-core or camel-support. > > When I patch the classes DefaultComponent /-Consumer etc. it works. > > > -Ursprüngliche Nachricht- > Von: Claus Ibsen > Gesendet: Dienstag, 3. Dezember 2019 13:29 > An: users@camel.apache.org > Betreff: Re: DefaultComponent > > Hi > > If you have custom components you need to source code migrate them to Camel 3 > and rebuild them. Camel 3 does not run with Camel 2 components. > > On Tue, Dec 3, 2019 at 1:21 PM wrote: > > > > Yes. I know and my own components use this. But it seems spring or flowable > > needs this class there. > > > > > > -Ursprüngliche Nachricht- > > Von: Andrea Cosentino > > Gesendet: Dienstag, 3. Dezember 2019 13:01 > > An: users@camel.apache.org > > Cc: dev > > Betreff: Re: DefaultComponent > > > > In Camel 3 the DefaultComponent is located at > > > > org.apache.camel.support > > > > It is reported in the migration guide > > > > https://camel.apache.org/manual/latest/camel-3-migration-guide.html#_m > > igrating_custom_components > > > > Il giorno mar 3 dic 2019 alle ore 12:59 ha > > scritto: > > > > > Hi, > > > > > > I got this error. What is missing? > > > > > > java.lang.NoClassDefFoundError: > > > org/apache/camel/impl/DefaultComponent > > > > > > Stacktrace: > > > > > > java.lang.NoClassDefFoundError: org/apache/camel/impl/DefaultComponent > > > at java.base/java.lang.ClassLoader.defineClass1(Native > > > Method) ~[na:na] > > > at > > > java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1016) > > > ~[na:na] > > > at > > > java.base/java.security.SecureClassLoader.defineClass(SecureClassLoa > > > de > > > r.java:174) > > > ~[na:na] > > > at > > > java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(Builtin > > > Cl > > > assLoader.java:802) > > > ~[na:na] > > > at > > > java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPat > > > hO > > > rNull(BuiltinClassLoader.java:700) > > > ~[na:na] > > > at > > > java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(Bui > > > lt > > > inClassLoader.java:623) > > > ~[na:na] > > > at > > > java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinCl > > > as > > > sLoader.java:581) > > > ~[na:na] > > > at > > > java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass( > > > Cl > > > assLoaders.java:178) > > > ~[na:na] > > > at > > > java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) > > > ~[na:na] > > > at > > > org.apache.camel.util.ObjectHelper.doLoadClass(ObjectHelper.java:474 > > > ) > > > ~[camel-util-3.0.0.jar:3.0.0] > > > at > > > org.apache.camel.util.ObjectHelper.loadClass(ObjectHelper.java:378) > > > ~[camel-util-3.0.0.jar:3.0.0] > > > at > > > org.apache.camel.util.ObjectHelper.loadClass(ObjectHelper.java:355) > > > ~[camel-util-3.0.0.jar:3.0.0] > > > at > > > org.apache.camel.impl.engine.DefaultClassResolver.loadClass(DefaultC > > > la > > > ssResolver.java:140) > > > ~[camel-base-3.0.0.jar:3.0.0] > > > at > > > org.apache.camel.impl.engine.DefaultClassResolver.resolveClass(Defau > > > lt > > > ClassResolver.java:55) > > > ~[camel-base-3.0.0.jar:3.0.0] > > > at > > > org.apache.camel.impl.engine.DefaultFactoryFinder.doNewInstance(Defa > > > ul > > > tFactoryFinder.java:120) > > > ~[camel-base-3.0.0.jar:3.0.0] > > > at > > > org.apache.camel.impl.engine.DefaultFactoryFinder.lambda$findClass$0 > > > (D > > > efaultFactoryFinder.java:77) > > > ~[camel-base-3.0.0.jar:3.0.0] > > > at > > > org.apache.camel.impl.engine.DefaultFactoryFinder$1.apply(DefaultFac > > > to > > > ryFinder.java:155) > > > ~[camel-base-3.0.0.jar:3.0.0] > > > at > > > org.apache.camel.impl.engine.DefaultFactoryFinder$1.apply(DefaultFac > > > to > > > ryFinder.java:151) > > > ~[camel-base-3.0.0.jar:3.0.0] > > > at > > > java.base/java.util.concurrent.ConcurrentHashMap.computeIfAbsent(Con > > > cu > > > rrentHashMap.java:1705) > > > ~[na:na] > > > at > > > org.apache.camel.impl.engine.DefaultFactoryFinder.addToClassMap(Defa > > > ul > > > tFactoryFinder.java:151) > > > ~[camel-base-3.0.0.jar:3.0.0] > > > at > > > org.apache.camel.impl.engine.DefaultFactoryFinder.findClass(DefaultF > > > ac > > > toryFinder.java:74) > > > ~[camel-base-3.0.0.jar:3.0.0] > > > at > > > org.apache.camel.impl.engine.DefaultFactoryFinder.findClass(DefaultF > > > ac > > > toryFinder.java:66) > > > ~[camel-base-3.0.0.jar:3.0.0] > > > at > > > org.apache.camel.impl.engine.DefaultComponentResolver.findComponent( > > > De > > > faultComponentResol
Re: DefaultComponent
They are supporting 2.24.0 https://github.com/flowable/flowable-engine/blob/master/pom.xml#L25 Il giorno mar 3 dic 2019 alle ore 13:43 Claus Ibsen ha scritto: > Hi > > Oh didnt know so much about flowable-camel as its 3rd party and not ASF. > Same thing, its likely not Camel 3 compatible, so they need to do a > new release that supports Camel 3. > > > > On Tue, Dec 3, 2019 at 1:36 PM wrote: > > > > Its not my components. > > Its spring boot or flowable. But I cannot see in dependeny tree where > flowble-camel > > uses camel-core or camel-support. > > > > When I patch the classes DefaultComponent /-Consumer etc. it works. > > > > > > -Ursprüngliche Nachricht- > > Von: Claus Ibsen > > Gesendet: Dienstag, 3. Dezember 2019 13:29 > > An: users@camel.apache.org > > Betreff: Re: DefaultComponent > > > > Hi > > > > If you have custom components you need to source code migrate them to > Camel 3 and rebuild them. Camel 3 does not run with Camel 2 components. > > > > On Tue, Dec 3, 2019 at 1:21 PM wrote: > > > > > > Yes. I know and my own components use this. But it seems spring or > flowable needs this class there. > > > > > > > > > -Ursprüngliche Nachricht- > > > Von: Andrea Cosentino > > > Gesendet: Dienstag, 3. Dezember 2019 13:01 > > > An: users@camel.apache.org > > > Cc: dev > > > Betreff: Re: DefaultComponent > > > > > > In Camel 3 the DefaultComponent is located at > > > > > > org.apache.camel.support > > > > > > It is reported in the migration guide > > > > > > https://camel.apache.org/manual/latest/camel-3-migration-guide.html#_m > > > igrating_custom_components > > > > > > Il giorno mar 3 dic 2019 alle ore 12:59 ha > > > scritto: > > > > > > > Hi, > > > > > > > > I got this error. What is missing? > > > > > > > > java.lang.NoClassDefFoundError: > > > > org/apache/camel/impl/DefaultComponent > > > > > > > > Stacktrace: > > > > > > > > java.lang.NoClassDefFoundError: > org/apache/camel/impl/DefaultComponent > > > > at java.base/java.lang.ClassLoader.defineClass1(Native > > > > Method) ~[na:na] > > > > at > > > > java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1016) > ~[na:na] > > > > at > > > > java.base/java.security.SecureClassLoader.defineClass(SecureClassLoa > > > > de > > > > r.java:174) > > > > ~[na:na] > > > > at > > > > java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(Builtin > > > > Cl > > > > assLoader.java:802) > > > > ~[na:na] > > > > at > > > > java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPat > > > > hO > > > > rNull(BuiltinClassLoader.java:700) > > > > ~[na:na] > > > > at > > > > java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(Bui > > > > lt > > > > inClassLoader.java:623) > > > > ~[na:na] > > > > at > > > > java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinCl > > > > as > > > > sLoader.java:581) > > > > ~[na:na] > > > > at > > > > java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass( > > > > Cl > > > > assLoaders.java:178) > > > > ~[na:na] > > > > at > > > > java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) > > > > ~[na:na] > > > > at > > > > org.apache.camel.util.ObjectHelper.doLoadClass(ObjectHelper.java:474 > > > > ) > > > > ~[camel-util-3.0.0.jar:3.0.0] > > > > at > > > > org.apache.camel.util.ObjectHelper.loadClass(ObjectHelper.java:378) > > > > ~[camel-util-3.0.0.jar:3.0.0] > > > > at > > > > org.apache.camel.util.ObjectHelper.loadClass(ObjectHelper.java:355) > > > > ~[camel-util-3.0.0.jar:3.0.0] > > > > at > > > > org.apache.camel.impl.engine.DefaultClassResolver.loadClass(DefaultC > > > > la > > > > ssResolver.java:140) > > > > ~[camel-base-3.0.0.jar:3.0.0] > > > > at > > > > org.apache.camel.impl.engine.DefaultClassResolver.resolveClass(Defau > > > > lt > > > > ClassResolver.java:55) > > > > ~[camel-base-3.0.0.jar:3.0.0] > > > > at > > > > org.apache.camel.impl.engine.DefaultFactoryFinder.doNewInstance(Defa > > > > ul > > > > tFactoryFinder.java:120) > > > > ~[camel-base-3.0.0.jar:3.0.0] > > > > at > > > > org.apache.camel.impl.engine.DefaultFactoryFinder.lambda$findClass$0 > > > > (D > > > > efaultFactoryFinder.java:77) > > > > ~[camel-base-3.0.0.jar:3.0.0] > > > > at > > > > org.apache.camel.impl.engine.DefaultFactoryFinder$1.apply(DefaultFac > > > > to > > > > ryFinder.java:155) > > > > ~[camel-base-3.0.0.jar:3.0.0] > > > > at > > > > org.apache.camel.impl.engine.DefaultFactoryFinder$1.apply(DefaultFac > > > > to > > > > ryFinder.java:151) > > > > ~[camel-base-3.0.0.jar:3.0.0] > > > > at > > > > java.base/java.util.concurrent.ConcurrentHashMap.computeIfAbsent(Con > > > > cu > > > > rrentHashMap.java:1705) > > > > ~[na:na] > > > > at > > > > org.apache.camel.impl.engine.DefaultFactoryFinder.addToClassMap(Defa > > > > ul > > > > tFactoryFinder.java:151) > > > > ~[camel-base-3.0.0.jar:3.0.0] > > >
AW: DefaultComponent
I have it. Its flowable that uses 2-style DefaultComponent etc. -Ursprüngliche Nachricht- Von: Claus Ibsen Gesendet: Dienstag, 3. Dezember 2019 13:44 An: users@camel.apache.org Betreff: Re: DefaultComponent Hi Oh didnt know so much about flowable-camel as its 3rd party and not ASF. Same thing, its likely not Camel 3 compatible, so they need to do a new release that supports Camel 3. On Tue, Dec 3, 2019 at 1:36 PM wrote: > > Its not my components. > Its spring boot or flowable. But I cannot see in dependeny tree where > flowble-camel uses camel-core or camel-support. > > When I patch the classes DefaultComponent /-Consumer etc. it works. > > > -Ursprüngliche Nachricht- > Von: Claus Ibsen > Gesendet: Dienstag, 3. Dezember 2019 13:29 > An: users@camel.apache.org > Betreff: Re: DefaultComponent > > Hi > > If you have custom components you need to source code migrate them to Camel 3 > and rebuild them. Camel 3 does not run with Camel 2 components. > > On Tue, Dec 3, 2019 at 1:21 PM wrote: > > > > Yes. I know and my own components use this. But it seems spring or flowable > > needs this class there. > > > > > > -Ursprüngliche Nachricht- > > Von: Andrea Cosentino > > Gesendet: Dienstag, 3. Dezember 2019 13:01 > > An: users@camel.apache.org > > Cc: dev > > Betreff: Re: DefaultComponent > > > > In Camel 3 the DefaultComponent is located at > > > > org.apache.camel.support > > > > It is reported in the migration guide > > > > https://camel.apache.org/manual/latest/camel-3-migration-guide.html# > > _m > > igrating_custom_components > > > > Il giorno mar 3 dic 2019 alle ore 12:59 > > ha > > scritto: > > > > > Hi, > > > > > > I got this error. What is missing? > > > > > > java.lang.NoClassDefFoundError: > > > org/apache/camel/impl/DefaultComponent > > > > > > Stacktrace: > > > > > > java.lang.NoClassDefFoundError: org/apache/camel/impl/DefaultComponent > > > at java.base/java.lang.ClassLoader.defineClass1(Native > > > Method) ~[na:na] > > > at > > > java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1016) > > > ~[na:na] > > > at > > > java.base/java.security.SecureClassLoader.defineClass(SecureClassL > > > oa > > > de > > > r.java:174) > > > ~[na:na] > > > at > > > java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(Built > > > in > > > Cl > > > assLoader.java:802) > > > ~[na:na] > > > at > > > java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassP > > > at > > > hO > > > rNull(BuiltinClassLoader.java:700) > > > ~[na:na] > > > at > > > java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(B > > > ui > > > lt > > > inClassLoader.java:623) > > > ~[na:na] > > > at > > > java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(Builtin > > > Cl > > > as > > > sLoader.java:581) > > > ~[na:na] > > > at > > > java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClas > > > s( > > > Cl > > > assLoaders.java:178) > > > ~[na:na] > > > at > > > java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) > > > ~[na:na] > > > at > > > org.apache.camel.util.ObjectHelper.doLoadClass(ObjectHelper.java:4 > > > 74 > > > ) > > > ~[camel-util-3.0.0.jar:3.0.0] > > > at > > > org.apache.camel.util.ObjectHelper.loadClass(ObjectHelper.java:378 > > > ) > > > ~[camel-util-3.0.0.jar:3.0.0] > > > at > > > org.apache.camel.util.ObjectHelper.loadClass(ObjectHelper.java:355 > > > ) > > > ~[camel-util-3.0.0.jar:3.0.0] > > > at > > > org.apache.camel.impl.engine.DefaultClassResolver.loadClass(Defaul > > > tC > > > la > > > ssResolver.java:140) > > > ~[camel-base-3.0.0.jar:3.0.0] > > > at > > > org.apache.camel.impl.engine.DefaultClassResolver.resolveClass(Def > > > au > > > lt > > > ClassResolver.java:55) > > > ~[camel-base-3.0.0.jar:3.0.0] > > > at > > > org.apache.camel.impl.engine.DefaultFactoryFinder.doNewInstance(De > > > fa > > > ul > > > tFactoryFinder.java:120) > > > ~[camel-base-3.0.0.jar:3.0.0] > > > at > > > org.apache.camel.impl.engine.DefaultFactoryFinder.lambda$findClass > > > $0 > > > (D > > > efaultFactoryFinder.java:77) > > > ~[camel-base-3.0.0.jar:3.0.0] > > > at > > > org.apache.camel.impl.engine.DefaultFactoryFinder$1.apply(DefaultF > > > ac > > > to > > > ryFinder.java:155) > > > ~[camel-base-3.0.0.jar:3.0.0] > > > at > > > org.apache.camel.impl.engine.DefaultFactoryFinder$1.apply(DefaultF > > > ac > > > to > > > ryFinder.java:151) > > > ~[camel-base-3.0.0.jar:3.0.0] > > > at > > > java.base/java.util.concurrent.ConcurrentHashMap.computeIfAbsent(C > > > on > > > cu > > > rrentHashMap.java:1705) > > > ~[na:na] > > > at > > > org.apache.camel.impl.engine.DefaultFactoryFinder.addToClassMap(De > > > fa > > > ul > > > tFactoryFinder.java:151) > > > ~[camel-base-3.0.0.jar:3.0.0] > > > at > > > org.apache.camel.impl.engine.DefaultFactoryFinder.findClass(Defaul > > > tF > > >
Re: file component to access doneFileName option
Thanks, Claus. I agree with you and I implement the GenericFileFilter as
below
public class FileTransferFilter implements GenericFileFilter {
@Override
public boolean accept(GenericFile pathname) {
// we don't accept any files starting with skip in the name
return !pathname.getFileName().startsWith("skip");
}
}
but for my case, skip is not hard coded value, it is dynamic variable from
ready file name, how could I pass this variable to this filter?
On Mon, Dec 2, 2019 at 11:20 PM Claus Ibsen wrote:
> 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
>
--
~
Weiquan Yuan
Located in Ottawa, Canada
Tracing camel-zipkin-starter with Rabbitmq
Hi
I have implemented different microservice where internal communication is
taking place by camel and rabbitMQ with different exchange and queue.
Ex: Service1 Publish message to RabbitMQ ( i.e Exchange 1 -> Queue 1) where
Service2 Consume message
Service2 Publish message to RabbitMQ ( i.e Exchange 2 -> Queue 2) where
Service3 Consume message
Service3 Publish message to RabbitMQ ( i.e Exchange 3 -> Queue 3) where
Service4 Consume message and so on.
I am using camel-zipkin for tracing, and log4j2 for logging.
I am using Springboot : 1.5.12.RELEASE and 2.21.5 version of following
dependencies of camel :
camel-spring-boot-starter
camel-rabbitmq-starter
camel-core
camel-spring
camel-zipkin-starter
camel-test
camel-test-spring
I need suggestion for my two problems
1. span-id, trace-id are not getting printed in logs. I have necessary
placeholders added in my log4j2.xml.
2. Whenever a message is sent to an exchange a unique span-id and trace-id
is getting generated.
My Questions are :
1. Is it possible to have a unique traceID for entire data traverse from
Service 1 to Service N.
2. How can I print span-id, trace-id to logs.
Attached is log4j2.xml, pom.xml and application.yaml for reference.
Do let me know in case more information is required
Regards
Prabhat Kumar
%d{-MM-dd'T'HH:mm:ss.SXXX}|2|%level|example-service|%X{X-B3-TraceId},%X{X-B3-SpanId},%X{X-Span-Export}|${sys:PID}|%thread|%logger{1.}|%message%n
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
org.springframework.boot
spring-boot-starter-parent
1.5.12.RELEASE
com.camel
example
0.0.1-SNAPSHOT
example
Demo project for Spring Boot
1.8
2.21.5
org.springframework.boot
spring-boot-starter-web
org.springframework.boot
spring-boot-starter-logging
org.springframework.boot
spring-boot-starter-log4j2
org.springframework.boot
spring-boot-starter-amqp
org.apache.camel
camel-spring-boot-starter
${camel.version}
org.apache.camel
camel-rabbitmq-starter
${camel.version}
org.apache.camel
camel-core
${camel.version}
org.apache.camel
camel-spring
${camel.version}
org.apache.camel
camel-zipkin-starter
${camel.version}
org.projectlombok
lombok
org.apache.camel
camel-test
${camel.version}
test
org.apache.camel
camel-test-spring
${camel.version}
test
org.springframework.boot
spring-boot-starter-test
test
org.springframework.boot
spring-boot-maven-plugin
Re: file component to access doneFileName option
Hi
You can use java api, to look for the done file name.
You know the target file name.
Then do a file list and check if there is a done file name for it.
On Tue, Dec 3, 2019 at 3:52 PM WEIQUAN YUAN wrote:
>
> Thanks, Claus. I agree with you and I implement the GenericFileFilter as
> below
>
> public class FileTransferFilter implements GenericFileFilter {
>
> @Override
> public boolean accept(GenericFile pathname) {
> // we don't accept any files starting with skip in the name
> return !pathname.getFileName().startsWith("skip");
> }
> }
>
> but for my case, skip is not hard coded value, it is dynamic variable from
> ready file name, how could I pass this variable to this filter?
>
> On Mon, Dec 2, 2019 at 11:20 PM Claus Ibsen wrote:
>
> > 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
> >
>
>
> --
> ~
> Weiquan Yuan
> Located in Ottawa, Canada
--
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
