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
>
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
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
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.
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
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
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.
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.
>
>
>
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.
>
>
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
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:
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
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
13 matches
Mail list logo