Graceful shutdown of message aggregation

[Branko Husarik, Wood & Co.]

Hello,

I have a question about the graceful shutdown of the message aggregation. I am 
aggregating up to 10 messages that should be saved to the database and logged 
to the console. When I shut down the application, remaining aggregated data are 
lost.

.aggregate(constant(true), batchInsertAggregationStrategy)
.completionPredicate(simple("${exchangeProperty.CamelAggregatedSize} >= 
10"))
.completionTimeout(6)
.completeAllOnStop()
.to(dbSaverSqlInsertProcessor.buildSqlBatchInsertEndpoint())
.process(savedIdsLoggingProcessor);

After shutdown the following message is countdowning:

INFO  [org.apache.camel.impl.engine.DefaultShutdownStrategy] (Camel (camel-1) 
thread #23 - ShutdownTask) Waiting as there are still 4 inflight and pending 
exchanges to complete, timeout in 45 seconds. Inflights per route: [route1 = 4]
INFO  [org.apache.camel.impl.engine.DefaultShutdownStrategy] (Camel (camel-1) 
thread #23 - ShutdownTask) Waiting as there are still 4 inflight and pending 
exchanges to complete, timeout in 44 seconds. Inflights per route: [route1 = 4]
...
WARN  [org.apache.camel.impl.engine.DefaultShutdownStrategy] 
(SpringApplicationShutdownHook) Timeout occurred during graceful shutdown. 
Forcing the routes to be shutdown now. Notice: some resources may still be 
running as graceful shutdown did not complete successfully.
WARN  [org.apache.camel.impl.engine.DefaultShutdownStrategy] (Camel (camel-1) 
thread #23 - ShutdownTask) Interrupted while waiting during graceful shutdown, 
will force shutdown now.

Please Can you give me tip what I am doing wrong way? Thank you

Best Regards

Branko Husarik


[cid:image001.png@01DAE3FC.1DF76FF0]
Braňko Husárik
Calypso Developer
IT Development
email: branko.husa...@wood.cz
m: +420 606 022 474

WOOD & Company
Palladium, nám. Republiky 1079/1a
110 00 Prague 1, Czech Republic
wood.com








DISCLAIMER
WOOD & Company Financial Services, a.s. and its branches are authorized and 
regulated by the CNB as Home State regulator and in Poland by the KNF, in 
Slovakia by the NBS, in Italy by the CONSOB and in the UK by the FCA as Host 
State regulators. For further information about WOOD & Co., its investment 
services, financial instruments and associated risks, safeguard client assets 
(incl. compensation schemes) and contractual relationship please see our 
website at www.wood.com under section Corporate 
Governance. Unless otherwise stated, this transmission is neither an offer nor 
the solicitation of an offer to sell or purchase any investment. All estimates, 
opinions and other information contained herein are subject to change without 
notice and are provided in good faith but without legal responsibility or 
liability. Opinion may be personal to the author and may not reflect the 
opinions of WOOD & Co. Communications from sales persons, sales traders or 
traders should not be regarded as investment research and may contain opinions 
or trading ideas which are different from WOOD & Co. investment research 
opinions. This e-mail and any attachments are confidential and may be 
privileged or otherwise protected from disclosure. If you are not a named 
addressee you must not use, disclose, distribute, copy, print or rely on this 
e-mail and any of its attachments. Please notify the sender that you have 
received this email by mistake by replying to the email, and then delete the 
email and any copies of it. Although WOOD & Co. routinely screens e-mails for 
viruses, addressees should scan this e-mail and any attachments for viruses. 
WOOD & Co. makes no representation or warranty as to the absence of viruses in 
this e-mail or any attachments. Please note that to ensure regulatory 
compliance and for the protection of our clients and business, we may monitor 
and read e-mails sent to and from our server(s).

Re: [VOTE] Release Apache Camel K 2.4.0

[Andrea Cosentino]

+1 (binding)

Thanks Pasquale

Il giorno mer 31 lug 2024 alle ore 05:52 Otavio Rodolfo Piske <
angusyo...@gmail.com> ha scritto:

> +1 (binding)
>
> Thanks Pasquale
>
> On Tue, Jul 30, 2024 at 10:04 AM Zineb Bendhiba 
> wrote:
>
> > +1 (binding)
> >
> > Le lun. 29 juil. 2024 à 16:36, Pasquale Congiusti <
> > pasquale.congiu...@gmail.com> a écrit :
> >
> > > Hello,
> > >
> > > This is a vote to release Apache Camel K 2.4.0. This release contains
> > > several new features and bug fixes [1].
> > >
> > > Camel K release files:
> > > https://dist.apache.org/repos/dist/dev/camel/camel-k/2.4.0/
> > >
> > > Camel K Tag:
> > > https://github.com/apache/camel-k/releases/tag/v2.4.0
> > >
> > > Camel K CRD Java dependency staging repository:
> > > https://repository.apache.org/content/repositories/orgapachecamel-1738
> > >
> > > Staging container image repository (multi architecture manifest):
> > >
> > >
> >
> https://hub.docker.com/layers/camelk/camel-k/2.4.0/images/sha256-307b048a8c9913c167d19521ebd2c889cb98fe135c4bc2964ac8ec8f95c242b1?context=explore
> > >
> > > It's possible to install all staging artifacts with a single command
> > > (preferably using the kamel CLI you find in Camel K release files):
> > >
> > > $ kamel install --operator-image=camelk/camel-k:2.4.0 --olm=false
> > >
> > > Please test this release candidate and cast your vote.
> > >
> > > [ ] +1 Release Apache Camel K 2.4.0
> > > [ ] -1 Veto the release (provide specific comments)
> > >
> > > The vote is open for at least 72 hours.
> > >
> > > I start the vote with my +1 (binding).
> > >
> > > Thanks and regards,
> > > Pasquale Congiusti
> > >
> > > [1] https://github.com/apache/camel-k/milestone/49?closed=1
> > >
> >
> >
> > --
> > Zineb Bendhiba
> >
>
>
> --
> Otavio R. Piske
> http://orpiske.net
>

Re: [VOTE] Release Apache Camel K 2.4.0

[Otavio Rodolfo Piske]

+1 (binding)

Thanks Pasquale

On Tue, Jul 30, 2024 at 10:04 AM Zineb Bendhiba 
wrote:

> +1 (binding)
>
> Le lun. 29 juil. 2024 à 16:36, Pasquale Congiusti <
> pasquale.congiu...@gmail.com> a écrit :
>
> > Hello,
> >
> > This is a vote to release Apache Camel K 2.4.0. This release contains
> > several new features and bug fixes [1].
> >
> > Camel K release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-k/2.4.0/
> >
> > Camel K Tag:
> > https://github.com/apache/camel-k/releases/tag/v2.4.0
> >
> > Camel K CRD Java dependency staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1738
> >
> > Staging container image repository (multi architecture manifest):
> >
> >
> https://hub.docker.com/layers/camelk/camel-k/2.4.0/images/sha256-307b048a8c9913c167d19521ebd2c889cb98fe135c4bc2964ac8ec8f95c242b1?context=explore
> >
> > It's possible to install all staging artifacts with a single command
> > (preferably using the kamel CLI you find in Camel K release files):
> >
> > $ kamel install --operator-image=camelk/camel-k:2.4.0 --olm=false
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release Apache Camel K 2.4.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > I start the vote with my +1 (binding).
> >
> > Thanks and regards,
> > Pasquale Congiusti
> >
> > [1] https://github.com/apache/camel-k/milestone/49?closed=1
> >
>
>
> --
> Zineb Bendhiba
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release Apache Camel K 2.4.0

[Zineb Bendhiba]

+1 (binding)

Le lun. 29 juil. 2024 à 16:36, Pasquale Congiusti <
pasquale.congiu...@gmail.com> a écrit :

> Hello,
>
> This is a vote to release Apache Camel K 2.4.0. This release contains
> several new features and bug fixes [1].
>
> Camel K release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k/2.4.0/
>
> Camel K Tag:
> https://github.com/apache/camel-k/releases/tag/v2.4.0
>
> Camel K CRD Java dependency staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1738
>
> Staging container image repository (multi architecture manifest):
>
> https://hub.docker.com/layers/camelk/camel-k/2.4.0/images/sha256-307b048a8c9913c167d19521ebd2c889cb98fe135c4bc2964ac8ec8f95c242b1?context=explore
>
> It's possible to install all staging artifacts with a single command
> (preferably using the kamel CLI you find in Camel K release files):
>
> $ kamel install --operator-image=camelk/camel-k:2.4.0 --olm=false
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release Apache Camel K 2.4.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> I start the vote with my +1 (binding).
>
> Thanks and regards,
> Pasquale Congiusti
>
> [1] https://github.com/apache/camel-k/milestone/49?closed=1
>


-- 
Zineb Bendhiba

Re: Kubernetes-events consumer debugging help

[Pasquale Congiusti]

Looking at the following trace:

{"timestamp":"2024-07-29
16:33:24.735","level":"DEBUG","thread":"main","logger":"org.apache.camel.component.kubernetes.KubernetesHelper","message":"Create
Kubernetes client with the following Configuration: KubernetesConfiguration
[masterUrl=client=my-namespace, category=null,
kubernetesClient=null, username=null, password=null, operation=null,
apiVersion=null, caCertData=null, caCertFile=null, clientCertData=null,
clientCertFile=null, clientKeyAlgo=null, clientKeyData=null,
clientKeyFile=null, clientKeyPassphrase=null, oauthToken=null,
trustCerts=null, namespace=null, labelKey=null, labelValue=null,
resourceName=null, portName=null, dnsDomain=null, poolSize=1,
connectionTimeout=null]","context":"default"}

It seems you're missing to configure the credentials to let your
application authenticate against the cluster. Check the examples on the
component page [1] in order to get more reference about how to properly
configure it.

Cheers,
Pasquale.

[1]
https://camel.apache.org/components/4.4.x/kubernetes-events-component.html#_kubernetes_events_consumer_example

On Mon, Jul 29, 2024 at 7:59 PM Neuman, Benjamin J
 wrote:

> Hi all. I am attempting to implement a route which will receive k8 events
> and simply write them to system:out.
> The application is running in our cluster, however, it is not receiving
> any events. I'm hoping to get some info on how I might debug this issue.
> For reference, here is the route:
> from("kubernetes-events:client=my-namespace")
> .setHeader(KubernetesConstants.KUBERNETES_NAMESPACE_NAME,
> constant("my-namespace"))
> .process(new KubernertesProcessor())
> .to("stream:out");
> }
>
> public static class KubernertesProcessor implements Processor {
> @Override
> public void process(Exchange exchange) throws Exception {
> Message in = exchange.getIn();
> Event event = exchange.getIn().getBody(Event.class);
> log.info("Got event with event name: {} and action {}",
> event.getMetadata().getName(),
>
> in.getHeader(KubernetesConstants.KUBERNETES_EVENT_ACTION));
> }
> }
> and some logs that may be of use:
> {"timestamp":"2024-07-29
> 16:33:24.734","level":"DEBUG","thread":"main","logger":"org.apache.camel.impl.engine.InternalRouteStartupManager","message":"Warming
> up route id: route1 having autoStartup=true","context":"default"}
> {"timestamp":"2024-07-29
> 16:33:24.735","level":"DEBUG","thread":"main","logger":"org.apache.camel.component.kubernetes.KubernetesHelper","message":"Create
> Kubernetes client with the following Configuration: KubernetesConfiguration
> [masterUrl=client=my-namespace, category=null,
> kubernetesClient=null, username=null, password=null, operation=null,
> apiVersion=null, caCertData=null, caCertFile=null, clientCertData=null,
> clientCertFile=null, clientKeyAlgo=null, clientKeyData=null,
> clientKeyFile=null, clientKeyPassphrase=null, oauthToken=null,
> trustCerts=null, namespace=null, labelKey=null, labelValue=null,
> resourceName=null, portName=null, dnsDomain=null, poolSize=1,
> connectionTimeout=null]","context":"default"}
> {"timestamp":"2024-07-29
> 16:33:25.337","level":"DEBUG","thread":"main","logger":"org.apache.camel.impl.engine.InternalRouteStartupManager","message":"Route:
> route1 >>> Route[kubernetes-events://client=my-namespace ->
> null]","context":"default"}
> {"timestamp":"2024-07-29
> 16:33:25.337","level":"DEBUG","thread":"main","logger":"org.apache.camel.impl.engine.InternalRouteStartupManager","message":"Starting
> consumer (order: 1000) on route: route1","context":"default"}
> {"timestamp":"2024-07-29
> 16:33:25.338","level":"DEBUG","thread":"main","logger":"org.apache.camel.support.DefaultConsumer","message":"Build
> consumer:
> Consumer[kubernetes-events://client=my-namespace]","context":"default"}
> {"timestamp":"2024-07-29
> 16:33:25.338","level":"DEBUG","thread":"main","logger":"org.apache.camel.support.DefaultConsumer","message":"Init
> consumer:
> Consumer[kubernetes-events://client=my-namespace]","context":"default"}
> {"timestamp":"2024-07-29
> 16:33:25.339","level":"DEBUG","thread":"main","logger":"org.apache.camel.support.DefaultConsumer","message":"Starting
> consumer:
> Consumer[kubernetes-events://client=my-namespace]","context":"default"}
> {"timestamp":"2024-07-29
> 16:33:25.339","level":"DEBUG","thread":"main","logger":"org.apache.camel.impl.engine.BaseExecutorServiceManager","message":"Created
> new ThreadPool for source:
> kubernetes-events://client=my-namespace with name:
> KubernetesConsumer. ->
> org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@46b7c89b
> [Running org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@46b7c89b[Running>,
> pool size = 0, active threads = 0, queued tasks = 0, completed tasks =
> 0][KubernetesConsumer]","context":"default"}
> {"timestamp":"2024-07-29
> 

Enabling Virtual Threads Support...

[James Carman]

It looks like the only way to enable virtual threads support is via a
System property. How tough would it be, at least within spring boot,
to enable this feature via other means (like application.properties
similar to how Spring Boot itself enables virtual threads)? I can take
a stab at submitting a PR for it.

Thanks,

James

Kubernetes-events consumer debugging help

[Neuman, Benjamin J]

Hi all. I am attempting to implement a route which will receive k8 events and 
simply write them to system:out.
The application is running in our cluster, however, it is not receiving any 
events. I'm hoping to get some info on how I might debug this issue.
For reference, here is the route:
from("kubernetes-events:client=my-namespace")
.setHeader(KubernetesConstants.KUBERNETES_NAMESPACE_NAME, 
constant("my-namespace"))
.process(new KubernertesProcessor())
.to("stream:out");
}

public static class KubernertesProcessor implements Processor {
@Override
public void process(Exchange exchange) throws Exception {
Message in = exchange.getIn();
Event event = exchange.getIn().getBody(Event.class);
log.info("Got event with event name: {} and action {}", 
event.getMetadata().getName(),
in.getHeader(KubernetesConstants.KUBERNETES_EVENT_ACTION));
}
}
and some logs that may be of use:
{"timestamp":"2024-07-29 
16:33:24.734","level":"DEBUG","thread":"main","logger":"org.apache.camel.impl.engine.InternalRouteStartupManager","message":"Warming
 up route id: route1 having autoStartup=true","context":"default"}
{"timestamp":"2024-07-29 
16:33:24.735","level":"DEBUG","thread":"main","logger":"org.apache.camel.component.kubernetes.KubernetesHelper","message":"Create
 Kubernetes client with the following Configuration: KubernetesConfiguration 
[masterUrl=client=my-namespace, category=null, kubernetesClient=null, 
username=null, password=null, operation=null, apiVersion=null, caCertData=null, 
caCertFile=null, clientCertData=null, clientCertFile=null, clientKeyAlgo=null, 
clientKeyData=null, clientKeyFile=null, clientKeyPassphrase=null, 
oauthToken=null, trustCerts=null, namespace=null, labelKey=null, 
labelValue=null, resourceName=null, portName=null, dnsDomain=null, poolSize=1, 
connectionTimeout=null]","context":"default"}
{"timestamp":"2024-07-29 
16:33:25.337","level":"DEBUG","thread":"main","logger":"org.apache.camel.impl.engine.InternalRouteStartupManager","message":"Route:
 route1 >>> Route[kubernetes-events://client=my-namespace -> 
null]","context":"default"}
{"timestamp":"2024-07-29 
16:33:25.337","level":"DEBUG","thread":"main","logger":"org.apache.camel.impl.engine.InternalRouteStartupManager","message":"Starting
 consumer (order: 1000) on route: route1","context":"default"}
{"timestamp":"2024-07-29 
16:33:25.338","level":"DEBUG","thread":"main","logger":"org.apache.camel.support.DefaultConsumer","message":"Build
 consumer: 
Consumer[kubernetes-events://client=my-namespace]","context":"default"}
{"timestamp":"2024-07-29 
16:33:25.338","level":"DEBUG","thread":"main","logger":"org.apache.camel.support.DefaultConsumer","message":"Init
 consumer: 
Consumer[kubernetes-events://client=my-namespace]","context":"default"}
{"timestamp":"2024-07-29 
16:33:25.339","level":"DEBUG","thread":"main","logger":"org.apache.camel.support.DefaultConsumer","message":"Starting
 consumer: 
Consumer[kubernetes-events://client=my-namespace]","context":"default"}
{"timestamp":"2024-07-29 
16:33:25.339","level":"DEBUG","thread":"main","logger":"org.apache.camel.impl.engine.BaseExecutorServiceManager","message":"Created
 new ThreadPool for source: kubernetes-events://client=my-namespace 
with name: KubernetesConsumer. -> 
org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@46b7c89b[Running,
 pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 
0][KubernetesConsumer]","context":"default"}
{"timestamp":"2024-07-29 
16:33:25.343","level":"DEBUG","thread":"main","logger":"org.apache.camel.impl.engine.InternalRouteStartupManager","message":"Route:
 route1 started and consuming from: 
kubernetes-events://client=my-namespace","context":"default"}
Any help/guidance is greatly appreciated.

This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or intended recipient’s authorized agent, the reader is hereby
notified that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.

Re: [VOTE] Release Apache Camel K 2.4.0

[Claudio Miranda]

+1 (non binding)

Em seg., 29 de jul. de 2024 às 15:36, Pasquale Congiusti
 escreveu:
>
> Hello,
>
> This is a vote to release Apache Camel K 2.4.0. This release contains
> several new features and bug fixes [1].
>
> Camel K release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k/2.4.0/
>
> Camel K Tag:
> https://github.com/apache/camel-k/releases/tag/v2.4.0
>
> Camel K CRD Java dependency staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1738
>
> Staging container image repository (multi architecture manifest):
> https://hub.docker.com/layers/camelk/camel-k/2.4.0/images/sha256-307b048a8c9913c167d19521ebd2c889cb98fe135c4bc2964ac8ec8f95c242b1?context=explore
>
> It's possible to install all staging artifacts with a single command
> (preferably using the kamel CLI you find in Camel K release files):
>
> $ kamel install --operator-image=camelk/camel-k:2.4.0 --olm=false
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release Apache Camel K 2.4.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> I start the vote with my +1 (binding).
>
> Thanks and regards,
> Pasquale Congiusti
>
> [1] https://github.com/apache/camel-k/milestone/49?closed=1



-- 
  Claudio Miranda

clau...@claudius.com.br
http://www.claudius.com.br

[VOTE] Release Apache Camel K 2.4.0

[Pasquale Congiusti]

Hello,

This is a vote to release Apache Camel K 2.4.0. This release contains
several new features and bug fixes [1].

Camel K release files:
https://dist.apache.org/repos/dist/dev/camel/camel-k/2.4.0/

Camel K Tag:
https://github.com/apache/camel-k/releases/tag/v2.4.0

Camel K CRD Java dependency staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1738

Staging container image repository (multi architecture manifest):
https://hub.docker.com/layers/camelk/camel-k/2.4.0/images/sha256-307b048a8c9913c167d19521ebd2c889cb98fe135c4bc2964ac8ec8f95c242b1?context=explore

It's possible to install all staging artifacts with a single command
(preferably using the kamel CLI you find in Camel K release files):

$ kamel install --operator-image=camelk/camel-k:2.4.0 --olm=false

Please test this release candidate and cast your vote.

[ ] +1 Release Apache Camel K 2.4.0
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

I start the vote with my +1 (binding).

Thanks and regards,
Pasquale Congiusti

[1] https://github.com/apache/camel-k/milestone/49?closed=1

[ANNOUNCEMENT] Apache Camel Karavan 4.7.0 Release

[Marat Gubaidullin]

Dear Apache Camel Community,

We are happy to announce the release of Apache Camel Karavan!

Improvements:

   1. Docker or Kubernetes templates and configuration now adapt to the
   installed environment.
   2. Dev Mode and Build Mode in Docker environment propagate environment
   variables configured in the project’s docker-compose.yaml.
   3. Dev Mode and Build Mode in Docker mount volumes as configured in the
   project’s docker-compose.yaml.
   4. Karavan supports placeholders in DSL and Kamelet properties.
   5. Improved file change status determination based on content rather
   than change date.
   6. Karavan displays diff for changed files, enhancing visibility and
   traceability.
   7. Topology can visualize consumer and producer groups, providing better
   insights into data flow.
   8. Karavan uses simple ConcurrentMaps instead of Hazelcast to cache
   project data, reducing startup time and memory consumption.
   9. Configuration files can be deployed as ConfigMaps through the UI in
   Kubernetes.
   10. Configuration files can be saved in a shared folder in Docker,
   facilitating easier access and management.

Latest versions:

   1. Camel 4.7.0
   2. Kamelets 4.7.0
   3. Jkube 1.16.2
   4. JBang v0.117.1
   5. Quarkus 3.12.3

Source release package:
https://dist.apache.org/repos/dist/release/camel/camel-karavan/4.7.0/

VS Code Extension
https://marketplace.visualstudio.com/items?itemName=camel-karavan.karavan

Container images
https://github.com/orgs/apache/packages?repo_name=camel-karavan

How-to
https://github.com/apache/camel-karavan/blob/main/docs/README.md

Have a great day and happy integrations!
Marat Gubaidullin

Virtual Threads Support...

[James Carman]

It looks like the only way to enable virtual threads support is via a
System property. How tough would it be, at least within spring boot,
to enable this feature via other means (like application.properties
similar to how Spring Boot itself enables virtual threads)?

Re: Customise Java DSL in Camel 4

[Claude Mamo]

Following up on this. I managed to stand up a route from within a kamelet
thanks to a custom route policy and a Camel context startup listener. Might
need to tweak/revise my approach because of some kamelet limitations but I
don't think they're blockers. Thanks for the help.

Claude

On Mon, Jul 22, 2024 at 9:14 AM Claude Mamo  wrote:

> Thanks Murat and Ivan for your input. Kamelets might do the trick for some
> scenarios we have in mind. I'm not sure if we can hide the complexity
> behind Kamelets for this scenario where we want to overlay from/to
> endpoints (e.g., http) with the ability to store and replay messages which
> is a common requirement when integrating health systems. As I see it, this
> is not just a matter of persisting the message but also transparently
> injecting an intermediate route to consume the message and replay it. From
> the little prototyping I've done till now, it doesn't seem I can have
> multiple routes in a Kamelet.
>
> On Sat, Jul 20, 2024 at 8:54 PM Marat Gubaidullin <
> marat.gubaidul...@gmail.com> wrote:
>
>> Hello Claude.
>>
>> To make it intuitive in Karavan you could make your custom Kamelets that
>> incapsulate components/dsl configuration complexity.
>>
>> On Sat, Jul 20, 2024, 12:28 Claude Mamo  wrote:
>>
>> > Yeah I had considered it but the functionality we want to provide would
>> be
>> > more intuitive if it's part of the DSL. On the minus side, providing a
>> > custom DSL would make it harder for us to integrate with designers like
>> > Apache Karavan so that's for sure something we need to factor in. I
>> should
>> > highlight that the fromHie(...) EIP example is actually meant to be a
>> > wrapper for any endpoint (direct, http, etc...). I could use
>> interceptors,
>> > however, I'm trying to make this more idiomatic.
>> >
>> > On Sat, Jul 20, 2024 at 1:55 PM Ivan Kulaga <
>> > kulagaivanandreev...@gmail.com>
>> > wrote:
>> >
>> > > Hello Claude!
>> > >
>> > > Please tell, have you considered writing custom components? Writing a
>> new
>> > > component is a somewhat common task, and there are many instruments
>> and
>> > > examples for that in camel (
>> > > https://camel.apache.org/manual/writing-components.html).
>> > > With custom components, your camel route may look like this:
>> > > from("hie:my-hie-server-address?my-hie-parameter=value")
>> > > .transform(...)
>> > > .to(mrs:my-mrs-server-address?action=open)
>> > > .transform(...)
>> > > .to("hie:my-hie-server-address")
>> > > Writing custom components does not require forking camel repo, you can
>> > just
>> > > add them as a dependency in your application and then add them to
>> camel
>> > > context at application configuration step.
>> > >
>> > > Best regards,
>> > >
>> > > Ivan
>> > >
>> > > On Sat, Jul 20, 2024 at 4:23 PM Claude Mamo 
>> > wrote:
>> > >
>> > > > Hello Camel community,
>> > > >
>> > > > Probably this has been asked before but couldn't find a good answer
>> in
>> > > the
>> > > > mailing lists nor Zulip. I'd like to tailor the Camel Java DSL for
>> > health
>> > > > information exchange. This means creating a no. of EIPs. For
>> example:
>> > > >
>> > > > fromHie(...).transform(...).openMRS(...).transform(...).toHie(...)
>> > > >
>> > > > So far, all I've come up with is a base class extending RouteBuilder
>> > but
>> > > > this approach doesn't really work for various reasons. I've came
>> across
>> > > > https://github.com/oehf/ipf/tree/master which I think it's
>> extending
>> > the
>> > > > Camel DSL by means of Groovy metaprogramming. Doesn't seem like a
>> bad
>> > > > approach though I'm looking for alternatives which don't include
>> > forking
>> > > > the Camel repo. Ideas? As a side note, I'd also like to extend the
>> YAML
>> > > DSL
>> > > > but my focus is on the Java one for now.
>> > > >
>> > > > Cheers,
>> > > >
>> > > > Claude
>> > > >
>> > >
>> >
>>
>

AW: Camel 4.6.0: Issue with AdviceWithRouteBuilder

[Klug Andreas (BD/SWD-BEB5)]

Hello,

Concerning the issue with the AdviceWith as mentioned in the attached mail: I 
somehow got confused with another issue, meaning, I guess my previous statement 
was wrong. The issue seems to be as follows:

The AdviceWith tasks seem to work fine in both cases, 4.4.0 and 4.7.0, when 
using these tasks from a lifecycle strategy, but when using these tasks from 
within a route template definition converter, then an exception occurs.

final var converter = new RouteAdvisoryStrategy(context,environment);
defaultContext.addRouteTemplateDefinitionConverter("*", converter);

I do have a repo case, which throws that exception (but still continues to run 
Camel) upon applying AdviceWith tasks, run with mvn spring-boot:run. The code 
works fine with Camel 4.4.0, but fails with 4.7.0. (in case of running the repo 
case with 4.4.0 – I had to comment out getExchangeStatusTags in 
MetricsNamingStrategy).

Due to company policies, I’m not allowed to send the code to the mailing list, 
thus I sent it already to Claus personally, but I’m not sure if Claus is 
currently available. In case anybody else might want to look at it, pls. let me 
know.

We would be very glad if you can support us here.

Thanks very much.

Mit freundlichen Grüßen / Best Regards

Andreas Klug

Robert Bosch GmbH | Postfach 10 60 50 | 70049 Stuttgart | GERMANY | 
www.bosch.com

Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HRB 14000;
Aufsichtsratsvorsitzender: Prof. Dr. Stefan Asenkerschbaumer; Geschäftsführung: 
Dr. Stefan Hartung, Dr. Christian Fischer, Dr. Markus Forschner, Stefan Grosch, 
Dr. Markus Heyn, Dr. Frank Meyer,
Dr. Tanja Rückert

Von: Claus Ibsen 
Datum: Freitag, 12. Juli 2024 um 11:27
An: users@camel.apache.org 
Betreff: Re: Camel 4.6.0: Issue with AdviceWithRouteBuilder
Hi

No but try with 4.7.0 when its released

On Fri, Jul 12, 2024 at 11:14 AM Klug Andreas (BD/SWD-BEB5)
 wrote:

> Hello everyone,
>
> After migrating from 4.4.0 to 4.6.0 we experience a strange issue with the
> AdviceWithRouteBuilder.
>
> We do have multiple AdviceWithTasks which are working in 4.4.0 and 4.6.0,
> e. g.
>
>   *   weaveByToUri("micrometer:.*").before()
>   *   weaveById("*").selectLast().before()
>
> However, using weaveAddFirst().before() or builder.weaveAddFirst().after()
> won’t work starting from 4.6.0.
> I double-checked that by weaving in pretty simple to identify statements
> like
> .log("")
> and finding these statements in the route dump.
> Even trying to mimic weaveAddFirst() by using
> weaveById(“*”).selectFirst().before() or
> weaveById(“*”).selectFirst().after() doesn’t seem to work.
>
> Do you have any suggestions?
>
> Best Regards,
> Andreas
>


--
Claus Ibsen
-
@davsclaus
Camel in Action 2: 
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.manning.com%2Fibsen2=05%7C02%7CAndreas.Klug2%40de.bosch.com%7C8edefc9229d94a8e58fd08dca254e71c%7C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7C638563732749221939%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=oXjSsK0Ga%2BKJpuDoI46fJKgWr55Oqvxbo7py%2B5xjiEg%3D=0

Re: Customise Java DSL in Camel 4

[Claude Mamo]

Thanks Murat and Ivan for your input. Kamelets might do the trick for some
scenarios we have in mind. I'm not sure if we can hide the complexity
behind Kamelets for this scenario where we want to overlay from/to
endpoints (e.g., http) with the ability to store and replay messages which
is a common requirement when integrating health systems. As I see it, this
is not just a matter of persisting the message but also transparently
injecting an intermediate route to consume the message and replay it. From
the little prototyping I've done till now, it doesn't seem I can have
multiple routes in a Kamelet.

On Sat, Jul 20, 2024 at 8:54 PM Marat Gubaidullin <
marat.gubaidul...@gmail.com> wrote:

> Hello Claude.
>
> To make it intuitive in Karavan you could make your custom Kamelets that
> incapsulate components/dsl configuration complexity.
>
> On Sat, Jul 20, 2024, 12:28 Claude Mamo  wrote:
>
> > Yeah I had considered it but the functionality we want to provide would
> be
> > more intuitive if it's part of the DSL. On the minus side, providing a
> > custom DSL would make it harder for us to integrate with designers like
> > Apache Karavan so that's for sure something we need to factor in. I
> should
> > highlight that the fromHie(...) EIP example is actually meant to be a
> > wrapper for any endpoint (direct, http, etc...). I could use
> interceptors,
> > however, I'm trying to make this more idiomatic.
> >
> > On Sat, Jul 20, 2024 at 1:55 PM Ivan Kulaga <
> > kulagaivanandreev...@gmail.com>
> > wrote:
> >
> > > Hello Claude!
> > >
> > > Please tell, have you considered writing custom components? Writing a
> new
> > > component is a somewhat common task, and there are many instruments and
> > > examples for that in camel (
> > > https://camel.apache.org/manual/writing-components.html).
> > > With custom components, your camel route may look like this:
> > > from("hie:my-hie-server-address?my-hie-parameter=value")
> > > .transform(...)
> > > .to(mrs:my-mrs-server-address?action=open)
> > > .transform(...)
> > > .to("hie:my-hie-server-address")
> > > Writing custom components does not require forking camel repo, you can
> > just
> > > add them as a dependency in your application and then add them to camel
> > > context at application configuration step.
> > >
> > > Best regards,
> > >
> > > Ivan
> > >
> > > On Sat, Jul 20, 2024 at 4:23 PM Claude Mamo 
> > wrote:
> > >
> > > > Hello Camel community,
> > > >
> > > > Probably this has been asked before but couldn't find a good answer
> in
> > > the
> > > > mailing lists nor Zulip. I'd like to tailor the Camel Java DSL for
> > health
> > > > information exchange. This means creating a no. of EIPs. For example:
> > > >
> > > > fromHie(...).transform(...).openMRS(...).transform(...).toHie(...)
> > > >
> > > > So far, all I've come up with is a base class extending RouteBuilder
> > but
> > > > this approach doesn't really work for various reasons. I've came
> across
> > > > https://github.com/oehf/ipf/tree/master which I think it's extending
> > the
> > > > Camel DSL by means of Groovy metaprogramming. Doesn't seem like a bad
> > > > approach though I'm looking for alternatives which don't include
> > forking
> > > > the Camel repo. Ideas? As a side note, I'd also like to extend the
> YAML
> > > DSL
> > > > but my focus is on the Java one for now.
> > > >
> > > > Cheers,
> > > >
> > > > Claude
> > > >
> > >
> >
>

Re: Customise Java DSL in Camel 4

[Marat Gubaidullin]

Hello Claude.

To make it intuitive in Karavan you could make your custom Kamelets that
incapsulate components/dsl configuration complexity.

On Sat, Jul 20, 2024, 12:28 Claude Mamo  wrote:

> Yeah I had considered it but the functionality we want to provide would be
> more intuitive if it's part of the DSL. On the minus side, providing a
> custom DSL would make it harder for us to integrate with designers like
> Apache Karavan so that's for sure something we need to factor in. I should
> highlight that the fromHie(...) EIP example is actually meant to be a
> wrapper for any endpoint (direct, http, etc...). I could use interceptors,
> however, I'm trying to make this more idiomatic.
>
> On Sat, Jul 20, 2024 at 1:55 PM Ivan Kulaga <
> kulagaivanandreev...@gmail.com>
> wrote:
>
> > Hello Claude!
> >
> > Please tell, have you considered writing custom components? Writing a new
> > component is a somewhat common task, and there are many instruments and
> > examples for that in camel (
> > https://camel.apache.org/manual/writing-components.html).
> > With custom components, your camel route may look like this:
> > from("hie:my-hie-server-address?my-hie-parameter=value")
> > .transform(...)
> > .to(mrs:my-mrs-server-address?action=open)
> > .transform(...)
> > .to("hie:my-hie-server-address")
> > Writing custom components does not require forking camel repo, you can
> just
> > add them as a dependency in your application and then add them to camel
> > context at application configuration step.
> >
> > Best regards,
> >
> > Ivan
> >
> > On Sat, Jul 20, 2024 at 4:23 PM Claude Mamo 
> wrote:
> >
> > > Hello Camel community,
> > >
> > > Probably this has been asked before but couldn't find a good answer in
> > the
> > > mailing lists nor Zulip. I'd like to tailor the Camel Java DSL for
> health
> > > information exchange. This means creating a no. of EIPs. For example:
> > >
> > > fromHie(...).transform(...).openMRS(...).transform(...).toHie(...)
> > >
> > > So far, all I've come up with is a base class extending RouteBuilder
> but
> > > this approach doesn't really work for various reasons. I've came across
> > > https://github.com/oehf/ipf/tree/master which I think it's extending
> the
> > > Camel DSL by means of Groovy metaprogramming. Doesn't seem like a bad
> > > approach though I'm looking for alternatives which don't include
> forking
> > > the Camel repo. Ideas? As a side note, I'd also like to extend the YAML
> > DSL
> > > but my focus is on the Java one for now.
> > >
> > > Cheers,
> > >
> > > Claude
> > >
> >
>

Re: Customise Java DSL in Camel 4

[Claude Mamo]

Yeah I had considered it but the functionality we want to provide would be
more intuitive if it's part of the DSL. On the minus side, providing a
custom DSL would make it harder for us to integrate with designers like
Apache Karavan so that's for sure something we need to factor in. I should
highlight that the fromHie(...) EIP example is actually meant to be a
wrapper for any endpoint (direct, http, etc...). I could use interceptors,
however, I'm trying to make this more idiomatic.

On Sat, Jul 20, 2024 at 1:55 PM Ivan Kulaga 
wrote:

> Hello Claude!
>
> Please tell, have you considered writing custom components? Writing a new
> component is a somewhat common task, and there are many instruments and
> examples for that in camel (
> https://camel.apache.org/manual/writing-components.html).
> With custom components, your camel route may look like this:
> from("hie:my-hie-server-address?my-hie-parameter=value")
> .transform(...)
> .to(mrs:my-mrs-server-address?action=open)
> .transform(...)
> .to("hie:my-hie-server-address")
> Writing custom components does not require forking camel repo, you can just
> add them as a dependency in your application and then add them to camel
> context at application configuration step.
>
> Best regards,
>
> Ivan
>
> On Sat, Jul 20, 2024 at 4:23 PM Claude Mamo  wrote:
>
> > Hello Camel community,
> >
> > Probably this has been asked before but couldn't find a good answer in
> the
> > mailing lists nor Zulip. I'd like to tailor the Camel Java DSL for health
> > information exchange. This means creating a no. of EIPs. For example:
> >
> > fromHie(...).transform(...).openMRS(...).transform(...).toHie(...)
> >
> > So far, all I've come up with is a base class extending RouteBuilder but
> > this approach doesn't really work for various reasons. I've came across
> > https://github.com/oehf/ipf/tree/master which I think it's extending the
> > Camel DSL by means of Groovy metaprogramming. Doesn't seem like a bad
> > approach though I'm looking for alternatives which don't include forking
> > the Camel repo. Ideas? As a side note, I'd also like to extend the YAML
> DSL
> > but my focus is on the Java one for now.
> >
> > Cheers,
> >
> > Claude
> >
>

Re: Customise Java DSL in Camel 4

[Ivan Kulaga]

Hello Claude!

Please tell, have you considered writing custom components? Writing a new
component is a somewhat common task, and there are many instruments and
examples for that in camel (
https://camel.apache.org/manual/writing-components.html).
With custom components, your camel route may look like this:
from("hie:my-hie-server-address?my-hie-parameter=value")
.transform(...)
.to(mrs:my-mrs-server-address?action=open)
.transform(...)
.to("hie:my-hie-server-address")
Writing custom components does not require forking camel repo, you can just
add them as a dependency in your application and then add them to camel
context at application configuration step.

Best regards,

Ivan

On Sat, Jul 20, 2024 at 4:23 PM Claude Mamo  wrote:

> Hello Camel community,
>
> Probably this has been asked before but couldn't find a good answer in the
> mailing lists nor Zulip. I'd like to tailor the Camel Java DSL for health
> information exchange. This means creating a no. of EIPs. For example:
>
> fromHie(...).transform(...).openMRS(...).transform(...).toHie(...)
>
> So far, all I've come up with is a base class extending RouteBuilder but
> this approach doesn't really work for various reasons. I've came across
> https://github.com/oehf/ipf/tree/master which I think it's extending the
> Camel DSL by means of Groovy metaprogramming. Doesn't seem like a bad
> approach though I'm looking for alternatives which don't include forking
> the Camel repo. Ideas? As a side note, I'd also like to extend the YAML DSL
> but my focus is on the Java one for now.
>
> Cheers,
>
> Claude
>

Customise Java DSL in Camel 4

[Claude Mamo]

Hello Camel community,

Probably this has been asked before but couldn't find a good answer in the
mailing lists nor Zulip. I'd like to tailor the Camel Java DSL for health
information exchange. This means creating a no. of EIPs. For example:

fromHie(...).transform(...).openMRS(...).transform(...).toHie(...)

So far, all I've come up with is a base class extending RouteBuilder but
this approach doesn't really work for various reasons. I've came across
https://github.com/oehf/ipf/tree/master which I think it's extending the
Camel DSL by means of Groovy metaprogramming. Doesn't seem like a bad
approach though I'm looking for alternatives which don't include forking
the Camel repo. Ideas? As a side note, I'd also like to extend the YAML DSL
but my focus is on the Java one for now.

Cheers,

Claude

RE: Troubles with dynamic routing RabbiMQ endpoint and route start/stop

[Jan Bares, WOOD & Co.]

Hi,

We upgraded to camel-spring-rabbitmq 4.6.0 but we see the very same problem as 
described bellow, Just to recap - we have dynamic toD() endpoint of 
SpringRabbitMQ producer (spring-rabbitmq). We send few exchanges and stop the 
route. Then we start the route and send another exchange, but 
SpringRabbitMQProducer says.

Failed delivery for (MessageId: 7691536141474904 on ExchangeId: 
7691536141474904). Exhausted after delivery attempt: 1 caught: 
java.util.concurrent.RejectedExecutionException

In SpringRabbitMQProducer

public boolean process(Exchange exchange, AsyncCallback callback) {
if (!this.isRunAllowed()) {// 113
if (exchange.getException() == null) {// 114
exchange.setException(new RejectedExecutionException());// 115
}

It seems that the route start stop combined with dynamic routing does not work 
as expected.

Kind regards, Jan

> -Original Message-
> From: Claus Ibsen 
> Sent: Thursday, July 4, 2024 10:05 AM
> To: users@camel.apache.org
> Subject: Re: Troubles with dynamic routing RabbiMQ endpoint and route 
> start/stop
>
> Hi
>
> camel-rabbitmq is the old component that is deprecated.
> You should use camel-spring-rabbitmq
>
> And you cannot mix old Camel v3 components with Camel v4
>
> On Thu, Jul 4, 2024 at 9:52 AM Jan Bares, WOOD & Co.
>  wrote:
>
> > Hi,
> >
> > We have dynamic toD() endpoint of RabbitMQ producer (camel-rabbitmq). We
> > send few exchanges and stop the route. Then we start the route and send
> > another exchange, but RabbitMQProducer says:
> >
> > Failed delivery for (MessageId: 9269944780100 on ExchangeId:
> > 9269944780100). Exhausted after delivery attempt: 1 caught:
> > java.util.concurrent.RejectedExecutionException
> > java.util.concurrent.RejectedExecutionException: null
> > at
> >
> org.apache.camel.component.rabbitmq.RabbitMQProducer.process(RabbitMQPro
> ducer.java:199)
> > ...
> >
> > This is because the RabbbitMQProducer is not running:
> >
> > public boolean process(Exchange exchange, AsyncCallback callback) {
> > if (!this.isRunAllowed()) {// 197
> > if (exchange.getException() == null) {// 198
> > exchange.setException(new RejectedExecutionException());//
> > 199
> > }
> >
> > I suspect this is a bug related to dynamic routing.
> >
> > SpringBoot 3.2.5
> > Camel 4.6.0
> > camel-rabbitmq 3.22.2
> >
> > Thank you for any pointers, Jan
> >
> > Jan Bares
> > Head of Calypso development | IT Development

Jan Bares
Head of Calypso development | IT Development

Phone: +420 222 096 457
Mobile: +420 776 333 676
Email: jan.ba...@wood.cz

WOOD & Company
Palladium, nám. Republiky 1079/1a, 110 00 Prague 1, Czech Republic | wood.cz






DISCLAIMER
WOOD & Company Financial Services, a.s. and its branches are authorized and 
regulated by the CNB as Home State regulator and in Poland by the KNF, in 
Slovakia by the NBS, in Italy by the CONSOB and in the UK by the FCA as Host 
State regulators. For further information about WOOD & Co., its investment 
services, financial instruments and associated risks, safeguard client assets 
(incl. compensation schemes) and contractual relationship please see our 
website at www.wood.com under section Corporate 
Governance. Unless otherwise stated, this transmission is neither an offer nor 
the solicitation of an offer to sell or purchase any investment. All estimates, 
opinions and other information contained herein are subject to change without 
notice and are provided in good faith but without legal responsibility or 
liability. Opinion may be personal to the author and may not reflect the 
opinions of WOOD & Co. Communications from sales persons, sales traders or 
traders should not be regarded as investment research and may contain opinions 
or trading ideas which are different from WOOD & Co. investment research 
opinions. This e-mail and any attachments are confidential and may be 
privileged or otherwise protected from disclosure. If you are not a named 
addressee you must not use, disclose, distribute, copy, print or rely on this 
e-mail and any of its attachments. Please notify the sender that you have 
received this email by mistake by replying to the email, and then delete the 
email and any copies of it. Although WOOD & Co. routinely screens e-mails for 
viruses, addressees should scan this e-mail and any attachments for viruses. 
WOOD & Co. makes no representation or warranty as to the absence of viruses in 
this e-mail or any attachments. Please note that to ensure regulatory 
compliance and for the protection of our clients and business, we may monitor 
and read e-mails sent to and from our server(s).

Re: [VOTE] Release Apache Camel Kamelets 4.7.0

[Andrea Cosentino]

Thanks all the vote passes.

I'll go ahead with the process.

Thanks.

Il giorno mar 16 lug 2024 alle ore 09:18 Gaëlle Fournier <
gaelle.fournier.w...@gmail.com> ha scritto:

> +1 (non-binding)
>
> Thanks!
>
> ---
> Gaëlle
>
> Le lun. 15 juil. 2024 à 09:50, Andrea Cosentino  a
> écrit :
>
> > Hello all,
> >
> > This is a vote for releasing camel-kamelets 4.7.0
> >
> > This is a release supporting Camel 4.7.0 dev release.
> >
> > Kamelets release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.7.0
> > Kamelets staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1734
> > Kamelets Tag:
> > https://github.com/apache/camel-kamelets/releases/tag/v4.7.0
> >
> > Please cast your vote.
> >
> > [ ] +1 Release camel-kamelets 4.7.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Here's my +1.
> >
> > Thanks,
> > Andrea Cosentino
> >
>

[RESULT] [VOTE] Release Apache Camel Kamelets 4.7.0

[Andrea Cosentino]

Hello all,

This vote passes with the following result:

3 +1 binding votes: Andrea Cosentino, Marat Gubaidullin and Otavio Rodolfo
Piske

2 +1 non-binding votes: Claudio Miranda and Gaelle Fournier

Thanks all for voting.

I'll go ahead with the process.

Cheers

Re: [VOTE] Release Apache Camel Kamelets 4.7.0

[Gaëlle Fournier]

+1 (non-binding)

Thanks!

---
Gaëlle

Le lun. 15 juil. 2024 à 09:50, Andrea Cosentino  a
écrit :

> Hello all,
>
> This is a vote for releasing camel-kamelets 4.7.0
>
> This is a release supporting Camel 4.7.0 dev release.
>
> Kamelets release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.7.0
> Kamelets staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1734
> Kamelets Tag:
> https://github.com/apache/camel-kamelets/releases/tag/v4.7.0
>
> Please cast your vote.
>
> [ ] +1 Release camel-kamelets 4.7.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Here's my +1.
>
> Thanks,
> Andrea Cosentino
>

Re: [VOTE] Release Apache Camel Kamelets 4.7.0

[Otavio Rodolfo Piske]

+1 (binding)

Thanks Andrea!

On Mon, Jul 15, 2024 at 3:54 PM Marat Gubaidullin <
marat.gubaidul...@gmail.com> wrote:

> +1 (binding)
>
> Thanks Andrea
>
> On Mon, Jul 15, 2024 at 3:50 AM Andrea Cosentino 
> wrote:
>
> > Hello all,
> >
> > This is a vote for releasing camel-kamelets 4.7.0
> >
> > This is a release supporting Camel 4.7.0 dev release.
> >
> > Kamelets release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.7.0
> > Kamelets staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1734
> > Kamelets Tag:
> > https://github.com/apache/camel-kamelets/releases/tag/v4.7.0
> >
> > Please cast your vote.
> >
> > [ ] +1 Release camel-kamelets 4.7.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Here's my +1.
> >
> > Thanks,
> > Andrea Cosentino
> >
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release Apache Camel Kamelets 4.7.0

[Marat Gubaidullin]

+1 (binding)

Thanks Andrea

On Mon, Jul 15, 2024 at 3:50 AM Andrea Cosentino  wrote:

> Hello all,
>
> This is a vote for releasing camel-kamelets 4.7.0
>
> This is a release supporting Camel 4.7.0 dev release.
>
> Kamelets release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.7.0
> Kamelets staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1734
> Kamelets Tag:
> https://github.com/apache/camel-kamelets/releases/tag/v4.7.0
>
> Please cast your vote.
>
> [ ] +1 Release camel-kamelets 4.7.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Here's my +1.
>
> Thanks,
> Andrea Cosentino
>

Re: [VOTE] Release Apache Camel Kamelets 4.7.0

[Claudio Miranda]

+1 (non binding)

Em seg., 15 de jul. de 2024 às 08:50, Andrea Cosentino
 escreveu:
>
> Hello all,
>
> This is a vote for releasing camel-kamelets 4.7.0
>
> This is a release supporting Camel 4.7.0 dev release.
>
> Kamelets release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.7.0
> Kamelets staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1734
> Kamelets Tag:
> https://github.com/apache/camel-kamelets/releases/tag/v4.7.0
>
> Please cast your vote.
>
> [ ] +1 Release camel-kamelets 4.7.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Here's my +1.
>
> Thanks,
> Andrea Cosentino



-- 
  Claudio Miranda

clau...@claudius.com.br
http://www.claudius.com.br

[VOTE] Release Apache Camel Kamelets 4.7.0

[Andrea Cosentino]

Hello all,

This is a vote for releasing camel-kamelets 4.7.0

This is a release supporting Camel 4.7.0 dev release.

Kamelets release files:
https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.7.0
Kamelets staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1734
Kamelets Tag:
https://github.com/apache/camel-kamelets/releases/tag/v4.7.0

Please cast your vote.

[ ] +1 Release camel-kamelets 4.7.0
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

Here's my +1.

Thanks,
Andrea Cosentino

[ANNOUNCE] Apache Camel 4.7.0 Released

[Gregor Zurowski]

The Camel PMC is pleased to announce the release of Apache Camel 4.7.0.

Apache Camel is an open source integration framework that empowers you
to quickly and easily integrate various systems consuming or producing
data.

This release contains 198 new features and improvements.

The release is available for immediate download at:

https://camel.apache.org/download/

For more details please take a look at the release notes at:

https://camel.apache.org/releases/release-4.7.0/

Re: Camel 4.6.0: Issue with AdviceWithRouteBuilder

[Claus Ibsen]

Hi

No but try with 4.7.0 when its released

On Fri, Jul 12, 2024 at 11:14 AM Klug Andreas (BD/SWD-BEB5)
 wrote:

> Hello everyone,
>
> After migrating from 4.4.0 to 4.6.0 we experience a strange issue with the
> AdviceWithRouteBuilder.
>
> We do have multiple AdviceWithTasks which are working in 4.4.0 and 4.6.0,
> e. g.
>
>   *   weaveByToUri("micrometer:.*").before()
>   *   weaveById("*").selectLast().before()
>
> However, using weaveAddFirst().before() or builder.weaveAddFirst().after()
> won’t work starting from 4.6.0.
> I double-checked that by weaving in pretty simple to identify statements
> like
> .log("")
> and finding these statements in the route dump.
> Even trying to mimic weaveAddFirst() by using
> weaveById(“*”).selectFirst().before() or
> weaveById(“*”).selectFirst().after() doesn’t seem to work.
>
> Do you have any suggestions?
>
> Best Regards,
> Andreas
>


-- 
Claus Ibsen
-
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Camel 4.6.0: Issue with AdviceWithRouteBuilder

[Klug Andreas (BD/SWD-BEB5)]

Hello everyone,

After migrating from 4.4.0 to 4.6.0 we experience a strange issue with the 
AdviceWithRouteBuilder.

We do have multiple AdviceWithTasks which are working in 4.4.0 and 4.6.0, e. g.

  *   weaveByToUri("micrometer:.*").before()
  *   weaveById("*").selectLast().before()

However, using weaveAddFirst().before() or builder.weaveAddFirst().after() 
won’t work starting from 4.6.0.
I double-checked that by weaving in pretty simple to identify statements like 
.log("")
 and finding these statements in the route dump.
Even trying to mimic weaveAddFirst() by using 
weaveById(“*”).selectFirst().before() or weaveById(“*”).selectFirst().after() 
doesn’t seem to work.

Do you have any suggestions?

Best Regards,
Andreas

回复: MDCUnitOfWork not working with vert.x-eventloop-thread

[_ Jane]

Hi Claus,

Thanks for the suggestion. I tested the sample code with Camel Quarkus 3.2 and 
3.8. The result logs are the same.



发件人: Claus Ibsen 
发送时间: 2024年7月11日 15:24
收件人: users@camel.apache.org 
主题: Re: MDCUnitOfWork not working with vert.x-eventloop-thread

Hi

This is an old Quarkus version and we dont support this
 CAMEL VERSION   QUARKUSJDK   KIND RELEASED SUPPORTED UNTIL
 3.18.6   2.13.3   11  LTS   April 2023July 2023

You can try latest v4 Camel version and see what happens there.



On Thu, Jul 11, 2024 at 7:58 AM _ Jane  wrote:

> Dear community,
>
> When I using Camel Quarkus and use camel-knative event producer, the
> thread name is vert.x-eventloop-thread-xxx and the fields from
> MDCUnitOfWork (like camel.routeId) is missing. Is there any special
> configuration needed to show the MDCUnitOfWork fields in my log? Thanks!
>
> The Camel Quarkus version is 2.13.3 and here is the sample code:
>
> from("timer://foo?fixedRate=true=6")
> .routeId("route_timer_test")
> .setBody(constant("test event"))
> .setHeader(CloudEvent.CAMEL_CLOUD_EVENT_SOURCE, constant("test-route"))
> .log("there is camel.routeId")
> .to("knative:event/broker-test")
> .log("there isn't camel.routeId")
>
> The log format config is "quarkus.log.console.format=%d{-MM-dd
> HH:mm:ss,SSS} %-5p [%c{3.}] (%t) - %X{camel.routeId} - %s%e%n" and the
> result log is:
>
> 2024-07-11 13:53:51,273 INFO  [route_timer_test] (Camel (test-route)
> thread #2 - timer://foo) - route_timer_test- there is camel.routeId
> 2024-07-11 13:53:51,401 INFO  [route_timer_test]
> (vert.x-eventloop-thread-0) -  - there isn't camel.routeId
>
>

--
Claus Ibsen
-
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel NotifyBuilder does not match when exception is thrown

[Lance Java]

Thanks Claus, since I don't have routeId's I searched the NotifyBuilder
javadocs and found wereSentTo(...). I was able to use this to match the
routes which are not the inbound entry point.

This works:

@Testpublic void testNotify() {
  NotifyBuilder notifierA = new NotifyBuilder(camelContext)
  .from("direct:route-a")
  .whenDone(1)
  .create();
  NotifyBuilder notifierB = new NotifyBuilder(camelContext)
  .wereSentTo("direct:route-b")
  .whenDone(1)
  .create();
  NotifyBuilder notifierDead = new NotifyBuilder(camelContext)
  .wereSentTo("direct:dead-letter")
  .whenDone(1)
  .create();

  producerTemplate.sendBody("direct:route-a", null);

  assertThat(list).containsExactly("a", "b", "dead");
  assertThat(notifierA.matches(5, TimeUnit.SECONDS)).isTrue();
  assertThat(notifierB.matches(5, TimeUnit.SECONDS)).isTrue();
  assertThat(notifierDead.matches(5, TimeUnit.SECONDS)).isTrue();
}


On Thu, 11 Jul 2024 at 12:04, Claus Ibsen  wrote:

> Hi
>
> whenFrom is from the original route, so that would be "direct:route-a"
>
> You can use fromCurrentRoute (route id based) instead
>
> On Thu, Jul 11, 2024 at 12:16 PM Lance Java
>  wrote:
>
> > I asked this question on stack overflow but didn't get a response so
> asking
> > here
> >
> >
> https://stackoverflow.com/questions/78720143/camel-notifybuilder-does-not-match-when-exception-is-thrown
> >
> > It seems that camel's NotifyBuilder
> >  works in normal
> > message processing but does not work when exceptions are thrown.
> >
> > Please see the following test case where I create the following routes
> >
> >- direct:route-a adds "a" to a list and passes to direct:route-b
> >- direct:route-b adds "b" to a list and throws exception
> >- errorHandler routes to direct:dead-letter as a deadLetterChannel
> >- direct:dead-letter adds "dead" to a list
> >
> > I can see that the list contains "a", "b", "dead" when I send a message
> to
> > direct:route-a
> >
> > But the NotifyBuilders for direct:route-b and direct:dead-letter don't
> > match for some reason.
> >
> > Is there a bug in NotifyBuilder where they don't match when exceptions
> are
> > thrown? Am I using NotifyBuilder incorrectly? I've tried both
> > NotifyBuilder.whenDone(1) and NotifyBuilder.whenFailed(1) and neither
> > causes a match.
> >
> > Looking at the NotifyBuilder javadoc
> > <
> >
> https://www.javadoc.io/doc/org.apache.camel/camel-core/2.25.4/org/apache/camel/builder/NotifyBuilder.html#whenDone-int-
> > >
> > I
> > see the following comment for whenDone(...)
> >
> > > The difference between done and completed is that done can also include
> > failed messages, where as completed is only successful processed
> messages.
> >
> > import lombok.extern.slf4j.Slf4j;import
> > org.apache.camel.CamelContext;import
> > org.apache.camel.ProducerTemplate;import
> > org.apache.camel.builder.NotifyBuilder;import
> > org.apache.camel.builder.RouteBuilder;import
> > org.apache.camel.impl.DefaultCamelContext;import
> > org.apache.camel.impl.engine.DefaultProducerTemplate;import
> > org.junit.jupiter.api.AfterEach;import
> > org.junit.jupiter.api.BeforeEach;import org.junit.jupiter.api.Test;
> > import java.util.LinkedList;import java.util.List;import
> > java.util.concurrent.TimeUnit;
> > import static org.assertj.core.api.Assertions.assertThat;
> > @Slf4jpublic class NotifyBuilderTest {
> > private CamelContext camelContext;
> > private ProducerTemplate producerTemplate;
> > private List list;
> >
> > @BeforeEach
> > public void beforeEach() throws Exception {
> > list = new LinkedList<>();
> > camelContext = new DefaultCamelContext();
> >
> > camelContext.addRoutes(new RouteBuilder() {
> > @Override
> > public void configure() {
> > from("direct:route-a")
> > .process(exchange -> list.add("a"))
> > .to("direct:route-b");
> >
> > from("direct:route-b")
> > .process(exchange -> list.add("b"))
> > .process(exchange -> { throw new
> Exception("foo");
> > });
> >
> > errorHandler(deadLetterChannel("direct:dead-letter"));
> >
> > from("direct:dead-letter")
> > .process(exchange -> list.add("dead"));
> > }
> > });
> > producerTemplate = new DefaultProducerTemplate(camelContext);
> >
> > camelContext.start();
> > producerTemplate.start();
> > }
> >
> > @AfterEach
> > public void afterEach() {
> > producerTemplate.stop();
> > camelContext.stop();
> > }
> >
> > @Test
> > public void testNotify() {
> > NotifyBuilder notifierA = new NotifyBuilder(camelContext)
> > .from("direct:route-a")
> > .whenDone(1)
> > .create();
> > 

Re: Camel NotifyBuilder does not match when exception is thrown

[Claus Ibsen]

Hi

whenFrom is from the original route, so that would be "direct:route-a"

You can use fromCurrentRoute (route id based) instead

On Thu, Jul 11, 2024 at 12:16 PM Lance Java
 wrote:

> I asked this question on stack overflow but didn't get a response so asking
> here
>
> https://stackoverflow.com/questions/78720143/camel-notifybuilder-does-not-match-when-exception-is-thrown
>
> It seems that camel's NotifyBuilder
>  works in normal
> message processing but does not work when exceptions are thrown.
>
> Please see the following test case where I create the following routes
>
>- direct:route-a adds "a" to a list and passes to direct:route-b
>- direct:route-b adds "b" to a list and throws exception
>- errorHandler routes to direct:dead-letter as a deadLetterChannel
>- direct:dead-letter adds "dead" to a list
>
> I can see that the list contains "a", "b", "dead" when I send a message to
> direct:route-a
>
> But the NotifyBuilders for direct:route-b and direct:dead-letter don't
> match for some reason.
>
> Is there a bug in NotifyBuilder where they don't match when exceptions are
> thrown? Am I using NotifyBuilder incorrectly? I've tried both
> NotifyBuilder.whenDone(1) and NotifyBuilder.whenFailed(1) and neither
> causes a match.
>
> Looking at the NotifyBuilder javadoc
> <
> https://www.javadoc.io/doc/org.apache.camel/camel-core/2.25.4/org/apache/camel/builder/NotifyBuilder.html#whenDone-int-
> >
> I
> see the following comment for whenDone(...)
>
> > The difference between done and completed is that done can also include
> failed messages, where as completed is only successful processed messages.
>
> import lombok.extern.slf4j.Slf4j;import
> org.apache.camel.CamelContext;import
> org.apache.camel.ProducerTemplate;import
> org.apache.camel.builder.NotifyBuilder;import
> org.apache.camel.builder.RouteBuilder;import
> org.apache.camel.impl.DefaultCamelContext;import
> org.apache.camel.impl.engine.DefaultProducerTemplate;import
> org.junit.jupiter.api.AfterEach;import
> org.junit.jupiter.api.BeforeEach;import org.junit.jupiter.api.Test;
> import java.util.LinkedList;import java.util.List;import
> java.util.concurrent.TimeUnit;
> import static org.assertj.core.api.Assertions.assertThat;
> @Slf4jpublic class NotifyBuilderTest {
> private CamelContext camelContext;
> private ProducerTemplate producerTemplate;
> private List list;
>
> @BeforeEach
> public void beforeEach() throws Exception {
> list = new LinkedList<>();
> camelContext = new DefaultCamelContext();
>
> camelContext.addRoutes(new RouteBuilder() {
> @Override
> public void configure() {
> from("direct:route-a")
> .process(exchange -> list.add("a"))
> .to("direct:route-b");
>
> from("direct:route-b")
> .process(exchange -> list.add("b"))
> .process(exchange -> { throw new Exception("foo");
> });
>
> errorHandler(deadLetterChannel("direct:dead-letter"));
>
> from("direct:dead-letter")
> .process(exchange -> list.add("dead"));
> }
> });
> producerTemplate = new DefaultProducerTemplate(camelContext);
>
> camelContext.start();
> producerTemplate.start();
> }
>
> @AfterEach
> public void afterEach() {
> producerTemplate.stop();
> camelContext.stop();
> }
>
> @Test
> public void testNotify() {
> NotifyBuilder notifierA = new NotifyBuilder(camelContext)
> .from("direct:route-a")
> .whenDone(1)
> .create();
> NotifyBuilder notifierB = new NotifyBuilder(camelContext)
> .from("direct:route-b")
> .whenDone(1)
> .create();
> NotifyBuilder notifierDead = new NotifyBuilder(camelContext)
> .from("direct:dead-letter")
> .whenDone(1)
> .create();
>
> producerTemplate.sendBody("direct:route-a", null);
>
> // this succeeds
> assertThat(list).containsExactly("a", "b", "dead");
>
> // this succeeds
> assertThat(notifierA.matches(5, TimeUnit.SECONDS)).isTrue();
>
> // this fails
> assertThat(notifierB.matches(5, TimeUnit.SECONDS)).isTrue();
>
> // this fails
> assertThat(notifierDead.matches(5, TimeUnit.SECONDS)).isTrue();
> }
> }
>


-- 
Claus Ibsen
-
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Camel NotifyBuilder does not match when exception is thrown

[Lance Java]

I asked this question on stack overflow but didn't get a response so asking
here
https://stackoverflow.com/questions/78720143/camel-notifybuilder-does-not-match-when-exception-is-thrown

It seems that camel's NotifyBuilder
 works in normal
message processing but does not work when exceptions are thrown.

Please see the following test case where I create the following routes

   - direct:route-a adds "a" to a list and passes to direct:route-b
   - direct:route-b adds "b" to a list and throws exception
   - errorHandler routes to direct:dead-letter as a deadLetterChannel
   - direct:dead-letter adds "dead" to a list

I can see that the list contains "a", "b", "dead" when I send a message to
direct:route-a

But the NotifyBuilders for direct:route-b and direct:dead-letter don't
match for some reason.

Is there a bug in NotifyBuilder where they don't match when exceptions are
thrown? Am I using NotifyBuilder incorrectly? I've tried both
NotifyBuilder.whenDone(1) and NotifyBuilder.whenFailed(1) and neither
causes a match.

Looking at the NotifyBuilder javadoc

I
see the following comment for whenDone(...)

> The difference between done and completed is that done can also include
failed messages, where as completed is only successful processed messages.

import lombok.extern.slf4j.Slf4j;import
org.apache.camel.CamelContext;import
org.apache.camel.ProducerTemplate;import
org.apache.camel.builder.NotifyBuilder;import
org.apache.camel.builder.RouteBuilder;import
org.apache.camel.impl.DefaultCamelContext;import
org.apache.camel.impl.engine.DefaultProducerTemplate;import
org.junit.jupiter.api.AfterEach;import
org.junit.jupiter.api.BeforeEach;import org.junit.jupiter.api.Test;
import java.util.LinkedList;import java.util.List;import
java.util.concurrent.TimeUnit;
import static org.assertj.core.api.Assertions.assertThat;
@Slf4jpublic class NotifyBuilderTest {
private CamelContext camelContext;
private ProducerTemplate producerTemplate;
private List list;

@BeforeEach
public void beforeEach() throws Exception {
list = new LinkedList<>();
camelContext = new DefaultCamelContext();

camelContext.addRoutes(new RouteBuilder() {
@Override
public void configure() {
from("direct:route-a")
.process(exchange -> list.add("a"))
.to("direct:route-b");

from("direct:route-b")
.process(exchange -> list.add("b"))
.process(exchange -> { throw new Exception("foo"); });

errorHandler(deadLetterChannel("direct:dead-letter"));

from("direct:dead-letter")
.process(exchange -> list.add("dead"));
}
});
producerTemplate = new DefaultProducerTemplate(camelContext);

camelContext.start();
producerTemplate.start();
}

@AfterEach
public void afterEach() {
producerTemplate.stop();
camelContext.stop();
}

@Test
public void testNotify() {
NotifyBuilder notifierA = new NotifyBuilder(camelContext)
.from("direct:route-a")
.whenDone(1)
.create();
NotifyBuilder notifierB = new NotifyBuilder(camelContext)
.from("direct:route-b")
.whenDone(1)
.create();
NotifyBuilder notifierDead = new NotifyBuilder(camelContext)
.from("direct:dead-letter")
.whenDone(1)
.create();

producerTemplate.sendBody("direct:route-a", null);

// this succeeds
assertThat(list).containsExactly("a", "b", "dead");

// this succeeds
assertThat(notifierA.matches(5, TimeUnit.SECONDS)).isTrue();

// this fails
assertThat(notifierB.matches(5, TimeUnit.SECONDS)).isTrue();

// this fails
assertThat(notifierDead.matches(5, TimeUnit.SECONDS)).isTrue();
}
}

Re: MDCUnitOfWork not working with vert.x-eventloop-thread

[Claus Ibsen]

Hi

This is an old Quarkus version and we dont support this
 CAMEL VERSION   QUARKUSJDK   KIND RELEASED SUPPORTED UNTIL
 3.18.6   2.13.3   11  LTS   April 2023July 2023

You can try latest v4 Camel version and see what happens there.



On Thu, Jul 11, 2024 at 7:58 AM _ Jane  wrote:

> Dear community,
>
> When I using Camel Quarkus and use camel-knative event producer, the
> thread name is vert.x-eventloop-thread-xxx and the fields from
> MDCUnitOfWork (like camel.routeId) is missing. Is there any special
> configuration needed to show the MDCUnitOfWork fields in my log? Thanks!
>
> The Camel Quarkus version is 2.13.3 and here is the sample code:
>
> from("timer://foo?fixedRate=true=6")
> .routeId("route_timer_test")
> .setBody(constant("test event"))
> .setHeader(CloudEvent.CAMEL_CLOUD_EVENT_SOURCE, constant("test-route"))
> .log("there is camel.routeId")
> .to("knative:event/broker-test")
> .log("there isn't camel.routeId")
>
> The log format config is "quarkus.log.console.format=%d{-MM-dd
> HH:mm:ss,SSS} %-5p [%c{3.}] (%t) - %X{camel.routeId} - %s%e%n" and the
> result log is:
>
> 2024-07-11 13:53:51,273 INFO  [route_timer_test] (Camel (test-route)
> thread #2 - timer://foo) - route_timer_test- there is camel.routeId
> 2024-07-11 13:53:51,401 INFO  [route_timer_test]
> (vert.x-eventloop-thread-0) -  - there isn't camel.routeId
>
>

-- 
Claus Ibsen
-
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

MDCUnitOfWork not working with vert.x-eventloop-thread

[_ Jane]

Dear community,

When I using Camel Quarkus and use camel-knative event producer, the thread 
name is vert.x-eventloop-thread-xxx and the fields from MDCUnitOfWork (like 
camel.routeId) is missing. Is there any special configuration needed to show 
the MDCUnitOfWork fields in my log? Thanks!

The Camel Quarkus version is 2.13.3 and here is the sample code:

from("timer://foo?fixedRate=true=6")
.routeId("route_timer_test")
.setBody(constant("test event"))
.setHeader(CloudEvent.CAMEL_CLOUD_EVENT_SOURCE, constant("test-route"))
.log("there is camel.routeId")
.to("knative:event/broker-test")
.log("there isn't camel.routeId")

The log format config is "quarkus.log.console.format=%d{-MM-dd 
HH:mm:ss,SSS} %-5p [%c{3.}] (%t) - %X{camel.routeId} - %s%e%n" and the result 
log is:

2024-07-11 13:53:51,273 INFO  [route_timer_test] (Camel (test-route) thread #2 
- timer://foo) - route_timer_test- there is camel.routeId
2024-07-11 13:53:51,401 INFO  [route_timer_test] (vert.x-eventloop-thread-0) -  
- there isn't camel.routeId

Re: Camel bean

[Claus Ibsen]

Hi

Sounds a bit complex, but you are welcome to create a JIRA.
And provide some sample code that demonstrates this. Or see if you dare to
add some kind of unit test that reproduces this, and works with your fix.



On Fri, Jul 5, 2024 at 5:33 PM logesh  wrote:

> I am trying to use bean with reference and method call.The bean has
> overloaded methods and hence it is being called in this way.The below
> method call was populated with parameter type and value in reference to the
> guidanct provided in  here.
>
> https://camel.apache.org/manual/bean-binding.html#_declaring_parameter_type_and_value
>
> My bean spring DSL looks as below
>
> 
> I get  ambiguous method invocation possible exception.
> On investigating further this was drilled down to issue happening during
> the matchmethod call in BeanInfo class under org.apache.camel.component.
>
> The matchmethod was calling the method splitsafequote method with 4
> parameters (input seperator trime:true and keepquote:true) in
> strignquotehelper class under org.apache.camel.util which splits the
> parameters and types.The problem was isolated to the type and value
> concatenated with space between them ignored.The flag skipleadingwhitespace
> is set to true and is never changed which ignores the space and is missed
> in the parsing logic.
> This in turn breaks at the match method which looks for the indexof(32)
> which is for a whitespace and since it's not there it returns -1 and there
> by breaking the whole purpose of passing parameter type and value.
>
> Camel version used :4.5.0
> Camel components:camel-bean and camel-util
>
> Please let know if this is a bug or if any missing configuration from.my
> side
>
> PS:I changed the flag to false and it works fine with the above bean method
> call
>
> Thanks
> Logeshwaran Devakar
>


-- 
Claus Ibsen
-
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: RabbitMQ component and Failed auto ACK

[Claus Ibsen]

Hi

You need to ask spring-rabbitmq how their auto ack works, but I would
assume it would ack it as soon as Camel receive the message (onMessage)
like JMS.
And that Camel will process the message no matter what.

If you want once and only once semantics then you need something that acks
it later (or something like transactional).
But distributed messaging and networking is complex, also be prepared for
duplicates.

See also the acknowledgeMode option in the camel-spring-rabbitmq docs




On Fri, Jul 5, 2024 at 2:09 PM Guillem Folch 
wrote:

> Hi all,
>
>
> I'm currently using a RabbitMQ queue and a client application using SPRING
> RABBITMQ component as consumer.
> Currently we are not setting any acknowdlege-Mode, so I guess we are using
> auto acknacknowledgement , so we let Camel component to manage
> automatically the ACK of the message  when the consumer receives the
> message from the queue.
> Our simplified Camel route looks like the following:
>
>
> 
>uri="spring-rabbitmq:MyExchange?routingKey=MyQueue=MyQueue=20"/>
> 
>   
>  
>
> My question is what happens with the flow if the Ack cannot be sent
> successfully, for instance because there's a network issue or a problem in
> RabbitMQ.
> Will be the Camel message aborted? Will continue the flow to the
> direct:someOtherCamleRoute?
>
> I was expecting that in this situation the flow will not continue. But
> I've got some customer logs that seem to indicate that the flow continues
> and the message is sent to the processor and to the next route.
> In this case as the message is not acknowledged in RabbitMQ, after some
> time is already available for another consumer and it's duplicating the
> message process.
> Is this possible? Am I missing something?
>
> Thanks
> Guillem
>
>
>
>

-- 
Claus Ibsen
-
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Camel bean

[logesh]

I am trying to use bean with reference and method call.The bean has
overloaded methods and hence it is being called in this way.The below
method call was populated with parameter type and value in reference to the
guidanct provided in  here.
https://camel.apache.org/manual/bean-binding.html#_declaring_parameter_type_and_value

My bean spring DSL looks as below

RabbitMQ component and Failed auto ACK

[Guillem Folch]

Hi all,


I'm currently using a RabbitMQ queue and a client application using SPRING 
RABBITMQ component as consumer.
Currently we are not setting any acknowdlege-Mode, so I guess we are using auto 
acknacknowledgement , so we let Camel component to manage automatically the ACK 
of the message  when the consumer receives the message from the queue.
Our simplified Camel route looks like the following:



  
  
  
 

My question is what happens with the flow if the Ack cannot be sent 
successfully, for instance because there's a network issue or a problem in 
RabbitMQ.
Will be the Camel message aborted? Will continue the flow to the 
direct:someOtherCamleRoute?

I was expecting that in this situation the flow will not continue. But I've got 
some customer logs that seem to indicate that the flow continues and the 
message is sent to the processor and to the next route.
In this case as the message is not acknowledged in RabbitMQ, after some time is 
already available for another consumer and it's duplicating the message process.
Is this possible? Am I missing something?

Thanks
Guillem

RE: Troubles with dynamic routing RabbiMQ endpoint and route start/stop

[Jan Bares, WOOD & Co.]

Thanks, I was aware of camel-spring-rabbitmq but for camel-rabbitmq 
documentation just recommends to upgrade. Now we have a clear reason.

Jan

> -Original Message-
> From: Claus Ibsen 
> Sent: Thursday, July 4, 2024 10:05 AM
> To: users@camel.apache.org
> Subject: Re: Troubles with dynamic routing RabbiMQ endpoint and route 
> start/stop
>
> Hi
>
> camel-rabbitmq is the old component that is deprecated.
> You should use camel-spring-rabbitmq
>
> And you cannot mix old Camel v3 components with Camel v4
>
> On Thu, Jul 4, 2024 at 9:52 AM Jan Bares, WOOD & Co.
>  wrote:
>
> > Hi,
> >
> > We have dynamic toD() endpoint of RabbitMQ producer (camel-rabbitmq). We
> > send few exchanges and stop the route. Then we start the route and send
> > another exchange, but RabbitMQProducer says:
> >
> > Failed delivery for (MessageId: 9269944780100 on ExchangeId:
> > 9269944780100). Exhausted after delivery attempt: 1 caught:
> > java.util.concurrent.RejectedExecutionException
> > java.util.concurrent.RejectedExecutionException: null
> > at
> >
> org.apache.camel.component.rabbitmq.RabbitMQProducer.process(RabbitMQPro
> ducer.java:199)
> > ...
> >
> > This is because the RabbbitMQProducer is not running:
> >
> > public boolean process(Exchange exchange, AsyncCallback callback) {
> > if (!this.isRunAllowed()) {// 197
> > if (exchange.getException() == null) {// 198
> > exchange.setException(new RejectedExecutionException());//
> > 199
> > }
> >
> > I suspect this is a bug related to dynamic routing.
> >
> > SpringBoot 3.2.5
> > Camel 4.6.0
> > camel-rabbitmq 3.22.2
> >
> > Thank you for any pointers, Jan
> >
> > Jan Bares
> > Head of Calypso development | IT Development
> >
> > Phone: +420 222 096 457
> > Mobile: +420 776 333 676
> > Email: jan.ba...@wood.cz
> >
> > WOOD & Company
> > Palladium, n?m. Republiky 1079/1a, 110 00 Prague 1, Czech Republic |
> > wood.cz
> >
> >
> >
> >
> >
> > 
> > DISCLAIMER
> > WOOD & Company Financial Services, a.s. and its branches are authorized
> > and regulated by the CNB as Home State regulator and in Poland by the KNF,
> > in Slovakia by the NBS, in Italy by the CONSOB and in the UK by the FCA as
> > Host State regulators. For further information about WOOD & Co., its
> > investment services, financial instruments and associated risks, safeguard
> > client assets (incl. compensation schemes) and contractual relationship
> > please see our website at www.wood.com under
> > section Corporate Governance. Unless otherwise stated, this transmission is
> > neither an offer nor the solicitation of an offer to sell or purchase any
> > investment. All estimates, opinions and other information contained herein
> > are subject to change without notice and are provided in good faith but
> > without legal responsibility or liability. Opinion may be personal to the
> > author and may not reflect the opinions of WOOD & Co. Communications from
> > sales persons, sales traders or traders should not be regarded as
> > investment research and may contain opinions or trading ideas which are
> > different from WOOD & Co. investment research opinions. This e-mail and any
> > attachments are confidential and may be privileged or otherwise protected
> > from disclosure. If you are not a named addressee you must not use,
> > disclose, distribute, copy, print or rely on this e-mail and any of its
> > attachments. Please notify the sender that you have received this email by
> > mistake by replying to the email, and then delete the email and any copies
> > of it. Although WOOD & Co. routinely screens e-mails for viruses,
> > addressees should scan this e-mail and any attachments for viruses. WOOD &
> > Co. makes no representation or warranty as to the absence of viruses in
> > this e-mail or any attachments. Please note that to ensure regulatory
> > compliance and for the protection of our clients and business, we may
> > monitor and read e-mails sent to and from our server(s).
> >
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2

Jan Bares
Head of Calypso development | IT Development

Phone: +420 222 096 457
Mobile: +420 776 333 676
Email: jan.ba...@wood.cz

WOOD & Company
Palladium, nám. Republiky 1079/1a, 110 00 Prague 1, Czech Republic | wood.cz






DISCLAIMER
WOOD & Company Financial Services, a.s. and its branches are authorized and 
regulated by the CNB as Home State regulator and in Poland by the KNF, in 
Slovakia by the NBS, in Italy by the CONSOB and in the UK by the FCA as Host 
State regulators. For further information about WOOD & Co., its investment 
services, financial instruments and associated risks, safeguard client assets 
(incl. compensation schemes) and contractual relationship please see our 
website at www.wood.com under section Corporate 
Governance. 

Re: Troubles with dynamic routing RabbiMQ endpoint and route start/stop

[Claus Ibsen]

Hi

camel-rabbitmq is the old component that is deprecated.
You should use camel-spring-rabbitmq

And you cannot mix old Camel v3 components with Camel v4

On Thu, Jul 4, 2024 at 9:52 AM Jan Bares, WOOD & Co.
 wrote:

> Hi,
>
> We have dynamic toD() endpoint of RabbitMQ producer (camel-rabbitmq). We
> send few exchanges and stop the route. Then we start the route and send
> another exchange, but RabbitMQProducer says:
>
> Failed delivery for (MessageId: 9269944780100 on ExchangeId:
> 9269944780100). Exhausted after delivery attempt: 1 caught:
> java.util.concurrent.RejectedExecutionException
> java.util.concurrent.RejectedExecutionException: null
> at
> org.apache.camel.component.rabbitmq.RabbitMQProducer.process(RabbitMQProducer.java:199)
> ...
>
> This is because the RabbbitMQProducer is not running:
>
> public boolean process(Exchange exchange, AsyncCallback callback) {
> if (!this.isRunAllowed()) {// 197
> if (exchange.getException() == null) {// 198
> exchange.setException(new RejectedExecutionException());//
> 199
> }
>
> I suspect this is a bug related to dynamic routing.
>
> SpringBoot 3.2.5
> Camel 4.6.0
> camel-rabbitmq 3.22.2
>
> Thank you for any pointers, Jan
>
> Jan Bares
> Head of Calypso development | IT Development
>
> Phone: +420 222 096 457
> Mobile: +420 776 333 676
> Email: jan.ba...@wood.cz
>
> WOOD & Company
> Palladium, n?m. Republiky 1079/1a, 110 00 Prague 1, Czech Republic |
> wood.cz
>
>
>
>
>
> 
> DISCLAIMER
> WOOD & Company Financial Services, a.s. and its branches are authorized
> and regulated by the CNB as Home State regulator and in Poland by the KNF,
> in Slovakia by the NBS, in Italy by the CONSOB and in the UK by the FCA as
> Host State regulators. For further information about WOOD & Co., its
> investment services, financial instruments and associated risks, safeguard
> client assets (incl. compensation schemes) and contractual relationship
> please see our website at www.wood.com under
> section Corporate Governance. Unless otherwise stated, this transmission is
> neither an offer nor the solicitation of an offer to sell or purchase any
> investment. All estimates, opinions and other information contained herein
> are subject to change without notice and are provided in good faith but
> without legal responsibility or liability. Opinion may be personal to the
> author and may not reflect the opinions of WOOD & Co. Communications from
> sales persons, sales traders or traders should not be regarded as
> investment research and may contain opinions or trading ideas which are
> different from WOOD & Co. investment research opinions. This e-mail and any
> attachments are confidential and may be privileged or otherwise protected
> from disclosure. If you are not a named addressee you must not use,
> disclose, distribute, copy, print or rely on this e-mail and any of its
> attachments. Please notify the sender that you have received this email by
> mistake by replying to the email, and then delete the email and any copies
> of it. Although WOOD & Co. routinely screens e-mails for viruses,
> addressees should scan this e-mail and any attachments for viruses. WOOD &
> Co. makes no representation or warranty as to the absence of viruses in
> this e-mail or any attachments. Please note that to ensure regulatory
> compliance and for the protection of our clients and business, we may
> monitor and read e-mails sent to and from our server(s).
>


-- 
Claus Ibsen
-
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: [VOTE] Release Apache Camel Kamelets 4.4.3

[Andrea Cosentino]

Thanks all the vote passes.

I'll go ahead with the release process.

Il giorno mer 3 lug 2024 alle ore 16:34 Gaëlle Fournier <
gaelle.fournier.w...@gmail.com> ha scritto:

> +1 (non-binding)
>
> Thanks!
>
> ---
> Gaëlle
>
> Le lun. 1 juil. 2024 à 09:59, Andrea Cosentino  a
> écrit :
>
> > Hello all,
> >
> > This is a vote for releasing camel-kamelets 4.4.3
> >
> > This is a release supporting Camel 4.4.3 and it's an LTS release.
> >
> > Kamelets release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.4.3
> > Kamelets staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1726
> > Kamelets Tag:
> > https://github.com/apache/camel-kamelets/releases/tag/v4.4.3
> >
> > Please cast your vote.
> >
> > [ ] +1 Release camel-kamelets 4.4.3
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Here's my +1.
> >
> > Thanks,
> > Andrea Cosentino
> >
>

[RESULT][VOTE] Release Apache Camel Kamelets 4.4.3

[Andrea Cosentino]

Hello all,

The vote passes with the following results:

4 +1 binding votes: Andrea Cosentino, Claus Ibsen, Zineb Bendhiba and
Otavio Rodolfo Piske

2 +1 non-binding votes: Claudio Miranda and Gaelle Fournier

Thanks all for the votes.

I'll go ahead with the process.

Troubles with dynamic routing RabbiMQ endpoint and route start/stop

[Jan Bares, WOOD & Co.]

Hi,

We have dynamic toD() endpoint of RabbitMQ producer (camel-rabbitmq). We send 
few exchanges and stop the route. Then we start the route and send another 
exchange, but RabbitMQProducer says:

Failed delivery for (MessageId: 9269944780100 on ExchangeId: 9269944780100). 
Exhausted after delivery attempt: 1 caught: 
java.util.concurrent.RejectedExecutionException
java.util.concurrent.RejectedExecutionException: null
at 
org.apache.camel.component.rabbitmq.RabbitMQProducer.process(RabbitMQProducer.java:199)
...

This is because the RabbbitMQProducer is not running:

public boolean process(Exchange exchange, AsyncCallback callback) {
if (!this.isRunAllowed()) {// 197
if (exchange.getException() == null) {// 198
exchange.setException(new RejectedExecutionException());// 199
}

I suspect this is a bug related to dynamic routing.

SpringBoot 3.2.5
Camel 4.6.0
camel-rabbitmq 3.22.2

Thank you for any pointers, Jan

Jan Bares
Head of Calypso development | IT Development

Phone: +420 222 096 457
Mobile: +420 776 333 676
Email: jan.ba...@wood.cz

WOOD & Company
Palladium, n?m. Republiky 1079/1a, 110 00 Prague 1, Czech Republic | wood.cz






DISCLAIMER
WOOD & Company Financial Services, a.s. and its branches are authorized and 
regulated by the CNB as Home State regulator and in Poland by the KNF, in 
Slovakia by the NBS, in Italy by the CONSOB and in the UK by the FCA as Host 
State regulators. For further information about WOOD & Co., its investment 
services, financial instruments and associated risks, safeguard client assets 
(incl. compensation schemes) and contractual relationship please see our 
website at www.wood.com under section Corporate 
Governance. Unless otherwise stated, this transmission is neither an offer nor 
the solicitation of an offer to sell or purchase any investment. All estimates, 
opinions and other information contained herein are subject to change without 
notice and are provided in good faith but without legal responsibility or 
liability. Opinion may be personal to the author and may not reflect the 
opinions of WOOD & Co. Communications from sales persons, sales traders or 
traders should not be regarded as investment research and may contain opinions 
or trading ideas which are different from WOOD & Co. investment research 
opinions. This e-mail and any attachments are confidential and may be 
privileged or otherwise protected from disclosure. If you are not a named 
addressee you must not use, disclose, distribute, copy, print or rely on this 
e-mail and any of its attachments. Please notify the sender that you have 
received this email by mistake by replying to the email, and then delete the 
email and any copies of it. Although WOOD & Co. routinely screens e-mails for 
viruses, addressees should scan this e-mail and any attachments for viruses. 
WOOD & Co. makes no representation or warranty as to the absence of viruses in 
this e-mail or any attachments. Please note that to ensure regulatory 
compliance and for the protection of our clients and business, we may monitor 
and read e-mails sent to and from our server(s).

Re: [VOTE] Release Apache Camel Kamelets 4.4.3

[Gaëlle Fournier]

+1 (non-binding)

Thanks!

---
Gaëlle

Le lun. 1 juil. 2024 à 09:59, Andrea Cosentino  a écrit :

> Hello all,
>
> This is a vote for releasing camel-kamelets 4.4.3
>
> This is a release supporting Camel 4.4.3 and it's an LTS release.
>
> Kamelets release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.4.3
> Kamelets staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1726
> Kamelets Tag:
> https://github.com/apache/camel-kamelets/releases/tag/v4.4.3
>
> Please cast your vote.
>
> [ ] +1 Release camel-kamelets 4.4.3
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Here's my +1.
>
> Thanks,
> Andrea Cosentino
>

Re: Camel AWS2-S3 Unable to find valid certification path to the requested target”

[Chirag]

How do you run your app? is trust store overridden somehow?


On Tue, Jul 2, 2024 at 6:10 PM Srikant Mantha 
wrote:

> Hi,
> I am using camel aws s3 to upload a file in my camel-springboot
> microservice with camel aws version as 4.5.0. I am facing connectivity
> issues to the S3 bucket with the
>
> exception message like “unable to find valid certification path to the
> requested target”
>
> Below is my config and endpoint call
>
> My Camel Processor code
>
> //set the payload in the exchange body and the S3 url is constructed in
> the S3Config
> String endpointUri = “s3://”+s3Config.getBucketName();
> producerTemplate.send(endpointUri, exchange);
>
> Reference of S3Config
>
> String awsBucketAccessKey = "your_access_key";
> String awsBucketSecretKey = "your_secret_key";
>
> //exposed as a @Bean(“s3”)
> AWS2S3Component s3 = new AWS2S3Component();
> s3.setConfiguration(getConfiguration());
> s3.setHealthCheckProducerEnabled(true);
> s3.setLazyStartProducer(true);
>
> //autowire and register the bean
> camelContext.addComponent(“aws2-s3”, s3);
>
>
> getConfiguration() method
> AWS2S3Configuration configuration = new AWS2S3Configuration();
>
> S3Client s3Client =
> S3Client.builder().credentialsProvider(StaticCredentialsProvider.create(AwsBasicCredentials.create(awsBucketAccessKey,
> awsBucketSecretKey)))
> .region(Region.US_EAST_1).build();
>
> configuration.setAmazonS3Client(s3Client);
> configuration.setAutoDiscoverClient(true); -• I cannot find this property
> in camel-aws 4.5.0
> configuration.setBucketName("s3bucket2020");
> configuration.setRegion("us-east-1");
>
>
> From the application SSL DEBUG logs, I see problems in establishing
> connection
>
>   1.  Connecting socket to AMAZON S3 HOSTNAME
>   2.  Enabled Protocols
>   3.  Enabled cipher suites
>   4.  Starting handshake
>   5.  Shutdown connection
>   6.  Connection discarded
>
> Is there any SSL Configuration that I must set at the configuration level,
> I am confused now since I am already passing the credentials. What am I
> missing here ?
>
> -Regards
> Srikant Mantha
>

Camel AWS2-S3 Unable to find valid certification path to the requested target”

[Srikant Mantha]

Hi,
I am using camel aws s3 to upload a file in my camel-springboot microservice 
with camel aws version as 4.5.0. I am facing connectivity issues to the S3 
bucket with the

exception message like “unable to find valid certification path to the 
requested target”

Below is my config and endpoint call

My Camel Processor code

//set the payload in the exchange body and the S3 url is constructed in the 
S3Config
String endpointUri = “s3://”+s3Config.getBucketName();
producerTemplate.send(endpointUri, exchange);

Reference of S3Config

String awsBucketAccessKey = "your_access_key";
String awsBucketSecretKey = "your_secret_key";

//exposed as a @Bean(“s3”)
AWS2S3Component s3 = new AWS2S3Component();
s3.setConfiguration(getConfiguration());
s3.setHealthCheckProducerEnabled(true);
s3.setLazyStartProducer(true);

//autowire and register the bean
camelContext.addComponent(“aws2-s3”, s3);


getConfiguration() method
AWS2S3Configuration configuration = new AWS2S3Configuration();

S3Client s3Client = 
S3Client.builder().credentialsProvider(StaticCredentialsProvider.create(AwsBasicCredentials.create(awsBucketAccessKey,
 awsBucketSecretKey)))
.region(Region.US_EAST_1).build();

configuration.setAmazonS3Client(s3Client);
configuration.setAutoDiscoverClient(true); -• I cannot find this property in 
camel-aws 4.5.0
configuration.setBucketName("s3bucket2020");
configuration.setRegion("us-east-1");


From the application SSL DEBUG logs, I see problems in establishing connection

  1.  Connecting socket to AMAZON S3 HOSTNAME
  2.  Enabled Protocols
  3.  Enabled cipher suites
  4.  Starting handshake
  5.  Shutdown connection
  6.  Connection discarded

Is there any SSL Configuration that I must set at the configuration level, I am 
confused now since I am already passing the credentials. What am I missing here 
?

-Regards
Srikant Mantha

RE: Route stop with long running processor

[Jan Bares, WOOD & Co.]

Many thanks, this is what I was looking for. Jan

> -Original Message-
> From: Claus Ibsen 
> Sent: Tuesday, July 2, 2024 11:24 AM
> To: users@camel.apache.org
> Subject: Re: Route stop with long running processor
>
> Hi
>
> Try implement ShutdownPrepared
>
> On Tue, Jul 2, 2024 at 11:07 AM Jan Bares, WOOD & Co.
>  wrote:
>
> > Hi,
> >
> > We have a processor that takes long time to finish processing (tenths of
> > seconds) each exchange. Is there a way the processor can tell the route is
> > about to be stopped and finish the processing immediately? It seems that
> > the doStop is called only after all the processing is finished. In the
> > processor we have a loop and we can break the loop when we know that the
> > route is about to be stopped.
> >
> > Thanks, Jan
> >
> > Jan Bares
> > Head of Calypso development | IT Development
> >
> > Phone: +420 222 096 457
> > Mobile: +420 776 333 676
> > Email: jan.ba...@wood.cz
> >
> > WOOD & Company
> > Palladium, n?m. Republiky 1079/1a, 110 00 Prague 1, Czech Republic |
> > wood.cz
> >
> >
> >
> >
> >
> > 
> > DISCLAIMER
> > WOOD & Company Financial Services, a.s. and its branches are authorized
> > and regulated by the CNB as Home State regulator and in Poland by the KNF,
> > in Slovakia by the NBS, in Italy by the CONSOB and in the UK by the FCA as
> > Host State regulators. For further information about WOOD & Co., its
> > investment services, financial instruments and associated risks, safeguard
> > client assets (incl. compensation schemes) and contractual relationship
> > please see our website at www.wood.com under
> > section Corporate Governance. Unless otherwise stated, this transmission is
> > neither an offer nor the solicitation of an offer to sell or purchase any
> > investment. All estimates, opinions and other information contained herein
> > are subject to change without notice and are provided in good faith but
> > without legal responsibility or liability. Opinion may be personal to the
> > author and may not reflect the opinions of WOOD & Co. Communications from
> > sales persons, sales traders or traders should not be regarded as
> > investment research and may contain opinions or trading ideas which are
> > different from WOOD & Co. investment research opinions. This e-mail and any
> > attachments are confidential and may be privileged or otherwise protected
> > from disclosure. If you are not a named addressee you must not use,
> > disclose, distribute, copy, print or rely on this e-mail and any of its
> > attachments. Please notify the sender that you have received this email by
> > mistake by replying to the email, and then delete the email and any copies
> > of it. Although WOOD & Co. routinely screens e-mails for viruses,
> > addressees should scan this e-mail and any attachments for viruses. WOOD &
> > Co. makes no representation or warranty as to the absence of viruses in
> > this e-mail or any attachments. Please note that to ensure regulatory
> > compliance and for the protection of our clients and business, we may
> > monitor and read e-mails sent to and from our server(s).
> >
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2

Jan Bares
Head of Calypso development | IT Development

Phone: +420 222 096 457
Mobile: +420 776 333 676
Email: jan.ba...@wood.cz

WOOD & Company
Palladium, nám. Republiky 1079/1a, 110 00 Prague 1, Czech Republic | wood.cz






DISCLAIMER
WOOD & Company Financial Services, a.s. and its branches are authorized and 
regulated by the CNB as Home State regulator and in Poland by the KNF, in 
Slovakia by the NBS, in Italy by the CONSOB and in the UK by the FCA as Host 
State regulators. For further information about WOOD & Co., its investment 
services, financial instruments and associated risks, safeguard client assets 
(incl. compensation schemes) and contractual relationship please see our 
website at www.wood.com under section Corporate 
Governance. Unless otherwise stated, this transmission is neither an offer nor 
the solicitation of an offer to sell or purchase any investment. All estimates, 
opinions and other information contained herein are subject to change without 
notice and are provided in good faith but without legal responsibility or 
liability. Opinion may be personal to the author and may not reflect the 
opinions of WOOD & Co. Communications from sales persons, sales traders or 
traders should not be regarded as investment research and may contain opinions 
or trading ideas which are different from WOOD & Co. investment research 
opinions. This e-mail and any attachments are confidential and may be 
privileged or otherwise protected from disclosure. If you are not a named 
addressee you must not use, disclose, distribute, copy, print or rely on this 
e-mail and any of its attachments. Please notify the sender that you 

Re: Route stop with long running processor

[Claus Ibsen]

Hi

Try implement ShutdownPrepared

On Tue, Jul 2, 2024 at 11:07 AM Jan Bares, WOOD & Co.
 wrote:

> Hi,
>
> We have a processor that takes long time to finish processing (tenths of
> seconds) each exchange. Is there a way the processor can tell the route is
> about to be stopped and finish the processing immediately? It seems that
> the doStop is called only after all the processing is finished. In the
> processor we have a loop and we can break the loop when we know that the
> route is about to be stopped.
>
> Thanks, Jan
>
> Jan Bares
> Head of Calypso development | IT Development
>
> Phone: +420 222 096 457
> Mobile: +420 776 333 676
> Email: jan.ba...@wood.cz
>
> WOOD & Company
> Palladium, n?m. Republiky 1079/1a, 110 00 Prague 1, Czech Republic |
> wood.cz
>
>
>
>
>
> 
> DISCLAIMER
> WOOD & Company Financial Services, a.s. and its branches are authorized
> and regulated by the CNB as Home State regulator and in Poland by the KNF,
> in Slovakia by the NBS, in Italy by the CONSOB and in the UK by the FCA as
> Host State regulators. For further information about WOOD & Co., its
> investment services, financial instruments and associated risks, safeguard
> client assets (incl. compensation schemes) and contractual relationship
> please see our website at www.wood.com under
> section Corporate Governance. Unless otherwise stated, this transmission is
> neither an offer nor the solicitation of an offer to sell or purchase any
> investment. All estimates, opinions and other information contained herein
> are subject to change without notice and are provided in good faith but
> without legal responsibility or liability. Opinion may be personal to the
> author and may not reflect the opinions of WOOD & Co. Communications from
> sales persons, sales traders or traders should not be regarded as
> investment research and may contain opinions or trading ideas which are
> different from WOOD & Co. investment research opinions. This e-mail and any
> attachments are confidential and may be privileged or otherwise protected
> from disclosure. If you are not a named addressee you must not use,
> disclose, distribute, copy, print or rely on this e-mail and any of its
> attachments. Please notify the sender that you have received this email by
> mistake by replying to the email, and then delete the email and any copies
> of it. Although WOOD & Co. routinely screens e-mails for viruses,
> addressees should scan this e-mail and any attachments for viruses. WOOD &
> Co. makes no representation or warranty as to the absence of viruses in
> this e-mail or any attachments. Please note that to ensure regulatory
> compliance and for the protection of our clients and business, we may
> monitor and read e-mails sent to and from our server(s).
>


-- 
Claus Ibsen
-
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Route stop with long running processor

[Jan Bares, WOOD & Co.]

Hi,

We have a processor that takes long time to finish processing (tenths of 
seconds) each exchange. Is there a way the processor can tell the route is 
about to be stopped and finish the processing immediately? It seems that the 
doStop is called only after all the processing is finished. In the processor we 
have a loop and we can break the loop when we know that the route is about to 
be stopped.

Thanks, Jan

Jan Bares
Head of Calypso development | IT Development

Phone: +420 222 096 457
Mobile: +420 776 333 676
Email: jan.ba...@wood.cz

WOOD & Company
Palladium, n?m. Republiky 1079/1a, 110 00 Prague 1, Czech Republic | wood.cz






DISCLAIMER
WOOD & Company Financial Services, a.s. and its branches are authorized and 
regulated by the CNB as Home State regulator and in Poland by the KNF, in 
Slovakia by the NBS, in Italy by the CONSOB and in the UK by the FCA as Host 
State regulators. For further information about WOOD & Co., its investment 
services, financial instruments and associated risks, safeguard client assets 
(incl. compensation schemes) and contractual relationship please see our 
website at www.wood.com under section Corporate 
Governance. Unless otherwise stated, this transmission is neither an offer nor 
the solicitation of an offer to sell or purchase any investment. All estimates, 
opinions and other information contained herein are subject to change without 
notice and are provided in good faith but without legal responsibility or 
liability. Opinion may be personal to the author and may not reflect the 
opinions of WOOD & Co. Communications from sales persons, sales traders or 
traders should not be regarded as investment research and may contain opinions 
or trading ideas which are different from WOOD & Co. investment research 
opinions. This e-mail and any attachments are confidential and may be 
privileged or otherwise protected from disclosure. If you are not a named 
addressee you must not use, disclose, distribute, copy, print or rely on this 
e-mail and any of its attachments. Please notify the sender that you have 
received this email by mistake by replying to the email, and then delete the 
email and any copies of it. Although WOOD & Co. routinely screens e-mails for 
viruses, addressees should scan this e-mail and any attachments for viruses. 
WOOD & Co. makes no representation or warranty as to the absence of viruses in 
this e-mail or any attachments. Please note that to ensure regulatory 
compliance and for the protection of our clients and business, we may monitor 
and read e-mails sent to and from our server(s).

Re: [VOTE] Release Apache Camel Kamelets 4.4.3

[Claudio Miranda]

+1 (non-bindnig)

Em seg., 1 de jul. de 2024 às 08:59, Andrea Cosentino
 escreveu:
>
> Hello all,
>
> This is a vote for releasing camel-kamelets 4.4.3
>
> This is a release supporting Camel 4.4.3 and it's an LTS release.
>
> Kamelets release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.4.3
> Kamelets staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1726
> Kamelets Tag:
> https://github.com/apache/camel-kamelets/releases/tag/v4.4.3
>
> Please cast your vote.
>
> [ ] +1 Release camel-kamelets 4.4.3
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Here's my +1.
>
> Thanks,
> Andrea Cosentino



-- 
  Claudio Miranda

clau...@claudius.com.br
http://www.claudius.com.br

Re: [VOTE] Release Apache Camel Kamelets 4.4.3

[Otavio Rodolfo Piske]

+1 (binding)

Thanks Andrea!

On Mon, Jul 1, 2024 at 10:21 AM Claus Ibsen  wrote:

> +1 (binding)
>
> On Mon, Jul 1, 2024 at 9:59 AM Andrea Cosentino  wrote:
>
> > Hello all,
> >
> > This is a vote for releasing camel-kamelets 4.4.3
> >
> > This is a release supporting Camel 4.4.3 and it's an LTS release.
> >
> > Kamelets release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.4.3
> > Kamelets staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1726
> > Kamelets Tag:
> > https://github.com/apache/camel-kamelets/releases/tag/v4.4.3
> >
> > Please cast your vote.
> >
> > [ ] +1 Release camel-kamelets 4.4.3
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Here's my +1.
> >
> > Thanks,
> > Andrea Cosentino
> >
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release Apache Camel Kamelets 4.4.3

[Claus Ibsen]

+1 (binding)

On Mon, Jul 1, 2024 at 9:59 AM Andrea Cosentino  wrote:

> Hello all,
>
> This is a vote for releasing camel-kamelets 4.4.3
>
> This is a release supporting Camel 4.4.3 and it's an LTS release.
>
> Kamelets release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.4.3
> Kamelets staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1726
> Kamelets Tag:
> https://github.com/apache/camel-kamelets/releases/tag/v4.4.3
>
> Please cast your vote.
>
> [ ] +1 Release camel-kamelets 4.4.3
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Here's my +1.
>
> Thanks,
> Andrea Cosentino
>


-- 
Claus Ibsen
-
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: [VOTE] Release Apache Camel Kamelets 4.4.3

[Zineb Bendhiba]

+1 (binding)

Thanks Andrea

Le lun. 1 juil. 2024 à 09:59, Andrea Cosentino  a écrit :

> Hello all,
>
> This is a vote for releasing camel-kamelets 4.4.3
>
> This is a release supporting Camel 4.4.3 and it's an LTS release.
>
> Kamelets release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.4.3
> Kamelets staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1726
> Kamelets Tag:
> https://github.com/apache/camel-kamelets/releases/tag/v4.4.3
>
> Please cast your vote.
>
> [ ] +1 Release camel-kamelets 4.4.3
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Here's my +1.
>
> Thanks,
> Andrea Cosentino
>


-- 
Zineb Bendhiba

[VOTE] Release Apache Camel Kamelets 4.4.3

[Andrea Cosentino]

Hello all,

This is a vote for releasing camel-kamelets 4.4.3

This is a release supporting Camel 4.4.3 and it's an LTS release.

Kamelets release files:
https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.4.3
Kamelets staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1726
Kamelets Tag:
https://github.com/apache/camel-kamelets/releases/tag/v4.4.3

Please cast your vote.

[ ] +1 Release camel-kamelets 4.4.3
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

Here's my +1.

Thanks,
Andrea Cosentino

[ANNOUNCE] Apache Camel 4.4.3 (LTS) Released

[Gregor Zurowski]

The Camel PMC is pleased to announce the release of Apache Camel 4.4.3 (LTS).

Apache Camel is an open source integration framework that empowers you
to quickly and easily integrate various systems consuming or producing
data.

This release contains 31 new features and improvements.

The release is available for immediate download at:

https://camel.apache.org/download/

For more details please take a look at the release notes at:

https://camel.apache.org/releases/release-4.4.3/

Re: how to set different path for the different Knative endpoint in Camel K

[Pasquale Congiusti]

Thanks for testing with latest versions.
Please, open a gtihub issue in the Camel K project repository [1] so we can
triage and possibly fix the problem.

Thanks and regards,
Pasquale.

[1] https://github.com/apache/camel-k

On Wed, Jun 26, 2024 at 7:45 AM _ Jane  wrote:

> I tested the case on Camel K 2.2 and got the same result.
>
> multiple-endpoint.groovy
> // camel-k: language=groovy
>
> from('knative:endpoint/test1')
>.log('Trigger from endpoint test1')
>.setBody().constant('Success test123')
>
> from('knative:endpoint/test2')
>.log('Trigger from endpoint test2')
>.setBody().constant('Success test246')
>
> Command:
> $ kamel run --profile Knative multiple-endpoint.groovy
>
> Result:
> CAMEL_KNATIVE_CONFIGURATION:
>
> {"services":[{"type":"endpoint","name":"test1","path":"/","metadata":{"camel.endpoint.kind":"source","knative.apiVersion":"
> serving.knative.dev/v1
> ","knative.kind":"Service"}},{"type":"endpoint","name":"test2","path":"/","metadata":{"camel.endpoint.kind":"source","knative.apiVersion":"
> serving.knative.dev/v1","knative.kind":"Service"}}]}
>
> My expectation:
> CAMEL_KNATIVE_CONFIGURATION:
>
> {"services":[{"type":"endpoint","name":"test1","path":"/test1","metadata":{"camel.endpoint.kind":"source","knative.apiVersion":"
> serving.knative.dev/v1
> ","knative.kind":"Service"}},{"type":"endpoint","name":"test2","path":"/test2","metadata":{"camel.endpoint.kind":"source","knative.apiVersion":"
> serving.knative.dev/v1","knative.kind":"Service"}}]}
>
> 
> 发件人: Pasquale Congiusti 
> 发送时间: 2024年6月25日 17:28
> 收件人: users@camel.apache.org 
> 主题: Re: how to set different path for the different Knative endpoint in
> Camel K
>
> Version 1.10 is very old (2 years or the like). We are not supporting since
> long time already.
>
> The suggestion is to move to version 2.3 which is the latest supporting
> Camel LTS. Mind that, although running this Camel K version, you can still
> use any runtime of version 1.x >= 1.17 (which is the default version used
> in Camel K 1.12).
>
> Cheers,
> Pasquale.
>
> On Tue, Jun 25, 2024 at 10:39 AM _ Jane  wrote:
>
> > Hi Pasquale,
> >
> > Thanks for your reply!
> >
> > I'm using Camel K 1.10. And I hope to find a way to achieve it without
> > upgrading the Camel K version, such as using Camel properties or Camel K
> > trait. I've tried to use below Camel k trait but failed.
> >
> > $ kamel run --name multi-endpoint --profile Knative --trait
> >
> knative.configuration='{"services":[{"type":"endpoint","name":"test1","path":"/test1","metadata"
> > :{"camel.endpoint.kind":"source","knative.apiVersion":"
> > serving.knative.dev/v1
> >
> ","knative.kind":"Service"}},{"type":"endpoint","name":"test2","path":"/test2","metadata":{"camel.endpoint.kind":"source","knative.apiVersion":"serving
> > .knative.dev/v1","knative.kind":"Service"}}]}' MultiEndpointRoute.java
> >
> > Error: 1 error(s) decoding:
> >
> > * 'knative.Configuration' expected a map, got 'string'
> >
> > Is there any good idea?
> > 
> > 发件人: Pasquale Congiusti 
> > 发送时间: 2024年6月24日 17:30
> > 收件人: users@camel.apache.org 
> > 主题: Re: how to set different path for the different Knative endpoint in
> > Camel K
> >
> > Hello there.
> > What version of Camel K are you using? In the most recent versions we
> have
> > changed the way this is configured, and it's possible this issue got
> > solved. Can you try running the same with the latest stable releases?
> >
> > Thanks,
> > Pasquale.
> >
> > On Mon, Jun 24, 2024 at 10:04 AM _ Jane  wrote:
> >
> > > Dear Community,
> > >
> > > I want to define 2 routes with Knative endpoint consumer as below:
> > >
> > >
> > > from("knative:endpoint/test1")
> > > .routeId("route_inbound_knative1")
> > > .log("Trigger from test1 endpoint")
> > > .setBody(constant("Success test1"));
> > >
> > > from("knative:endpoint/test2")
> > > .routeId("route_inbound_knative2")
> > > .log("Trigger from test2 endpoint")
> > > .setBody(constant("Success test2"));
> > >
> > > After deploy it with "kamel run" command, the auto-generated
> > > CAMEL_KNATIVE_CONFIGURATION is as below:
> > >
> > >
> > >
> >
> {"services":[{"type":"endpoint","name":"test1","path":"/","metadata":{"camel.endpoint.kind":"source","knative.apiVersion":"
> > > serving.knative.dev/v1
> > >
> >
> ","knative.kind":"Service"}},{"type":"endpoint","name":"test2","path":"/","metadata":{"camel.endpoint.kind":"source","knative.apiVersion":"
> > > serving.knative.dev/v1","knative.kind":"Service"}}]}
> > >
> > > How can I set different path for these 2 Knative endpoint like "/test1"
> > > and "/test2"?
> > >
> > > Thanks!
> > >
> > >
> >
>

回复: how to set different path for the different Knative endpoint in Camel K

[_ Jane]

I tested the case on Camel K 2.2 and got the same result.

multiple-endpoint.groovy
// camel-k: language=groovy

from('knative:endpoint/test1')
   .log('Trigger from endpoint test1')
   .setBody().constant('Success test123')

from('knative:endpoint/test2')
   .log('Trigger from endpoint test2')
   .setBody().constant('Success test246')

Command:
$ kamel run --profile Knative multiple-endpoint.groovy

Result:
CAMEL_KNATIVE_CONFIGURATION:
{"services":[{"type":"endpoint","name":"test1","path":"/","metadata":{"camel.endpoint.kind":"source","knative.apiVersion":"serving.knative.dev/v1","knative.kind":"Service"}},{"type":"endpoint","name":"test2","path":"/","metadata":{"camel.endpoint.kind":"source","knative.apiVersion":"serving.knative.dev/v1","knative.kind":"Service"}}]}

My expectation:
CAMEL_KNATIVE_CONFIGURATION:
{"services":[{"type":"endpoint","name":"test1","path":"/test1","metadata":{"camel.endpoint.kind":"source","knative.apiVersion":"serving.knative.dev/v1","knative.kind":"Service"}},{"type":"endpoint","name":"test2","path":"/test2","metadata":{"camel.endpoint.kind":"source","knative.apiVersion":"serving.knative.dev/v1","knative.kind":"Service"}}]}


发件人: Pasquale Congiusti 
发送时间: 2024年6月25日 17:28
收件人: users@camel.apache.org 
主题: Re: how to set different path for the different Knative endpoint in Camel K

Version 1.10 is very old (2 years or the like). We are not supporting since
long time already.

The suggestion is to move to version 2.3 which is the latest supporting
Camel LTS. Mind that, although running this Camel K version, you can still
use any runtime of version 1.x >= 1.17 (which is the default version used
in Camel K 1.12).

Cheers,
Pasquale.

On Tue, Jun 25, 2024 at 10:39 AM _ Jane  wrote:

> Hi Pasquale,
>
> Thanks for your reply!
>
> I'm using Camel K 1.10. And I hope to find a way to achieve it without
> upgrading the Camel K version, such as using Camel properties or Camel K
> trait. I've tried to use below Camel k trait but failed.
>
> $ kamel run --name multi-endpoint --profile Knative --trait
> knative.configuration='{"services":[{"type":"endpoint","name":"test1","path":"/test1","metadata"
> :{"camel.endpoint.kind":"source","knative.apiVersion":"
> serving.knative.dev/v1
> ","knative.kind":"Service"}},{"type":"endpoint","name":"test2","path":"/test2","metadata":{"camel.endpoint.kind":"source","knative.apiVersion":"serving
> .knative.dev/v1","knative.kind":"Service"}}]}' MultiEndpointRoute.java
>
> Error: 1 error(s) decoding:
>
> * 'knative.Configuration' expected a map, got 'string'
>
> Is there any good idea?
> 
> 发件人: Pasquale Congiusti 
> 发送时间: 2024年6月24日 17:30
> 收件人: users@camel.apache.org 
> 主题: Re: how to set different path for the different Knative endpoint in
> Camel K
>
> Hello there.
> What version of Camel K are you using? In the most recent versions we have
> changed the way this is configured, and it's possible this issue got
> solved. Can you try running the same with the latest stable releases?
>
> Thanks,
> Pasquale.
>
> On Mon, Jun 24, 2024 at 10:04 AM _ Jane  wrote:
>
> > Dear Community,
> >
> > I want to define 2 routes with Knative endpoint consumer as below:
> >
> >
> > from("knative:endpoint/test1")
> > .routeId("route_inbound_knative1")
> > .log("Trigger from test1 endpoint")
> > .setBody(constant("Success test1"));
> >
> > from("knative:endpoint/test2")
> > .routeId("route_inbound_knative2")
> > .log("Trigger from test2 endpoint")
> > .setBody(constant("Success test2"));
> >
> > After deploy it with "kamel run" command, the auto-generated
> > CAMEL_KNATIVE_CONFIGURATION is as below:
> >
> >
> >
> {"services":[{"type":"endpoint","name":"test1","path":"/","metadata":{"camel.endpoint.kind":"source","knative.apiVersion":"
> > serving.knative.dev/v1
> >
> ","knative.kind":"Service"}},{"type":"endpoint","name":"test2","path":"/","metadata":{"camel.endpoint.kind":"source","knative.apiVersion":"
> > serving.knative.dev/v1","knative.kind":"Service"}}]}
> >
> > How can I set different path for these 2 Knative endpoint like "/test1"
> > and "/test2"?
> >
> > Thanks!
> >
> >
>

Re: how to set different path for the different Knative endpoint in Camel K

[Pasquale Congiusti]

Version 1.10 is very old (2 years or the like). We are not supporting since
long time already.

The suggestion is to move to version 2.3 which is the latest supporting
Camel LTS. Mind that, although running this Camel K version, you can still
use any runtime of version 1.x >= 1.17 (which is the default version used
in Camel K 1.12).

Cheers,
Pasquale.

On Tue, Jun 25, 2024 at 10:39 AM _ Jane  wrote:

> Hi Pasquale,
>
> Thanks for your reply!
>
> I'm using Camel K 1.10. And I hope to find a way to achieve it without
> upgrading the Camel K version, such as using Camel properties or Camel K
> trait. I've tried to use below Camel k trait but failed.
>
> $ kamel run --name multi-endpoint --profile Knative --trait
> knative.configuration='{"services":[{"type":"endpoint","name":"test1","path":"/test1","metadata"
> :{"camel.endpoint.kind":"source","knative.apiVersion":"
> serving.knative.dev/v1
> ","knative.kind":"Service"}},{"type":"endpoint","name":"test2","path":"/test2","metadata":{"camel.endpoint.kind":"source","knative.apiVersion":"serving
> .knative.dev/v1","knative.kind":"Service"}}]}' MultiEndpointRoute.java
>
> Error: 1 error(s) decoding:
>
> * 'knative.Configuration' expected a map, got 'string'
>
> Is there any good idea?
> 
> 发件人: Pasquale Congiusti 
> 发送时间: 2024年6月24日 17:30
> 收件人: users@camel.apache.org 
> 主题: Re: how to set different path for the different Knative endpoint in
> Camel K
>
> Hello there.
> What version of Camel K are you using? In the most recent versions we have
> changed the way this is configured, and it's possible this issue got
> solved. Can you try running the same with the latest stable releases?
>
> Thanks,
> Pasquale.
>
> On Mon, Jun 24, 2024 at 10:04 AM _ Jane  wrote:
>
> > Dear Community,
> >
> > I want to define 2 routes with Knative endpoint consumer as below:
> >
> >
> > from("knative:endpoint/test1")
> > .routeId("route_inbound_knative1")
> > .log("Trigger from test1 endpoint")
> > .setBody(constant("Success test1"));
> >
> > from("knative:endpoint/test2")
> > .routeId("route_inbound_knative2")
> > .log("Trigger from test2 endpoint")
> > .setBody(constant("Success test2"));
> >
> > After deploy it with "kamel run" command, the auto-generated
> > CAMEL_KNATIVE_CONFIGURATION is as below:
> >
> >
> >
> {"services":[{"type":"endpoint","name":"test1","path":"/","metadata":{"camel.endpoint.kind":"source","knative.apiVersion":"
> > serving.knative.dev/v1
> >
> ","knative.kind":"Service"}},{"type":"endpoint","name":"test2","path":"/","metadata":{"camel.endpoint.kind":"source","knative.apiVersion":"
> > serving.knative.dev/v1","knative.kind":"Service"}}]}
> >
> > How can I set different path for these 2 Knative endpoint like "/test1"
> > and "/test2"?
> >
> > Thanks!
> >
> >
>

回复: how to set different path for the different Knative endpoint in Camel K

[_ Jane]

Hi Pasquale,

Thanks for your reply!

I'm using Camel K 1.10. And I hope to find a way to achieve it without 
upgrading the Camel K version, such as using Camel properties or Camel K trait. 
I've tried to use below Camel k trait but failed.

$ kamel run --name multi-endpoint --profile Knative --trait 
knative.configuration='{"services":[{"type":"endpoint","name":"test1","path":"/test1","metadata"
:{"camel.endpoint.kind":"source","knative.apiVersion":"serving.knative.dev/v1","knative.kind":"Service"}},{"type":"endpoint","name":"test2","path":"/test2","metadata":{"camel.endpoint.kind":"source","knative.apiVersion":"serving
.knative.dev/v1","knative.kind":"Service"}}]}' MultiEndpointRoute.java

Error: 1 error(s) decoding:

* 'knative.Configuration' expected a map, got 'string'

Is there any good idea?

发件人: Pasquale Congiusti 
发送时间: 2024年6月24日 17:30
收件人: users@camel.apache.org 
主题: Re: how to set different path for the different Knative endpoint in Camel K

Hello there.
What version of Camel K are you using? In the most recent versions we have
changed the way this is configured, and it's possible this issue got
solved. Can you try running the same with the latest stable releases?

Thanks,
Pasquale.

On Mon, Jun 24, 2024 at 10:04 AM _ Jane  wrote:

> Dear Community,
>
> I want to define 2 routes with Knative endpoint consumer as below:
>
>
> from("knative:endpoint/test1")
> .routeId("route_inbound_knative1")
> .log("Trigger from test1 endpoint")
> .setBody(constant("Success test1"));
>
> from("knative:endpoint/test2")
> .routeId("route_inbound_knative2")
> .log("Trigger from test2 endpoint")
> .setBody(constant("Success test2"));
>
> After deploy it with "kamel run" command, the auto-generated
> CAMEL_KNATIVE_CONFIGURATION is as below:
>
>
> {"services":[{"type":"endpoint","name":"test1","path":"/","metadata":{"camel.endpoint.kind":"source","knative.apiVersion":"
> serving.knative.dev/v1
> ","knative.kind":"Service"}},{"type":"endpoint","name":"test2","path":"/","metadata":{"camel.endpoint.kind":"source","knative.apiVersion":"
> serving.knative.dev/v1","knative.kind":"Service"}}]}
>
> How can I set different path for these 2 Knative endpoint like "/test1"
> and "/test2"?
>
> Thanks!
>
>

Re: how to set different path for the different Knative endpoint in Camel K

[Pasquale Congiusti]

Hello there.
What version of Camel K are you using? In the most recent versions we have
changed the way this is configured, and it's possible this issue got
solved. Can you try running the same with the latest stable releases?

Thanks,
Pasquale.

On Mon, Jun 24, 2024 at 10:04 AM _ Jane  wrote:

> Dear Community,
>
> I want to define 2 routes with Knative endpoint consumer as below:
>
>
> from("knative:endpoint/test1")
> .routeId("route_inbound_knative1")
> .log("Trigger from test1 endpoint")
> .setBody(constant("Success test1"));
>
> from("knative:endpoint/test2")
> .routeId("route_inbound_knative2")
> .log("Trigger from test2 endpoint")
> .setBody(constant("Success test2"));
>
> After deploy it with "kamel run" command, the auto-generated
> CAMEL_KNATIVE_CONFIGURATION is as below:
>
>
> {"services":[{"type":"endpoint","name":"test1","path":"/","metadata":{"camel.endpoint.kind":"source","knative.apiVersion":"
> serving.knative.dev/v1
> ","knative.kind":"Service"}},{"type":"endpoint","name":"test2","path":"/","metadata":{"camel.endpoint.kind":"source","knative.apiVersion":"
> serving.knative.dev/v1","knative.kind":"Service"}}]}
>
> How can I set different path for these 2 Knative endpoint like "/test1"
> and "/test2"?
>
> Thanks!
>
>

how to set different path for the different Knative endpoint in Camel K

[_ Jane]

Dear Community,

I want to define 2 routes with Knative endpoint consumer as below:


from("knative:endpoint/test1")
.routeId("route_inbound_knative1")
.log("Trigger from test1 endpoint")
.setBody(constant("Success test1"));

from("knative:endpoint/test2")
.routeId("route_inbound_knative2")
.log("Trigger from test2 endpoint")
.setBody(constant("Success test2"));

After deploy it with "kamel run" command, the auto-generated 
CAMEL_KNATIVE_CONFIGURATION is as below:

{"services":[{"type":"endpoint","name":"test1","path":"/","metadata":{"camel.endpoint.kind":"source","knative.apiVersion":"serving.knative.dev/v1","knative.kind":"Service"}},{"type":"endpoint","name":"test2","path":"/","metadata":{"camel.endpoint.kind":"source","knative.apiVersion":"serving.knative.dev/v1","knative.kind":"Service"}}]}

How can I set different path for these 2 Knative endpoint like "/test1" and 
"/test2"?

Thanks!

[ANNOUNCE] Apache Camel 3.21.5 (LTS) Released

[Gregor Zurowski]

The Camel PMC is pleased to announce the release of Apache Camel 3.21.5 (LTS).

Apache Camel is an open source integration framework that empowers you
to quickly and easily integrate various systems consuming or producing
data.

This release is a new patch release with 18 improvements and fixes.

It is available for immediate download at:

https://camel.apache.org/download/

For more details please take a look at the release notes at:

https://camel.apache.org/releases/release-3.21.5/

3 sur 44 Camel-HTTP disableStreamCache=true bug ?

[Ryan Ikhlef]

  Hello,

I'm facing a weird behavior on the Camel-HTTP component (4.2.2) when I want
to use the "disableStreamCache=true" configuration specified in this page :
https://camel.apache.org/components/4.4.x/http-component.html.
When this option is set to true, the stream is consumed first by the Apache
HTTP Client, and then, when Camel tries to convert the InputStream to
CacheOutputStream object by copying the data, it raises a
"StreamAlreadyClosed" exception.

I even tried to get the body in a processor, to convert it into another
object like String.class etc... So, I tried to go deeply in the code to
figure out this error. Please find below my analysis.

When I make an HTTP call, the execution goes through the
org.apache.hc.client5.http.impl.classic.CloseableHttpClient#execute(HttpHost,
ClassicHttpRequest, HttpContext, HttpClientResponseHandler) method. Here,
it calls the handler defined by Camel in
org.apache.camel.component.http.HttpProducer#process(Exchange) - line 248.
In this handler, because I set up the option "disableStreamCache=true" the
handler sets the exchange body as the InputStream provided by the HTTP
Client. So, when it goes back to the execute method, the Apache HTTP Client
consumes the stream (i.e ; he closes it).
This is where the problem starts. In the exchange, I have a closed stream
that can't be used inside my route. For example, if I try to log the body,
it raises the exception pasted below.

I also tried the run my app with the option :
"camel.springboot.stream-caching-enabled: false" in my application.yml but
the bug is caused before this option is valuated (in the HTTP Client) so,
it's not effective.

I don't really know if it's me who does not fully understand this option or
if it's a bug. I think, the HTTP Client expects the user to read the
response inside the handler given in the execute method, then, it can
safely close the InputStream. But, in the Camel case, the handler just put
the InputStream reference inside the exchange. Maybe, when the option
disableStreamCache is set to true, the final user of Camel should be able
to give his own handler's implementation in order to consume it in the way
we need?

Thanks in advance for your inputs.
Regards,

Steps to reproduce :

I noticed this bug by using Camel spring boot 4.2.2 but I think this bug is
reproducible without Spring Boot.

Here find my dependencies in my pom.xml :

 4.4.2



   
   org.springframework.boot
  spring-boot-starter
 

   
   org.apache.camel.springboot
  camel-spring-boot-starter
  ${camel.version}
 
 
   org.apache.camel.springboot
  camel-http-starter
  ${camel.version}
 

  
   org.slf4j
  slf4j-api
 

   
   org.springframework.boot
  spring-boot-starter-logging
 


Here my Main class :

@SpringBootApplication
public class Main {
public static void main(String[] args) {
SpringApplication.run(Main.class, args);
 }
}

and found my route here :

@Component
public class MyRoute extends RouteBuilder {

@Override
public void configure() throws Exception {
getContext().getTypeConverterRegistry();

//@formatter:off
from("timer:test?repeatCount=1")
.setHeader(Exchange.HTTP_METHOD, constant("GET"))
.setHeader(Exchange.HTTP_URI, constant("
https://camel.apache.org/components/4.4.x/http-component.html;))
.to("http:myHttpRequest?disableStreamCache=true")
.log("body : ${body}")
.end();
//@formatter:on
}
}

Find here the log I got after running this project :

org.apache.camel.StreamCacheException: Error during type conversion from
type: org.apache.hc.client5.http.entity.LazyDecompressingInputStream to the
required type: org.apache.camel.StreamCache with value
org.apache.hc.client5.http.entity.LazyDecompressingInputStream@2e74480e due
to org.apache.camel.TypeConversionException: Error during type conversion
from type: org.apache.hc.client5.http.entity.LazyDecompressingInputStream
to the required type: org.apache.camel.StreamCache with value
org.apache.hc.client5.http.entity.LazyDecompressingInputStream@2e74480e due
to java.io.IOException: Attempted read on closed stream.
at
org.apache.camel.impl.engine.StreamCachingHelper.handleException(StreamCachingHelper.java:86)
~[camel-base-engine-4.4.2.jar:4.4.2]
at
org.apache.camel.impl.engine.StreamCachingHelper.handleException(StreamCachingHelper.java:81)
~[camel-base-engine-4.4.2.jar:4.4.2]
at
org.apache.camel.impl.engine.StreamCachingHelper.tryStreamCache(StreamCachingHelper.java:74)
~[camel-base-engine-4.4.2.jar:4.4.2]
at
org.apache.camel.impl.engine.StreamCachingHelper.convertToStreamCache(StreamCachingHelper.java:55)
~[camel-base-engine-4.4.2.jar:4.4.2]
at
org.apache.camel.impl.engine.CamelInternalProcessor$StreamCachingAdvice.before(CamelInternalProcessor.java:1009)
~[camel-base-engine-4.4.2.jar:4.4.2]
at

In Poll Enrich EIP, get email attachments are empty

[Kangjian Zhang (contractor, iSoftStone)]

Hi All,

Let's say I need to wait for an event notification and then pull an attachments 
email like this:

Camel version 3.18.x

from("servlet://foo?servletName=MyServlet")
.loopDoWhile().simple("${exchangeProperty.CamelBatchComplete} 
== null || ${exchangeProperty.CamelBatchComplete} == false")

.pollEnrich("imaps://{{mail.server}}?session=#oAuthSession=false=true={{mail.sub.folder}}=true")
.process(exchange -> {
AttachmentMessage attachmentMessage = 
exchange.getIn(AttachmentMessage.class);
// Here attachments is null
Map attachments = 
attachmentMessage.getAttachments();
})
.end();

Same code, works fine in Camel 3.14.x but doesn't work in Camel 3.18.x.

After debugging, it was found that in Camel 3.16.x, the implementation of 
DefaultAttachmentMessage.java was upgraded.

The key point is the CamelAttachmentObjects property in the ExchangeProperty, 
which is placed in the Exchange property in version 3.14.x, and in the 
ExtendedExchange property in version 3.16.x, which results in the loss of the 
CamelAttachmentObjects property between different Exchange.

Details can be found in the link below line 274:
https://github.com/apache/camel/commit/0125a133a11cbdff57d459634bac276c10963387

I tried a solution as follows:

Camel version 3.18.x

from("servlet://foo?servletName=MyServlet")
.loopDoWhile().simple("${exchangeProperty.CamelBatchComplete} 
== null || ${exchangeProperty.CamelBatchComplete} == false")

.pollEnrich("imaps://{{mail.server}}?session=#oAuthSession=false=true={{mail.sub.folder}}=true",
((oldExchange, newExchange) -> {
// Deliver the attachment to the oldExchange

oldExchange.setIn(newExchange.getIn(AttachmentMessage.class));
return oldExchange;
}))
.process(exchange -> {
AttachmentMessage attachmentMessage = 
exchange.getIn(AttachmentMessage.class);

Map attachments = 
attachmentMessage.getAttachments();
})
.end();

The above can solve the problem of not being able to get attachments, but there 
will be other properties missing.
Can you help with this? If information is missing, please do not hesitate to 
contact.

Thanks
Kangjian.

RE: When exactly are the route "after processing" options such as file move done?

[Jan Bares, WOOD & Co.]

Many thanks, it helped to understand what we did wrong. Jan

> -Original Message-
> From: Claus Ibsen 
> Sent: Tuesday, June 18, 2024 12:18 PM
> To: users@camel.apache.org
> Subject: Re: When exactly are the route "after processing" options such as 
> file
> move done?
>
> On Tue, Jun 18, 2024 at 12:06 PM Jan Bares, WOOD & Co.
>  wrote:
>
> > Yes, thanks. And does the rename happen on the first to() in the route or
> > on the last one?
> >
> >
> when the exchange from the original route is done being routed at the end
>
>
> > Jan
> >
> > > -Original Message-
> > > From: Claus Ibsen 
> > > Sent: Tuesday, June 18, 2024 11:52 AM
> > > To: users@camel.apache.org
> > > Subject: Re: When exactly are the route "after processing" options such
> > as file
> > > move done?
> > >
> > > Its the original route that move/rename then file when its done, not the
> > > wiretaps
> > >
> > > On Tue, Jun 18, 2024 at 11:40 AM Jan Bares, WOOD & Co.
> > >  wrote:
> > >
> > > > Hi,
> > > >
> > > > Say I have a route that reads a file and after processing it moves the
> > > > file to another folder.
> > > >
> > > >
> > > >
> > >
> >
> from("file:/mnt/folder/?include=input.txt=done/{date:now:MMddHHmms
> > > sSSS}.txt")
> > > > .process(...)
> > > > .wireTap("routeB")
> > > > .split(...)
> > > > .filter(...)
> > > > .to(...)
> > > > .wireTap("routeC")
> > > > .process(...)
> > > > .to(...)
> > > >
> > > > When exactly is the move operation done? As you can see I have
> > > > intermediate to() in my route and also two wireTap() that pass the
> > Exchange
> > > > to another route. The question is related to a problem when the
> > Exchange
> > > > still contains GenericFile but we have seen exception "file not found"
> > in a
> > > > wireTap route, because the file was already renamed.
> > > >
> > > > Thank you, Jan
> > > >
> > > > Jan Bares
> > > > Head of Calypso development | IT Development
> > > >
> > > > Phone: +420 222 096 457
> > > > Mobile: +420 776 333 676
> > > > Email: jan.ba...@wood.cz
> > > >
> > > > WOOD & Company
> > > > Palladium, n?m. Republiky 1079/1a, 110 00 Prague 1, Czech Republic |
> > > > wood.cz
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > 
> > > > DISCLAIMER
> > > > WOOD & Company Financial Services, a.s. and its branches are authorized
> > > > and regulated by the CNB as Home State regulator and in Poland by the
> > KNF,
> > > > in Slovakia by the NBS, in Italy by the CONSOB and in the UK by the
> > FCA as
> > > > Host State regulators. For further information about WOOD & Co., its
> > > > investment services, financial instruments and associated risks,
> > safeguard
> > > > client assets (incl. compensation schemes) and contractual relationship
> > > > please see our website at www.wood.com under
> > > > section Corporate Governance. Unless otherwise stated, this
> > transmission is
> > > > neither an offer nor the solicitation of an offer to sell or purchase
> > any
> > > > investment. All estimates, opinions and other information contained
> > herein
> > > > are subject to change without notice and are provided in good faith but
> > > > without legal responsibility or liability. Opinion may be personal to
> > the
> > > > author and may not reflect the opinions of WOOD & Co. Communications
> > from
> > > > sales persons, sales traders or traders should not be regarded as
> > > > investment research and may contain opinions or trading ideas which are
> > > > different from WOOD & Co. investment research opinions. This e-mail
> > and any
> > > > attachments are confidential and may be privileged or otherwise
> > protected
> > > > from disclosure. If you are not a named addressee you must not use,
> > > > disclose, distribute, copy, print or rely on this e-mail and any of its
> > > > attachments. Please notify the sender that you have received this
> > email by
> > > > mistake by replying to the email, and then delete the email and any
> > copies
> > > > of it. Although WOOD & Co. routinely screens e-mails for viruses,
> > > > addressees should scan this e-mail and any attachments for viruses.
> > WOOD &
> > > > Co. makes no representation or warranty as to the absence of viruses in
> > > > this e-mail or any attachments. Please note that to ensure regulatory
> > > > compliance and for the protection of our clients and business, we may
> > > > monitor and read e-mails sent to and from our server(s).
> > > >
> > >
> > >
> > > --
> > > Claus Ibsen
> > > -
> > > @davsclaus
> > > Camel in Action 2: https://www.manning.com/ibsen2
> >
> > Jan Bares
> > Head of Calypso development | IT Development
> >
> > Phone: +420 222 096 457
> > Mobile: +420 776 333 676
> > Email: jan.ba...@wood.cz
> >
> > WOOD & Company
> > Palladium, nám. Republiky 1079/1a, 110 00 Prague 1, Czech Republic |
> > wood.cz
> >
> >
> >
> >
> >
> > 
> > DISCLAIMER
> > WOOD & Company Financial 

Re: When exactly are the route "after processing" options such as file move done?

[Claus Ibsen]

On Tue, Jun 18, 2024 at 12:06 PM Jan Bares, WOOD & Co.
 wrote:

> Yes, thanks. And does the rename happen on the first to() in the route or
> on the last one?
>
>
when the exchange from the original route is done being routed at the end


> Jan
>
> > -Original Message-
> > From: Claus Ibsen 
> > Sent: Tuesday, June 18, 2024 11:52 AM
> > To: users@camel.apache.org
> > Subject: Re: When exactly are the route "after processing" options such
> as file
> > move done?
> >
> > Its the original route that move/rename then file when its done, not the
> > wiretaps
> >
> > On Tue, Jun 18, 2024 at 11:40 AM Jan Bares, WOOD & Co.
> >  wrote:
> >
> > > Hi,
> > >
> > > Say I have a route that reads a file and after processing it moves the
> > > file to another folder.
> > >
> > >
> > >
> >
> from("file:/mnt/folder/?include=input.txt=done/{date:now:MMddHHmms
> > sSSS}.txt")
> > > .process(...)
> > > .wireTap("routeB")
> > > .split(...)
> > > .filter(...)
> > > .to(...)
> > > .wireTap("routeC")
> > > .process(...)
> > > .to(...)
> > >
> > > When exactly is the move operation done? As you can see I have
> > > intermediate to() in my route and also two wireTap() that pass the
> Exchange
> > > to another route. The question is related to a problem when the
> Exchange
> > > still contains GenericFile but we have seen exception "file not found"
> in a
> > > wireTap route, because the file was already renamed.
> > >
> > > Thank you, Jan
> > >
> > > Jan Bares
> > > Head of Calypso development | IT Development
> > >
> > > Phone: +420 222 096 457
> > > Mobile: +420 776 333 676
> > > Email: jan.ba...@wood.cz
> > >
> > > WOOD & Company
> > > Palladium, n?m. Republiky 1079/1a, 110 00 Prague 1, Czech Republic |
> > > wood.cz
> > >
> > >
> > >
> > >
> > >
> > > 
> > > DISCLAIMER
> > > WOOD & Company Financial Services, a.s. and its branches are authorized
> > > and regulated by the CNB as Home State regulator and in Poland by the
> KNF,
> > > in Slovakia by the NBS, in Italy by the CONSOB and in the UK by the
> FCA as
> > > Host State regulators. For further information about WOOD & Co., its
> > > investment services, financial instruments and associated risks,
> safeguard
> > > client assets (incl. compensation schemes) and contractual relationship
> > > please see our website at www.wood.com under
> > > section Corporate Governance. Unless otherwise stated, this
> transmission is
> > > neither an offer nor the solicitation of an offer to sell or purchase
> any
> > > investment. All estimates, opinions and other information contained
> herein
> > > are subject to change without notice and are provided in good faith but
> > > without legal responsibility or liability. Opinion may be personal to
> the
> > > author and may not reflect the opinions of WOOD & Co. Communications
> from
> > > sales persons, sales traders or traders should not be regarded as
> > > investment research and may contain opinions or trading ideas which are
> > > different from WOOD & Co. investment research opinions. This e-mail
> and any
> > > attachments are confidential and may be privileged or otherwise
> protected
> > > from disclosure. If you are not a named addressee you must not use,
> > > disclose, distribute, copy, print or rely on this e-mail and any of its
> > > attachments. Please notify the sender that you have received this
> email by
> > > mistake by replying to the email, and then delete the email and any
> copies
> > > of it. Although WOOD & Co. routinely screens e-mails for viruses,
> > > addressees should scan this e-mail and any attachments for viruses.
> WOOD &
> > > Co. makes no representation or warranty as to the absence of viruses in
> > > this e-mail or any attachments. Please note that to ensure regulatory
> > > compliance and for the protection of our clients and business, we may
> > > monitor and read e-mails sent to and from our server(s).
> > >
> >
> >
> > --
> > Claus Ibsen
> > -
> > @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
>
> Jan Bares
> Head of Calypso development | IT Development
>
> Phone: +420 222 096 457
> Mobile: +420 776 333 676
> Email: jan.ba...@wood.cz
>
> WOOD & Company
> Palladium, nám. Republiky 1079/1a, 110 00 Prague 1, Czech Republic |
> wood.cz
>
>
>
>
>
> 
> DISCLAIMER
> WOOD & Company Financial Services, a.s. and its branches are authorized
> and regulated by the CNB as Home State regulator and in Poland by the KNF,
> in Slovakia by the NBS, in Italy by the CONSOB and in the UK by the FCA as
> Host State regulators. For further information about WOOD & Co., its
> investment services, financial instruments and associated risks, safeguard
> client assets (incl. compensation schemes) and contractual relationship
> please see our website at www.wood.com under
> section Corporate Governance. Unless otherwise stated, this transmission 

RE: When exactly are the route "after processing" options such as file move done?

[Jan Bares, WOOD & Co.]

Yes, thanks. And does the rename happen on the first to() in the route or on 
the last one?

Jan

> -Original Message-
> From: Claus Ibsen 
> Sent: Tuesday, June 18, 2024 11:52 AM
> To: users@camel.apache.org
> Subject: Re: When exactly are the route "after processing" options such as 
> file
> move done?
>
> Its the original route that move/rename then file when its done, not the
> wiretaps
>
> On Tue, Jun 18, 2024 at 11:40 AM Jan Bares, WOOD & Co.
>  wrote:
>
> > Hi,
> >
> > Say I have a route that reads a file and after processing it moves the
> > file to another folder.
> >
> >
> >
> from("file:/mnt/folder/?include=input.txt=done/{date:now:MMddHHmms
> sSSS}.txt")
> > .process(...)
> > .wireTap("routeB")
> > .split(...)
> > .filter(...)
> > .to(...)
> > .wireTap("routeC")
> > .process(...)
> > .to(...)
> >
> > When exactly is the move operation done? As you can see I have
> > intermediate to() in my route and also two wireTap() that pass the Exchange
> > to another route. The question is related to a problem when the Exchange
> > still contains GenericFile but we have seen exception "file not found" in a
> > wireTap route, because the file was already renamed.
> >
> > Thank you, Jan
> >
> > Jan Bares
> > Head of Calypso development | IT Development
> >
> > Phone: +420 222 096 457
> > Mobile: +420 776 333 676
> > Email: jan.ba...@wood.cz
> >
> > WOOD & Company
> > Palladium, n?m. Republiky 1079/1a, 110 00 Prague 1, Czech Republic |
> > wood.cz
> >
> >
> >
> >
> >
> > 
> > DISCLAIMER
> > WOOD & Company Financial Services, a.s. and its branches are authorized
> > and regulated by the CNB as Home State regulator and in Poland by the KNF,
> > in Slovakia by the NBS, in Italy by the CONSOB and in the UK by the FCA as
> > Host State regulators. For further information about WOOD & Co., its
> > investment services, financial instruments and associated risks, safeguard
> > client assets (incl. compensation schemes) and contractual relationship
> > please see our website at www.wood.com under
> > section Corporate Governance. Unless otherwise stated, this transmission is
> > neither an offer nor the solicitation of an offer to sell or purchase any
> > investment. All estimates, opinions and other information contained herein
> > are subject to change without notice and are provided in good faith but
> > without legal responsibility or liability. Opinion may be personal to the
> > author and may not reflect the opinions of WOOD & Co. Communications from
> > sales persons, sales traders or traders should not be regarded as
> > investment research and may contain opinions or trading ideas which are
> > different from WOOD & Co. investment research opinions. This e-mail and any
> > attachments are confidential and may be privileged or otherwise protected
> > from disclosure. If you are not a named addressee you must not use,
> > disclose, distribute, copy, print or rely on this e-mail and any of its
> > attachments. Please notify the sender that you have received this email by
> > mistake by replying to the email, and then delete the email and any copies
> > of it. Although WOOD & Co. routinely screens e-mails for viruses,
> > addressees should scan this e-mail and any attachments for viruses. WOOD &
> > Co. makes no representation or warranty as to the absence of viruses in
> > this e-mail or any attachments. Please note that to ensure regulatory
> > compliance and for the protection of our clients and business, we may
> > monitor and read e-mails sent to and from our server(s).
> >
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2

Jan Bares
Head of Calypso development | IT Development

Phone: +420 222 096 457
Mobile: +420 776 333 676
Email: jan.ba...@wood.cz

WOOD & Company
Palladium, nám. Republiky 1079/1a, 110 00 Prague 1, Czech Republic | wood.cz






DISCLAIMER
WOOD & Company Financial Services, a.s. and its branches are authorized and 
regulated by the CNB as Home State regulator and in Poland by the KNF, in 
Slovakia by the NBS, in Italy by the CONSOB and in the UK by the FCA as Host 
State regulators. For further information about WOOD & Co., its investment 
services, financial instruments and associated risks, safeguard client assets 
(incl. compensation schemes) and contractual relationship please see our 
website at www.wood.com under section Corporate 
Governance. Unless otherwise stated, this transmission is neither an offer nor 
the solicitation of an offer to sell or purchase any investment. All estimates, 
opinions and other information contained herein are subject to change without 
notice and are provided in good faith but without legal responsibility or 
liability. Opinion may be personal to the author and may not reflect the 
opinions of WOOD & Co. Communications from sales persons, sales 

Re: When exactly are the route "after processing" options such as file move done?

[Claus Ibsen]

Its the original route that move/rename then file when its done, not the
wiretaps

On Tue, Jun 18, 2024 at 11:40 AM Jan Bares, WOOD & Co.
 wrote:

> Hi,
>
> Say I have a route that reads a file and after processing it moves the
> file to another folder.
>
>
> from("file:/mnt/folder/?include=input.txt=done/{date:now:MMddHHmmssSSS}.txt")
> .process(...)
> .wireTap("routeB")
> .split(...)
> .filter(...)
> .to(...)
> .wireTap("routeC")
> .process(...)
> .to(...)
>
> When exactly is the move operation done? As you can see I have
> intermediate to() in my route and also two wireTap() that pass the Exchange
> to another route. The question is related to a problem when the Exchange
> still contains GenericFile but we have seen exception "file not found" in a
> wireTap route, because the file was already renamed.
>
> Thank you, Jan
>
> Jan Bares
> Head of Calypso development | IT Development
>
> Phone: +420 222 096 457
> Mobile: +420 776 333 676
> Email: jan.ba...@wood.cz
>
> WOOD & Company
> Palladium, n?m. Republiky 1079/1a, 110 00 Prague 1, Czech Republic |
> wood.cz
>
>
>
>
>
> 
> DISCLAIMER
> WOOD & Company Financial Services, a.s. and its branches are authorized
> and regulated by the CNB as Home State regulator and in Poland by the KNF,
> in Slovakia by the NBS, in Italy by the CONSOB and in the UK by the FCA as
> Host State regulators. For further information about WOOD & Co., its
> investment services, financial instruments and associated risks, safeguard
> client assets (incl. compensation schemes) and contractual relationship
> please see our website at www.wood.com under
> section Corporate Governance. Unless otherwise stated, this transmission is
> neither an offer nor the solicitation of an offer to sell or purchase any
> investment. All estimates, opinions and other information contained herein
> are subject to change without notice and are provided in good faith but
> without legal responsibility or liability. Opinion may be personal to the
> author and may not reflect the opinions of WOOD & Co. Communications from
> sales persons, sales traders or traders should not be regarded as
> investment research and may contain opinions or trading ideas which are
> different from WOOD & Co. investment research opinions. This e-mail and any
> attachments are confidential and may be privileged or otherwise protected
> from disclosure. If you are not a named addressee you must not use,
> disclose, distribute, copy, print or rely on this e-mail and any of its
> attachments. Please notify the sender that you have received this email by
> mistake by replying to the email, and then delete the email and any copies
> of it. Although WOOD & Co. routinely screens e-mails for viruses,
> addressees should scan this e-mail and any attachments for viruses. WOOD &
> Co. makes no representation or warranty as to the absence of viruses in
> this e-mail or any attachments. Please note that to ensure regulatory
> compliance and for the protection of our clients and business, we may
> monitor and read e-mails sent to and from our server(s).
>


-- 
Claus Ibsen
-
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

When exactly are the route "after processing" options such as file move done?

[Jan Bares, WOOD & Co.]

Hi,

Say I have a route that reads a file and after processing it moves the file to 
another folder.

from("file:/mnt/folder/?include=input.txt=done/{date:now:MMddHHmmssSSS}.txt")
.process(...)
.wireTap("routeB")
.split(...)
.filter(...)
.to(...)
.wireTap("routeC")
.process(...)
.to(...)

When exactly is the move operation done? As you can see I have intermediate 
to() in my route and also two wireTap() that pass the Exchange to another 
route. The question is related to a problem when the Exchange still contains 
GenericFile but we have seen exception "file not found" in a wireTap route, 
because the file was already renamed.

Thank you, Jan

Jan Bares
Head of Calypso development | IT Development

Phone: +420 222 096 457
Mobile: +420 776 333 676
Email: jan.ba...@wood.cz

WOOD & Company
Palladium, n?m. Republiky 1079/1a, 110 00 Prague 1, Czech Republic | wood.cz






DISCLAIMER
WOOD & Company Financial Services, a.s. and its branches are authorized and 
regulated by the CNB as Home State regulator and in Poland by the KNF, in 
Slovakia by the NBS, in Italy by the CONSOB and in the UK by the FCA as Host 
State regulators. For further information about WOOD & Co., its investment 
services, financial instruments and associated risks, safeguard client assets 
(incl. compensation schemes) and contractual relationship please see our 
website at www.wood.com under section Corporate 
Governance. Unless otherwise stated, this transmission is neither an offer nor 
the solicitation of an offer to sell or purchase any investment. All estimates, 
opinions and other information contained herein are subject to change without 
notice and are provided in good faith but without legal responsibility or 
liability. Opinion may be personal to the author and may not reflect the 
opinions of WOOD & Co. Communications from sales persons, sales traders or 
traders should not be regarded as investment research and may contain opinions 
or trading ideas which are different from WOOD & Co. investment research 
opinions. This e-mail and any attachments are confidential and may be 
privileged or otherwise protected from disclosure. If you are not a named 
addressee you must not use, disclose, distribute, copy, print or rely on this 
e-mail and any of its attachments. Please notify the sender that you have 
received this email by mistake by replying to the email, and then delete the 
email and any copies of it. Although WOOD & Co. routinely screens e-mails for 
viruses, addressees should scan this e-mail and any attachments for viruses. 
WOOD & Co. makes no representation or warranty as to the absence of viruses in 
this e-mail or any attachments. Please note that to ensure regulatory 
compliance and for the protection of our clients and business, we may monitor 
and read e-mails sent to and from our server(s).

[Announcement] Release Camel K 2.3.3

[Pasquale Congiusti]

Hi all,
on behalf of Apache Camel PMC I am happy to announce the official release
of Camel K version 2.3.3. This release fixes certain regressions identified
in version 2.3.2 for Openshift clusters. Artifacts and changelog available
in Github release page [1]. OLM and Helm artifacts will be available in the
next hours as there are background synchronization processes that may take
some time to complete.

Thanks and regards,
Pasquale Congiustí.

[1] https://github.com/apache/camel-k/releases/tag/v2.3.3

[RESULT] [VOTE] Release Apache Camel K 2.3.3

[Pasquale Congiusti]

Hello all,
the vote passes with the following results:

3 +1 binding: Claus Ibsen, Andrea Cosentino, Pasquale Congiusti

4 +1 non binding: Gaelle Fournier, Thomas Diesler, Miguel de Barros, Mert
Ozturk

Thanks to all the voters, I'll go ahead with the process.

Cheers,
Pasquale.

Re: [VOTE] Release Apache Camel K 2.3.3

[Pasquale Congiusti]

Hi all,
Vote is closed and passed with 3 binding and 4 non binding votes.

I'll continue the process and make the release during the day.

Thanks,
Pasquale.

On Fri, Jun 7, 2024 at 2:10 PM Pasquale Congiusti <
pasquale.congiu...@gmail.com> wrote:

> Hello,
>
> This is a vote to release Apache Camel K 2.3.3. This release provides the
> rebundle of OLM CRDs and some bug fixes required to fix a regression
> spotted on running version 2.3.2 on Openshift cluster via OLM [1].
>
> Camel K release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k/2.3.3/
>
> Camel K Tag:
> https://github.com/apache/camel-k/releases/tag/v2.3.3
>
> Camel K CRD Java dependency staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1719
>
> Staging container image repository (multi architecture manifest):
> https://hub.docker.com/layers/camelk/camel-k/2.3.3/images/sha256-f340d21029300082ef93bb947715aee8bc48a930aae6b0163673ed9cd355b7cc?context=explore
>
> It's possible to install all staging artifacts with a single command
> (preferably using the kamel CLI you find in Camel K release files):
>
> $ kamel install --operator-image=camelk/camel-k:2.3.3 --olm=false
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release Apache Camel K 2.3.3
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> I start the vote with my +1 (binding).
>
> Thanks and regards,
> Pasquale Congiusti
>
> [1] https://github.com/apache/camel-k/milestone/53?closed=1
>

Re: [VOTE] Release Apache Camel K 2.3.3

[Claus Ibsen]

+1 (binding)

On Fri, Jun 7, 2024 at 2:11 PM Pasquale Congiusti <
pasquale.congiu...@gmail.com> wrote:

> Hello,
>
> This is a vote to release Apache Camel K 2.3.3. This release provides the
> rebundle of OLM CRDs and some bug fixes required to fix a regression
> spotted on running version 2.3.2 on Openshift cluster via OLM [1].
>
> Camel K release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k/2.3.3/
>
> Camel K Tag:
> https://github.com/apache/camel-k/releases/tag/v2.3.3
>
> Camel K CRD Java dependency staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1719
>
> Staging container image repository (multi architecture manifest):
>
> https://hub.docker.com/layers/camelk/camel-k/2.3.3/images/sha256-f340d21029300082ef93bb947715aee8bc48a930aae6b0163673ed9cd355b7cc?context=explore
>
> It's possible to install all staging artifacts with a single command
> (preferably using the kamel CLI you find in Camel K release files):
>
> $ kamel install --operator-image=camelk/camel-k:2.3.3 --olm=false
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release Apache Camel K 2.3.3
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> I start the vote with my +1 (binding).
>
> Thanks and regards,
> Pasquale Congiusti
>
> [1] https://github.com/apache/camel-k/milestone/53?closed=1
>


-- 
Claus Ibsen
-
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: [VOTE] Release Apache Camel K 2.3.3

[Andrea Cosentino]

+1 (binding)

Thanks Pasquale

Il ven 7 giu 2024, 14:11 Pasquale Congiusti 
ha scritto:

> Hello,
>
> This is a vote to release Apache Camel K 2.3.3. This release provides the
> rebundle of OLM CRDs and some bug fixes required to fix a regression
> spotted on running version 2.3.2 on Openshift cluster via OLM [1].
>
> Camel K release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k/2.3.3/
>
> Camel K Tag:
> https://github.com/apache/camel-k/releases/tag/v2.3.3
>
> Camel K CRD Java dependency staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1719
>
> Staging container image repository (multi architecture manifest):
>
> https://hub.docker.com/layers/camelk/camel-k/2.3.3/images/sha256-f340d21029300082ef93bb947715aee8bc48a930aae6b0163673ed9cd355b7cc?context=explore
>
> It's possible to install all staging artifacts with a single command
> (preferably using the kamel CLI you find in Camel K release files):
>
> $ kamel install --operator-image=camelk/camel-k:2.3.3 --olm=false
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release Apache Camel K 2.3.3
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> I start the vote with my +1 (binding).
>
> Thanks and regards,
> Pasquale Congiusti
>
> [1] https://github.com/apache/camel-k/milestone/53?closed=1
>

Re: [VOTE] Release Apache Camel K 2.3.3

[Gaëlle Fournier]

+1 (non-binding)

Thanks Pasquale!

---
Gaëlle

Le ven. 7 juin 2024 à 14:12, Pasquale Congiusti <
pasquale.congiu...@gmail.com> a écrit :

> Hello,
>
> This is a vote to release Apache Camel K 2.3.3. This release provides the
> rebundle of OLM CRDs and some bug fixes required to fix a regression
> spotted on running version 2.3.2 on Openshift cluster via OLM [1].
>
> Camel K release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k/2.3.3/
>
> Camel K Tag:
> https://github.com/apache/camel-k/releases/tag/v2.3.3
>
> Camel K CRD Java dependency staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1719
>
> Staging container image repository (multi architecture manifest):
>
> https://hub.docker.com/layers/camelk/camel-k/2.3.3/images/sha256-f340d21029300082ef93bb947715aee8bc48a930aae6b0163673ed9cd355b7cc?context=explore
>
> It's possible to install all staging artifacts with a single command
> (preferably using the kamel CLI you find in Camel K release files):
>
> $ kamel install --operator-image=camelk/camel-k:2.3.3 --olm=false
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release Apache Camel K 2.3.3
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> I start the vote with my +1 (binding).
>
> Thanks and regards,
> Pasquale Congiusti
>
> [1] https://github.com/apache/camel-k/milestone/53?closed=1
>

[VOTE] Release Apache Camel K 2.3.3

[Pasquale Congiusti]

Hello,

This is a vote to release Apache Camel K 2.3.3. This release provides the
rebundle of OLM CRDs and some bug fixes required to fix a regression
spotted on running version 2.3.2 on Openshift cluster via OLM [1].

Camel K release files:
https://dist.apache.org/repos/dist/dev/camel/camel-k/2.3.3/

Camel K Tag:
https://github.com/apache/camel-k/releases/tag/v2.3.3

Camel K CRD Java dependency staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1719

Staging container image repository (multi architecture manifest):
https://hub.docker.com/layers/camelk/camel-k/2.3.3/images/sha256-f340d21029300082ef93bb947715aee8bc48a930aae6b0163673ed9cd355b7cc?context=explore

It's possible to install all staging artifacts with a single command
(preferably using the kamel CLI you find in Camel K release files):

$ kamel install --operator-image=camelk/camel-k:2.3.3 --olm=false

Please test this release candidate and cast your vote.

[ ] +1 Release Apache Camel K 2.3.3
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

I start the vote with my +1 (binding).

Thanks and regards,
Pasquale Congiusti

[1] https://github.com/apache/camel-k/milestone/53?closed=1

Re: Processor data persistence during route stop

[Mark Nuttall]

This is just using one of the EIPs to handle your use case. Camel is just
EIPs wired together.

" Otherwise we will have to include DB related jars/code to do the same
what Camel already does."
You have to do that if you want to persist anything, Routes should not be
long running (i.e. break up the work using channels). If you do really have
this issue, then check out one of the EIPs or maybe use a workflow tool
along side Camel.




On Thu, Jun 6, 2024 at 8:00 AM Jan Bares, WOOD & Co.
 wrote:

> It would be nice to be able to use Camel routes for persistence, since we
> already persist other data this way. When route is about to be stopped,
> pass a special message to a route, that will persist processor data to
> database using Camel endpoint. And in the same way, when route is to be
> started, endpoint will read data from database and initialize the
> processor. Otherwise we will have to include DB related jars/code to do the
> same what Camel already does.
>
> Thank you, Jan
>
> > -Original Message-
> > From: Claus Ibsen 
> > Sent: Thursday, June 6, 2024 1:16 PM
> > To: users@camel.apache.org
> > Subject: Re: Processor data persistence during route stop
> >
> > Hi
> >
> > That is something you need to implement yourself to have this kind of
> > persistence. Your processor or beans can extend ServiceSupport (or
> > implement Service) from Camel then you have doStart/doStop methods that
> > Camel calls for you.
> >
> >
> > On Thu, Jun 6, 2024 at 11:18 AM Branko Husarik, Wood & Co.
> >  wrote:
> >
> > > Hello,
> > >
> > >
> > >
> > > I would like to ask about the proper saving and loading of processor
> > > variables to the database at the route stop. I am trying to use
> > > RoutePolicySupport to find out the system shutdown, but I don’t see any
> > > nice solution for how to persist the state of some processors that
> could be
> > > restored after startup.
> > >
> > > Please, can you give me tips? Thank you
> > >
> > >
> > >
> > > Best Regards
> > >
> > >
> > >
> > > Branko Husarik
> > >
> > >
> > >
> > > *Braňko Husárik*
> > > Calypso Developer
> > > IT Development
> > > email: branko.husa...@wood.cz
> > > m: +420 606 022 474
> > >
> > > WOOD & Company
> > > Palladium, nám. Republiky 1079/1a
> > > 110 00 Prague 1, Czech Republic
> > > wood.com
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > --
> > > DISCLAIMER WOOD & Company Financial Services, a.s. and its branches are
> > > authorized and regulated by the CNB as Home State regulator and in
> Poland
> > > by the KNF, in Slovakia by the NBS, in Italy by the CONSOB and in the
> UK by
> > > the FCA as Host State regulators. For further information about WOOD &
> Co.,
> > > its investment services, financial instruments and associated risks,
> > > safeguard client assets (incl. compensation schemes) and contractual
> > > relationship please see our website at www.wood.com under section
> > > Corporate Governance. Unless otherwise stated, this transmission is
> neither
> > > an offer nor the solicitation of an offer to sell or purchase any
> > > investment. All estimates, opinions and other information contained
> herein
> > > are subject to change without notice and are provided in good faith but
> > > without legal responsibility or liability. Opinion may be personal to
> the
> > > author and may not reflect the opinions of WOOD & Co. Communications
> from
> > > sales persons, sales traders or traders should not be regarded as
> > > investment research and may contain opinions or trading ideas which are
> > > different from WOOD & Co. investment research opinions. This e-mail
> and any
> > > attachments are confidential and may be privileged or otherwise
> protected
> > > from disclosure. If you are not a named addressee you must not use,
> > > disclose, distribute, copy, print or rely on this e-mail and any of its
> > > attachments. Please notify the sender that you have received this
> email by
> > > mistake by replying to the email, and then delete the email and any
> copies
> > > of it. Although WOOD & Co. routinely screens e-mails for viruses,
> > > addressees should scan this e-mail and any attachments for viruses.
> WOOD &
> > > Co. makes no representation or warranty as to the absence of viruses in
> > > this e-mail or any attachments. Please note that to ensure regulatory
> > > compliance and for the protection of our clients and business, we may
> > > monitor and read e-mails sent to and from our server(s).
> > >
> >
> >
> > --
> > Claus Ibsen
> > -
> > @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
>
> Jan Bares
> Head of Calypso development | IT Development
>
> Phone: +420 222 096 457
> Mobile: +420 776 333 676
> Email: jan.ba...@wood.cz
>
> WOOD & Company
> Palladium, nám. Republiky 1079/1a, 110 00 Prague 1, Czech Republic |
> wood.cz
>
>
>
>
>
> 
> DISCLAIMER
> WOOD & Company Financial Services, a.s. and its branches are 

Camel K 2.3.2 regression on OLM Openshift installation

[Pasquale Congiusti]

Hi folks,
we've detected a regression happening on Openshift platform when using OLM
installation methodology with recent 2.3.2 Camel K operator. The details of
the problem are described in [1]. This problem is only affecting Openshift
with S2I publishing strategy mode, so, we suggest not to upgrade to such a
version and wait for the upcoming patch release instead. If you're already
on that version, consider downgrading to 2.3.1 or wait for the upcoming
patch release instead. Running Integrations and other operations are not
affected by this problem, only new Integration built via S2I are affected.

Please, note that other platforms or publishing strategies are not affected
and are running regularly as well. We should be starting the 2.3.3 release
by the end of this week or beginning of next week as latest.

Apologies for any inconvenience, we hope to fix this problem ASAP.

Cheers,
on behalf of Camel PMC, Pasquale Congiustí.

[1] https://github.com/apache/camel-k/issues/5595

RE: Processor data persistence during route stop

[Jan Bares, WOOD & Co.]

It would be nice to be able to use Camel routes for persistence, since we 
already persist other data this way. When route is about to be stopped, pass a 
special message to a route, that will persist processor data to database using 
Camel endpoint. And in the same way, when route is to be started, endpoint will 
read data from database and initialize the processor. Otherwise we will have to 
include DB related jars/code to do the same what Camel already does.

Thank you, Jan

> -Original Message-
> From: Claus Ibsen 
> Sent: Thursday, June 6, 2024 1:16 PM
> To: users@camel.apache.org
> Subject: Re: Processor data persistence during route stop
>
> Hi
>
> That is something you need to implement yourself to have this kind of
> persistence. Your processor or beans can extend ServiceSupport (or
> implement Service) from Camel then you have doStart/doStop methods that
> Camel calls for you.
>
>
> On Thu, Jun 6, 2024 at 11:18 AM Branko Husarik, Wood & Co.
>  wrote:
>
> > Hello,
> >
> >
> >
> > I would like to ask about the proper saving and loading of processor
> > variables to the database at the route stop. I am trying to use
> > RoutePolicySupport to find out the system shutdown, but I don’t see any
> > nice solution for how to persist the state of some processors that could be
> > restored after startup.
> >
> > Please, can you give me tips? Thank you
> >
> >
> >
> > Best Regards
> >
> >
> >
> > Branko Husarik
> >
> >
> >
> > *Braňko Husárik*
> > Calypso Developer
> > IT Development
> > email: branko.husa...@wood.cz
> > m: +420 606 022 474
> >
> > WOOD & Company
> > Palladium, nám. Republiky 1079/1a
> > 110 00 Prague 1, Czech Republic
> > wood.com
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > --
> > DISCLAIMER WOOD & Company Financial Services, a.s. and its branches are
> > authorized and regulated by the CNB as Home State regulator and in Poland
> > by the KNF, in Slovakia by the NBS, in Italy by the CONSOB and in the UK by
> > the FCA as Host State regulators. For further information about WOOD & Co.,
> > its investment services, financial instruments and associated risks,
> > safeguard client assets (incl. compensation schemes) and contractual
> > relationship please see our website at www.wood.com under section
> > Corporate Governance. Unless otherwise stated, this transmission is neither
> > an offer nor the solicitation of an offer to sell or purchase any
> > investment. All estimates, opinions and other information contained herein
> > are subject to change without notice and are provided in good faith but
> > without legal responsibility or liability. Opinion may be personal to the
> > author and may not reflect the opinions of WOOD & Co. Communications from
> > sales persons, sales traders or traders should not be regarded as
> > investment research and may contain opinions or trading ideas which are
> > different from WOOD & Co. investment research opinions. This e-mail and any
> > attachments are confidential and may be privileged or otherwise protected
> > from disclosure. If you are not a named addressee you must not use,
> > disclose, distribute, copy, print or rely on this e-mail and any of its
> > attachments. Please notify the sender that you have received this email by
> > mistake by replying to the email, and then delete the email and any copies
> > of it. Although WOOD & Co. routinely screens e-mails for viruses,
> > addressees should scan this e-mail and any attachments for viruses. WOOD &
> > Co. makes no representation or warranty as to the absence of viruses in
> > this e-mail or any attachments. Please note that to ensure regulatory
> > compliance and for the protection of our clients and business, we may
> > monitor and read e-mails sent to and from our server(s).
> >
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2

Jan Bares
Head of Calypso development | IT Development

Phone: +420 222 096 457
Mobile: +420 776 333 676
Email: jan.ba...@wood.cz

WOOD & Company
Palladium, nám. Republiky 1079/1a, 110 00 Prague 1, Czech Republic | wood.cz






DISCLAIMER
WOOD & Company Financial Services, a.s. and its branches are authorized and 
regulated by the CNB as Home State regulator and in Poland by the KNF, in 
Slovakia by the NBS, in Italy by the CONSOB and in the UK by the FCA as Host 
State regulators. For further information about WOOD & Co., its investment 
services, financial instruments and associated risks, safeguard client assets 
(incl. compensation schemes) and contractual relationship please see our 
website at www.wood.com under section Corporate 
Governance. Unless otherwise stated, this transmission is neither an offer nor 
the solicitation of an offer to sell or purchase any investment. All estimates, 
opinions and other information contained herein are subject to change without 
notice and are provided in good faith but without 

Re: Processor data persistence during route stop

[Claus Ibsen]

Hi

That is something you need to implement yourself to have this kind of
persistence. Your processor or beans can extend ServiceSupport (or
implement Service) from Camel then you have doStart/doStop methods that
Camel calls for you.


On Thu, Jun 6, 2024 at 11:18 AM Branko Husarik, Wood & Co.
 wrote:

> Hello,
>
>
>
> I would like to ask about the proper saving and loading of processor
> variables to the database at the route stop. I am trying to use
> RoutePolicySupport to find out the system shutdown, but I don’t see any
> nice solution for how to persist the state of some processors that could be
> restored after startup.
>
> Please, can you give me tips? Thank you
>
>
>
> Best Regards
>
>
>
> Branko Husarik
>
>
>
> *Braňko Husárik*
> Calypso Developer
> IT Development
> email: branko.husa...@wood.cz
> m: +420 606 022 474
>
> WOOD & Company
> Palladium, nám. Republiky 1079/1a
> 110 00 Prague 1, Czech Republic
> wood.com
>
>
>
>
>
>
>
>
>
> --
> DISCLAIMER WOOD & Company Financial Services, a.s. and its branches are
> authorized and regulated by the CNB as Home State regulator and in Poland
> by the KNF, in Slovakia by the NBS, in Italy by the CONSOB and in the UK by
> the FCA as Host State regulators. For further information about WOOD & Co.,
> its investment services, financial instruments and associated risks,
> safeguard client assets (incl. compensation schemes) and contractual
> relationship please see our website at www.wood.com under section
> Corporate Governance. Unless otherwise stated, this transmission is neither
> an offer nor the solicitation of an offer to sell or purchase any
> investment. All estimates, opinions and other information contained herein
> are subject to change without notice and are provided in good faith but
> without legal responsibility or liability. Opinion may be personal to the
> author and may not reflect the opinions of WOOD & Co. Communications from
> sales persons, sales traders or traders should not be regarded as
> investment research and may contain opinions or trading ideas which are
> different from WOOD & Co. investment research opinions. This e-mail and any
> attachments are confidential and may be privileged or otherwise protected
> from disclosure. If you are not a named addressee you must not use,
> disclose, distribute, copy, print or rely on this e-mail and any of its
> attachments. Please notify the sender that you have received this email by
> mistake by replying to the email, and then delete the email and any copies
> of it. Although WOOD & Co. routinely screens e-mails for viruses,
> addressees should scan this e-mail and any attachments for viruses. WOOD &
> Co. makes no representation or warranty as to the absence of viruses in
> this e-mail or any attachments. Please note that to ensure regulatory
> compliance and for the protection of our clients and business, we may
> monitor and read e-mails sent to and from our server(s).
>


-- 
Claus Ibsen
-
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Processor data persistence during route stop

[Branko Husarik, Wood & Co.]

Hello,

I would like to ask about the proper saving and loading of processor variables 
to the database at the route stop. I am trying to use RoutePolicySupport to 
find out the system shutdown, but I don't see any nice solution for how to 
persist the state of some processors that could be restored after startup.
Please, can you give me tips? Thank you

Best Regards

Branko Husarik

[cid:image001.png@01DAB801.3292F1E0]
Braňko Husárik
Calypso Developer
IT Development
email: branko.husa...@wood.cz
m: +420 606 022 474

WOOD & Company
Palladium, nám. Republiky 1079/1a
110 00 Prague 1, Czech Republic
wood.com








DISCLAIMER
WOOD & Company Financial Services, a.s. and its branches are authorized and 
regulated by the CNB as Home State regulator and in Poland by the KNF, in 
Slovakia by the NBS, in Italy by the CONSOB and in the UK by the FCA as Host 
State regulators. For further information about WOOD & Co., its investment 
services, financial instruments and associated risks, safeguard client assets 
(incl. compensation schemes) and contractual relationship please see our 
website at www.wood.com under section Corporate 
Governance. Unless otherwise stated, this transmission is neither an offer nor 
the solicitation of an offer to sell or purchase any investment. All estimates, 
opinions and other information contained herein are subject to change without 
notice and are provided in good faith but without legal responsibility or 
liability. Opinion may be personal to the author and may not reflect the 
opinions of WOOD & Co. Communications from sales persons, sales traders or 
traders should not be regarded as investment research and may contain opinions 
or trading ideas which are different from WOOD & Co. investment research 
opinions. This e-mail and any attachments are confidential and may be 
privileged or otherwise protected from disclosure. If you are not a named 
addressee you must not use, disclose, distribute, copy, print or rely on this 
e-mail and any of its attachments. Please notify the sender that you have 
received this email by mistake by replying to the email, and then delete the 
email and any copies of it. Although WOOD & Co. routinely screens e-mails for 
viruses, addressees should scan this e-mail and any attachments for viruses. 
WOOD & Co. makes no representation or warranty as to the absence of viruses in 
this e-mail or any attachments. Please note that to ensure regulatory 
compliance and for the protection of our clients and business, we may monitor 
and read e-mails sent to and from our server(s).

[Announcement] Release Camel K 2.3.2

[Pasquale Congiusti]

Hi all,
on behalf of Apache Camel PMC I am happy to announce the official release
of Camel K version 2.3.2. This release fixes certain regressions identified
in version 2.3.1. Artifacts and changelog available in Github release page
[1]. OLM and Helm artifacts will be available in the next hours as there
are background synchronization processes that may take some time to
complete.

Thanks and regards,
Pasquale Congiustí.

[1] https://github.com/apache/camel-k/releases/tag/v2.3.2

[RESULT] [VOTE] Release Apache Camel K 2.3.2

[Pasquale Congiusti]

Hello all,
the vote passes with the following results:

5 +1 binding: Claus Ibsen, Nicolas Filotto, Zineb Bendhiba, Andrea
Cosentino, Pasquale Congiusti

4 +1 non binding: Gaelle Fournier, Miguel de Barros, Mert Ozturk, Deepak
Pandey

Thanks to all the voters, I'll go ahead with the process.

Cheers,
Pasquale.

Re: [VOTE] Release Apache Camel K 2.3.2 - Attempt #2

[Pasquale Congiusti]

Vote is closed and passed with 5 binding and 4 non binding votes.

I'll continue the process and make the release during the day.

Thanks,
Pasquale.

On Tue, May 28, 2024 at 4:27 PM Pasquale Congiusti <
pasquale.congiu...@gmail.com> wrote:

> Hello,
>
> This is a vote to release Apache Camel K 2.3.2. This release provides
> some bug fixes [1] due to certain regressions introduced in version 2.3.1.
> This is a second attempt which is replacing the staging artifacts released
> in the previous vote (canceled due to some other regressions identified,
> and promptly fixed).
>
> Camel K release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k/2.3.2/
>
> Camel K Tag:
> https://github.com/apache/camel-k/releases/tag/v2.3.2
>
> Camel K CRD Java dependency staging repository:
> https://repository.apache.org/content/repositories/org apache camel-1715/
> 
>
> Staging container image repository (multi architecture manifest):
> https://hub.docker.com/layers/camelk/camel-k/2.3.2/images/sha256-b4e2704b79e3b0fec6d1f5d8968764174ca8223ed7b0f5f5468d57f7829f7f80?context=explore
>
> It's possible to install all staging artifacts with a single command
> (preferably using the kamel CLI you find in Camel K release files):
>
> $ kamel install --operator-image=camelk/camel-k:2.3.2 --olm=false
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release Apache Camel K 2.3.2
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> I start the vote with my +1 (binding).
>
> Thanks and regards,
> Pasquale Congiusti
>
> [1] https://github.com/apache/camel-k/milestone/51?closed=1
>

Re: Issue with duplicate MBean operation causing Hawtio to crash

[Claus Ibsen]

Hi

Thanks for reporting
https://issues.apache.org/jira/browse/CAMEL-20820

On Fri, May 31, 2024 at 10:37 AM Roger Goossens 
wrote:

> Hello everybody,
>
> We're hitting a small issue in Camel that unfortunately causes Hawtio to
> crash after upgrading to Camel 4 (and Hawtio 4).
>
> Hawtio crashes due to a duplicate MBean operation being exposed when using
> a json-validator endpoint (and possibly some other endpoints as well). I
> made a small project with a json-validator endpoint to reproduce the issue.
> The project is available here:
> https://github.com/rphgoossens/json-validation
> When you start it up and try to open the Hawtio dashboard (
> http://localhost:8080/actuator/hawtio), you'll notice it won't display
> anything and there's an error visible in the web console.
>
> The underlying issue (after some digging) appears to be a duplicate MBean
> Operation being exposed for the json-validator endpoint
> (clearContentCache())
>
> [image: Screenshot 2024-05-31 at 09.58.41.jpg]
>
> The duplication is a result of a ManagedOperation annotation being present
> on the clearContentCache method of the ResourceEndpoint class (a superclass
> of the JsonValdatorEndpoint class) and a ManagedOperation annotation being
> present on the clearContentCache method of the ManagedResourceEndpointMBean
> interface (an interface that the JsonValidatorEndpoint class implements).
> When you hover over both buttons in VisualVm (picture above), you'll both
> buttons having different descriptions (one has the description of the
> annotation in the ResourceEndpoint class and the other gets its description
> from the ManagedResourceEndpointMBean interface)
>
> [image: Screenshot 2024-05-31 at 10.03.26.jpg]
> [image: Screenshot 2024-05-31 at 10.03.49.jpg]
>
> Funny thing is that the duplication of the operation will NOT take place
> if the descriptions in the ManagedOperation annotations are the same (which
> they currently are not obviously). I tested this by shadowing the
> ResourceEndpoint class in my project and adjusting the description.
> ManagedAttribute annotations that are duplicated in ResourceEndpoint and
> ManagedResourceEndpointMBean (like isContentCache()) with different
> descriptions are not duplicated in the MBean exposure funny enough.
>
> You can argue that this shouldn't cause a crash in Hawtio (and it didn't
> in the 3 version), but the duplicate MBean operation is a small bug IMHO,
> since both operations in the end will call the same method. Only the one
> coming from the class at the bottom of the hierarchy (in this case
> the ResourceEndpoint one) should be exposed.
>
> So my request would be to create a Camel issue to solve this in a future
> Camel version.
>
> The only workaround we currently have is to set the
> camel.main.jms-management-m-beans-level to contextonly. Then Hawtio will
> load without errors, but then we're missing a lot MBean functionality, eg.
> stop and start individual routes in the project.
>
> I hope the information I provided was helpful and complete. Feel free to
> mail me for any additional questions and please let me know if you will
> create an issue for this.
>
> Best Regards,
> Roger Goossens.
>
>
>
>

-- 
Claus Ibsen
-
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Issue with duplicate MBean operation causing Hawtio to crash

[Roger Goossens]

Hello everybody,

We're hitting a small issue in Camel that unfortunately causes Hawtio to
crash after upgrading to Camel 4 (and Hawtio 4).

Hawtio crashes due to a duplicate MBean operation being exposed when using
a json-validator endpoint (and possibly some other endpoints as well). I
made a small project with a json-validator endpoint to reproduce the issue.
The project is available here:
https://github.com/rphgoossens/json-validation
When you start it up and try to open the Hawtio dashboard (
http://localhost:8080/actuator/hawtio), you'll notice it won't display
anything and there's an error visible in the web console.

The underlying issue (after some digging) appears to be a duplicate MBean
Operation being exposed for the json-validator endpoint
(clearContentCache())

[image: Screenshot 2024-05-31 at 09.58.41.jpg]

The duplication is a result of a ManagedOperation annotation being present
on the clearContentCache method of the ResourceEndpoint class (a superclass
of the JsonValdatorEndpoint class) and a ManagedOperation annotation being
present on the clearContentCache method of the ManagedResourceEndpointMBean
interface (an interface that the JsonValidatorEndpoint class implements).
When you hover over both buttons in VisualVm (picture above), you'll both
buttons having different descriptions (one has the description of the
annotation in the ResourceEndpoint class and the other gets its description
from the ManagedResourceEndpointMBean interface)

[image: Screenshot 2024-05-31 at 10.03.26.jpg]
[image: Screenshot 2024-05-31 at 10.03.49.jpg]

Funny thing is that the duplication of the operation will NOT take place if
the descriptions in the ManagedOperation annotations are the same (which
they currently are not obviously). I tested this by shadowing the
ResourceEndpoint class in my project and adjusting the description.
ManagedAttribute annotations that are duplicated in ResourceEndpoint and
ManagedResourceEndpointMBean (like isContentCache()) with different
descriptions are not duplicated in the MBean exposure funny enough.

You can argue that this shouldn't cause a crash in Hawtio (and it didn't in
the 3 version), but the duplicate MBean operation is a small bug IMHO,
since both operations in the end will call the same method. Only the one
coming from the class at the bottom of the hierarchy (in this case
the ResourceEndpoint one) should be exposed.

So my request would be to create a Camel issue to solve this in a future
Camel version.

The only workaround we currently have is to set the
camel.main.jms-management-m-beans-level to contextonly. Then Hawtio will
load without errors, but then we're missing a lot MBean functionality, eg.
stop and start individual routes in the project.

I hope the information I provided was helpful and complete. Feel free to
mail me for any additional questions and please let me know if you will
create an issue for this.

Best Regards,
Roger Goossens.

Re: [VOTE] Release Apache Camel K 2.3.2 - Attempt #2

[Mert Öztürk]

+1 (non-binding)

Many thanks for the speedy bug-fixing process with regards to the
regression issues!

On Tue, May 28, 2024 at 4:28 PM Pasquale Congiusti <
pasquale.congiu...@gmail.com> wrote:

> Hello,
>
> This is a vote to release Apache Camel K 2.3.2. This release provides some
> bug fixes [1] due to certain regressions introduced in version 2.3.1. This
> is a second attempt which is replacing the staging artifacts released in
> the previous vote (canceled due to some other regressions identified, and
> promptly fixed).
>
> Camel K release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k/2.3.2/
>
> Camel K Tag:
> https://github.com/apache/camel-k/releases/tag/v2.3.2
>
> Camel K CRD Java dependency staging repository:
> https://repository.apache.org/content/repositories/org apache camel-1715/
> 
>
> Staging container image repository (multi architecture manifest):
>
> https://hub.docker.com/layers/camelk/camel-k/2.3.2/images/sha256-b4e2704b79e3b0fec6d1f5d8968764174ca8223ed7b0f5f5468d57f7829f7f80?context=explore
>
> It's possible to install all staging artifacts with a single command
> (preferably using the kamel CLI you find in Camel K release files):
>
> $ kamel install --operator-image=camelk/camel-k:2.3.2 --olm=false
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release Apache Camel K 2.3.2
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> I start the vote with my +1 (binding).
>
> Thanks and regards,
> Pasquale Congiusti
>
> [1] https://github.com/apache/camel-k/milestone/51?closed=1
>

Re: [VOTE] Release Apache Camel K 2.3.2 - Attempt #2

[Gaëlle Fournier]

+1 (non-binding)

Thanks again!

---
Gaëlle

Le mar. 28 mai 2024 à 16:28, Pasquale Congiusti <
pasquale.congiu...@gmail.com> a écrit :

> Hello,
>
> This is a vote to release Apache Camel K 2.3.2. This release provides some
> bug fixes [1] due to certain regressions introduced in version 2.3.1. This
> is a second attempt which is replacing the staging artifacts released in
> the previous vote (canceled due to some other regressions identified, and
> promptly fixed).
>
> Camel K release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k/2.3.2/
>
> Camel K Tag:
> https://github.com/apache/camel-k/releases/tag/v2.3.2
>
> Camel K CRD Java dependency staging repository:
> https://repository.apache.org/content/repositories/org apache camel-1715/
> 
>
> Staging container image repository (multi architecture manifest):
>
> https://hub.docker.com/layers/camelk/camel-k/2.3.2/images/sha256-b4e2704b79e3b0fec6d1f5d8968764174ca8223ed7b0f5f5468d57f7829f7f80?context=explore
>
> It's possible to install all staging artifacts with a single command
> (preferably using the kamel CLI you find in Camel K release files):
>
> $ kamel install --operator-image=camelk/camel-k:2.3.2 --olm=false
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release Apache Camel K 2.3.2
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> I start the vote with my +1 (binding).
>
> Thanks and regards,
> Pasquale Congiusti
>
> [1] https://github.com/apache/camel-k/milestone/51?closed=1
>

RE: [VOTE] Release Apache Camel K 2.3.2 - Attempt #2

[Nicolas Filotto]

+1 (binding)

De : Andrea Cosentino 
Envoyé : mercredi 29 mai 2024 09:12
À : users@camel.apache.org 
Cc : dev 
Objet : Re: [VOTE] Release Apache Camel K 2.3.2 - Attempt #2

CAUTION: This email originated from outside of the organization. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.



+1 (binding)

Thanks Pasquale

Il giorno mar 28 mag 2024 alle ore 16:28 Pasquale Congiusti <
pasquale.congiu...@gmail.com> ha scritto:

> Hello,
>
> This is a vote to release Apache Camel K 2.3.2. This release provides some
> bug fixes [1] due to certain regressions introduced in version 2.3.1. This
> is a second attempt which is replacing the staging artifacts released in
> the previous vote (canceled due to some other regressions identified, and
> promptly fixed).
>
> Camel K release files:
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fcamel%2Fcamel-k%2F2.3.2%2F=05%7C02%7CNicolas.Filotto%40qlik.com%7C4d8cf23878ab48508d0508dc7faec098%7Cc21eeb5ff5a644e8a997124f2f7a497c%7C0%7C0%7C638525635728403975%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=ylqj4jp%2BjvN2BR8o8RnKQRyZGj%2BbY3zgL6x9WX%2BDSZw%3D=0
>
> Camel K Tag:
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fcamel-k%2Freleases%2Ftag%2Fv2.3.2=05%7C02%7CNicolas.Filotto%40qlik.com%7C4d8cf23878ab48508d0508dc7faec098%7Cc21eeb5ff5a644e8a997124f2f7a497c%7C0%7C0%7C638525635728415658%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=TtLMtZ3codr6c7%2FrS%2FzyRo6z46j8tQOtlqh2rb0DakU%3D=0
>
> Camel K CRD Java dependency staging repository:
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forg=05%7C02%7CNicolas.Filotto%40qlik.com%7C4d8cf23878ab48508d0508dc7faec098%7Cc21eeb5ff5a644e8a997124f2f7a497c%7C0%7C0%7C638525635728418845%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=5K9Wr6S0Q%2Btu%2FbZNPl%2Ff38QJXPbTPox2J%2BEwxznW4LI%3D=0
>  apache camel-1715/
> >
>
> Staging container image repository (multi architecture manifest):
>
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Flayers%2Fcamelk%2Fcamel-k%2F2.3.2%2Fimages%2Fsha256-b4e2704b79e3b0fec6d1f5d8968764174ca8223ed7b0f5f5468d57f7829f7f80%3Fcontext%3Dexplore=05%7C02%7CNicolas.Filotto%40qlik.com%7C4d8cf23878ab48508d0508dc7faec098%7Cc21eeb5ff5a644e8a997124f2f7a497c%7C0%7C0%7C638525635728424765%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=hcC5udWeouA6be90VPzlajDZsmiGnlfmKUwLMSdjyvg%3D=0
>
> It's possible to install all staging artifacts with a single command
> (preferably using the kamel CLI you find in Camel K release files):
>
> $ kamel install --operator-image=camelk/camel-k:2.3.2 --olm=false
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release Apache Camel K 2.3.2
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> I start the vote with my +1 (binding).
>
> Thanks and regards,
> Pasquale Congiusti
>
> [1] 
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fcamel-k%2Fmilestone%2F51%3Fclosed%3D1=05%7C02%7CNicolas.Filotto%40qlik.com%7C4d8cf23878ab48508d0508dc7faec098%7Cc21eeb5ff5a644e8a997124f2f7a497c%7C0%7C0%7C638525635728427706%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=cQ3xapFJ7kqeFv6fIx7BKAroSqgmt2%2FVBssoWFIbTCw%3D=0
>

The information transmitted is intended only for the person or entity to which 
it is addressed and may contain confidential and/or privileged material. Any 
review, retransmission, dissemination or other use of, or taking of any action 
in reliance upon, this information by persons or entities other than the 
intended recipient is prohibited. If you received this in 

Re: [VOTE] Release Apache Camel K 2.3.2 - Attempt #2

[Andrea Cosentino]

+1 (binding)

Thanks Pasquale

Il giorno mar 28 mag 2024 alle ore 16:28 Pasquale Congiusti <
pasquale.congiu...@gmail.com> ha scritto:

> Hello,
>
> This is a vote to release Apache Camel K 2.3.2. This release provides some
> bug fixes [1] due to certain regressions introduced in version 2.3.1. This
> is a second attempt which is replacing the staging artifacts released in
> the previous vote (canceled due to some other regressions identified, and
> promptly fixed).
>
> Camel K release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k/2.3.2/
>
> Camel K Tag:
> https://github.com/apache/camel-k/releases/tag/v2.3.2
>
> Camel K CRD Java dependency staging repository:
> https://repository.apache.org/content/repositories/org apache camel-1715/
> 
>
> Staging container image repository (multi architecture manifest):
>
> https://hub.docker.com/layers/camelk/camel-k/2.3.2/images/sha256-b4e2704b79e3b0fec6d1f5d8968764174ca8223ed7b0f5f5468d57f7829f7f80?context=explore
>
> It's possible to install all staging artifacts with a single command
> (preferably using the kamel CLI you find in Camel K release files):
>
> $ kamel install --operator-image=camelk/camel-k:2.3.2 --olm=false
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release Apache Camel K 2.3.2
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> I start the vote with my +1 (binding).
>
> Thanks and regards,
> Pasquale Congiusti
>
> [1] https://github.com/apache/camel-k/milestone/51?closed=1
>

Re: [VOTE] Release Apache Camel K 2.3.2 - Attempt #2

[zineb bendhiba]

+1 (binding)

Zineb

> Le 28 mai 2024 à 16:28, Pasquale Congiusti  a 
> écrit :
> 
> Hello,
> 
> This is a vote to release Apache Camel K 2.3.2. This release provides some
> bug fixes [1] due to certain regressions introduced in version 2.3.1. This
> is a second attempt which is replacing the staging artifacts released in
> the previous vote (canceled due to some other regressions identified, and
> promptly fixed).
> 
> Camel K release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k/2.3.2/
> 
> Camel K Tag:
> https://github.com/apache/camel-k/releases/tag/v2.3.2
> 
> Camel K CRD Java dependency staging repository:
> https://repository.apache.org/content/repositories/org apache camel-1715/
> 
> 
> Staging container image repository (multi architecture manifest):
> https://hub.docker.com/layers/camelk/camel-k/2.3.2/images/sha256-b4e2704b79e3b0fec6d1f5d8968764174ca8223ed7b0f5f5468d57f7829f7f80?context=explore
> 
> It's possible to install all staging artifacts with a single command
> (preferably using the kamel CLI you find in Camel K release files):
> 
> $ kamel install --operator-image=camelk/camel-k:2.3.2 --olm=false
> 
> Please test this release candidate and cast your vote.
> 
> [ ] +1 Release Apache Camel K 2.3.2
> [ ] -1 Veto the release (provide specific comments)
> 
> The vote is open for at least 72 hours.
> 
> I start the vote with my +1 (binding).
> 
> Thanks and regards,
> Pasquale Congiusti
> 
> [1] https://github.com/apache/camel-k/milestone/51?closed=1

[VOTE] Release Apache Camel K 2.3.2 - Attempt #2

[Pasquale Congiusti]

Hello,

This is a vote to release Apache Camel K 2.3.2. This release provides some
bug fixes [1] due to certain regressions introduced in version 2.3.1. This
is a second attempt which is replacing the staging artifacts released in
the previous vote (canceled due to some other regressions identified, and
promptly fixed).

Camel K release files:
https://dist.apache.org/repos/dist/dev/camel/camel-k/2.3.2/

Camel K Tag:
https://github.com/apache/camel-k/releases/tag/v2.3.2

Camel K CRD Java dependency staging repository:
https://repository.apache.org/content/repositories/org apache camel-1715/


Staging container image repository (multi architecture manifest):
https://hub.docker.com/layers/camelk/camel-k/2.3.2/images/sha256-b4e2704b79e3b0fec6d1f5d8968764174ca8223ed7b0f5f5468d57f7829f7f80?context=explore

It's possible to install all staging artifacts with a single command
(preferably using the kamel CLI you find in Camel K release files):

$ kamel install --operator-image=camelk/camel-k:2.3.2 --olm=false

Please test this release candidate and cast your vote.

[ ] +1 Release Apache Camel K 2.3.2
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

I start the vote with my +1 (binding).

Thanks and regards,
Pasquale Congiusti

[1] https://github.com/apache/camel-k/milestone/51?closed=1

Re: Camel Exception handled unknown element issue

[Bikash Kaushik]

Ok, thanks

On Tue, May 28, 2024 at 4:59 PM Claus Ibsen  wrote:

> Hi
>
> You cannot use  in  as that is the point to handle the
> exception.
> You need to remove it.
>
> On Tue, May 28, 2024 at 1:09 PM Bikash Kaushik 
> wrote:
>
> > Hi Team,
> >
> > I'm  doing camel migration from version 2.15.1 to 4.2.0. In older version
> > there is handle tag in exception block :
> >
> > 
> > java.lang.Exception
> >
> > 
> > false
> > 
> >  > message="X-Correlation-Id_${header.X-Correlation-Id} |
> > UserId_${header.RequestorId} | Exception occured">
> > 
> >
> > *But while upgrading it to Camel 4 getting below error :*
> > Caused by: org.apache.camel.xml.io.XmlPullParserLocationException:
> > Unexpected element '{http://camel.apache.org/schema/spring}handled'
> > in classpath:routes/camel-route.xml, line 885, column 26:
> > 
> >
> > *Please help me in fixing this issue.*
> >
> > --
> >
> >
> > *Regards,*
> > *Bikash Kaushik*
> >
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>


-- 


*Regards,*
*Bikash Kaushik*

Re: Camel Exception handled unknown element issue

[Claus Ibsen]

Hi

You cannot use  in  as that is the point to handle the
exception.
You need to remove it.

On Tue, May 28, 2024 at 1:09 PM Bikash Kaushik 
wrote:

> Hi Team,
>
> I'm  doing camel migration from version 2.15.1 to 4.2.0. In older version
> there is handle tag in exception block :
>
> 
> java.lang.Exception
>
> 
> false
> 
>  message="X-Correlation-Id_${header.X-Correlation-Id} |
> UserId_${header.RequestorId} | Exception occured">
> 
>
> *But while upgrading it to Camel 4 getting below error :*
> Caused by: org.apache.camel.xml.io.XmlPullParserLocationException:
> Unexpected element '{http://camel.apache.org/schema/spring}handled'
> in classpath:routes/camel-route.xml, line 885, column 26:
> 
>
> *Please help me in fixing this issue.*
>
> --
>
>
> *Regards,*
> *Bikash Kaushik*
>


-- 
Claus Ibsen
-
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Camel Exception handled unknown element issue

[Bikash Kaushik]

Hi Team,

I'm  doing camel migration from version 2.15.1 to 4.2.0. In older version
there is handle tag in exception block :


java.lang.Exception


false




*But while upgrading it to Camel 4 getting below error :*
Caused by: org.apache.camel.xml.io.XmlPullParserLocationException:
Unexpected element '{http://camel.apache.org/schema/spring}handled'
in classpath:routes/camel-route.xml, line 885, column 26:


*Please help me in fixing this issue.*

-- 


*Regards,*
*Bikash Kaushik*

FW: Empty body in received email

[Voorst, Harro van]

Hello again,

I still have the problem described below. No body content when I process a 
received email with Apache Camel.

I am working on Windows 11 laptop, with Intellij. Like I said, the same setup 
with Greenmail is working when I use Spring Integration.

Please, if someone has an idea how to fix this, let me know.

Regards,
Harro

From: Voorst, Harro van
Sent: Monday, May 27, 2024 08:12
To: users@camel.apache.org
Subject: Empty body in received email

Hello,

I am using Apache Camel mail 4.4.2. to read email messages from an inbox. The 
body of the emails are always empty (zero length String ""). The sender's 
address and the receiver's are there, as is the subject.

I use Greenmail as mail server in my tests, and I send test emails using 
Roundcube. This setup is working when I use Spring Integration to receive 
emails, i.e. the body of the received email is not empty. But I want to use 
Apache Camel instead.

Attached is my code. Please have a look and advise me on how to proceed.

Cheers,
Harro



Disclaimer
Dit bericht met eventuele bijlagen is vertrouwelijk en uitsluitend bestemd voor 
de geadresseerde. Indien u niet de bedoelde ontvanger bent, wordt u verzocht de 
afzender te waarschuwen en dit bericht met eventuele bijlagen direct te 
verwijderen en/of te vernietigen. Het is niet toegestaan dit bericht en 
eventuele bijlagen te vermenigvuldigen, door te sturen, openbaar te maken, op 
te slaan of op andere wijze te gebruiken. Ordina Holding B.V. en/of haar 
groepsmaatschappijen accepteren geen verantwoordelijkheid of aansprakelijkheid 
voor schade die voortvloeit uit de inhoud en/of de verzending van dit bericht.

This e-mail and any attachments are confidential and are solely intended for 
the addressee. If you are not the intended recipient, please notify the sender 
and delete and/or destroy this message and any attachments immediately. It is 
prohibited to copy, to distribute, to disclose or to use this e-mail and any 
attachments in any other way. Ordina Holding B.V. and/or its group companies do 
not accept any responsibility nor liability for any damage resulting from the 
content of and/or the transmission of this message.
<>

RE: Empty body in received email

[Voorst, Harro van]

Hi Stephan,

Thanks for your response. Yes, I tried all kinds of bodies, with : and without. 
One line, multiple lines etc. But it is always empty.

Regards,
Harro

-Original Message-
From: Siano, Stephan 
Sent: Monday, May 27, 2024 13:30
To: users@camel.apache.org
Subject: RE: Empty body in received email

Hi Harro,

I looked into your example. It seems that the body is of the : 
\n:.
Do you face the same issue with different bodies (e.g. "anything without a 
colon")?

Maybe some component here (e.g. the mail server, the camel-mail component or 
the mail server) misinterpret your body as additional headers.

Best regards
Stephan

-Original Message-
From: Voorst, Harro van 
Sent: Monday, 27 May 2024 13:24
To: users@camel.apache.org
Subject: RE: Empty body in received email

[You don't often get email from harro.van.voo...@ordina.nl.invalid. Learn why 
this is important at https://aka.ms/LearnAboutSenderIdentification ]

Hi Federico,

I changed the from clause to what you suggested. But I still get the empty body.

Regards,

Harro

-Original Message-
From: Federico Mariani 
Sent: Monday, May 27, 2024 09:59
To: users@camel.apache.org
Subject: Re: Empty body in received email

Hello,

I did a quick test with your reproducer using an in-memory Apache James Mail 
Server, and it is working fine, the only change I had to make was the 
following, in ImapRoute.configure I modified the *from* clause to

from("imap://" + host + ":" + port + "?username=" + username + "=" + 
password)

and in the processor, I could verify that exchange.getIn().getBody() contains 
the expected String message.

Regards,

Federico

Disclaimer
Dit bericht met eventuele bijlagen is vertrouwelijk en uitsluitend bestemd voor 
de geadresseerde. Indien u niet de bedoelde ontvanger bent, wordt u verzocht de 
afzender te waarschuwen en dit bericht met eventuele bijlagen direct te 
verwijderen en/of te vernietigen. Het is niet toegestaan dit bericht en 
eventuele bijlagen te vermenigvuldigen, door te sturen, openbaar te maken, op 
te slaan of op andere wijze te gebruiken. Ordina Holding B.V. en/of haar 
groepsmaatschappijen accepteren geen verantwoordelijkheid of aansprakelijkheid 
voor schade die voortvloeit uit de inhoud en/of de verzending van dit bericht.

This e-mail and any attachments are confidential and are solely intended for 
the addressee. If you are not the intended recipient, please notify the sender 
and delete and/or destroy this message and any attachments immediately. It is 
prohibited to copy, to distribute, to disclose or to use this e-mail and any 
attachments in any other way. Ordina Holding B.V. and/or its group companies do 
not accept any responsibility nor liability for any damage resulting from the 
content of and/or the transmission of this message.

Disclaimer
Dit bericht met eventuele bijlagen is vertrouwelijk en uitsluitend bestemd voor 
de geadresseerde. Indien u niet de bedoelde ontvanger bent, wordt u verzocht de 
afzender te waarschuwen en dit bericht met eventuele bijlagen direct te 
verwijderen en/of te vernietigen. Het is niet toegestaan dit bericht en 
eventuele bijlagen te vermenigvuldigen, door te sturen, openbaar te maken, op 
te slaan of op andere wijze te gebruiken. Ordina Holding B.V. en/of haar 
groepsmaatschappijen accepteren geen verantwoordelijkheid of aansprakelijkheid 
voor schade die voortvloeit uit de inhoud en/of de verzending van dit bericht.

This e-mail and any attachments are confidential and are solely intended for 
the addressee. If you are not the intended recipient, please notify the sender 
and delete and/or destroy this message and any attachments immediately. It is 
prohibited to copy, to distribute, to disclose or to use this e-mail and any 
attachments in any other way. Ordina Holding B.V. and/or its group companies do 
not accept any responsibility nor liability for any damage resulting from the 
content of and/or the transmission of this message.

RE: Empty body in received email

[Siano, Stephan]

Hi Harro,

I looked into your example. It seems that the body is of the : 
\n:.
Do you face the same issue with different bodies (e.g. "anything without a 
colon")?

Maybe some component here (e.g. the mail server, the camel-mail component or 
the mail server) misinterpret your body as additional headers.

Best regards
Stephan

-Original Message-
From: Voorst, Harro van  
Sent: Monday, 27 May 2024 13:24
To: users@camel.apache.org
Subject: RE: Empty body in received email

[You don't often get email from harro.van.voo...@ordina.nl.invalid. Learn why 
this is important at https://aka.ms/LearnAboutSenderIdentification ]

Hi Federico,

I changed the from clause to what you suggested. But I still get the empty body.

Regards,

Harro

-Original Message-
From: Federico Mariani 
Sent: Monday, May 27, 2024 09:59
To: users@camel.apache.org
Subject: Re: Empty body in received email

Hello,

I did a quick test with your reproducer using an in-memory Apache James Mail 
Server, and it is working fine, the only change I had to make was the 
following, in ImapRoute.configure I modified the *from* clause to

from("imap://" + host + ":" + port + "?username=" + username + "=" + 
password)

and in the processor, I could verify that exchange.getIn().getBody() contains 
the expected String message.

Regards,

Federico

Disclaimer
Dit bericht met eventuele bijlagen is vertrouwelijk en uitsluitend bestemd voor 
de geadresseerde. Indien u niet de bedoelde ontvanger bent, wordt u verzocht de 
afzender te waarschuwen en dit bericht met eventuele bijlagen direct te 
verwijderen en/of te vernietigen. Het is niet toegestaan dit bericht en 
eventuele bijlagen te vermenigvuldigen, door te sturen, openbaar te maken, op 
te slaan of op andere wijze te gebruiken. Ordina Holding B.V. en/of haar 
groepsmaatschappijen accepteren geen verantwoordelijkheid of aansprakelijkheid 
voor schade die voortvloeit uit de inhoud en/of de verzending van dit bericht.

This e-mail and any attachments are confidential and are solely intended for 
the addressee. If you are not the intended recipient, please notify the sender 
and delete and/or destroy this message and any attachments immediately. It is 
prohibited to copy, to distribute, to disclose or to use this e-mail and any 
attachments in any other way. Ordina Holding B.V. and/or its group companies do 
not accept any responsibility nor liability for any damage resulting from the 
content of and/or the transmission of this message.

RE: Empty body in received email

[Voorst, Harro van]

Hi Federico,

I changed the from clause to what you suggested. But I still get the empty body.

Regards,

Harro

-Original Message-
From: Federico Mariani 
Sent: Monday, May 27, 2024 09:59
To: users@camel.apache.org
Subject: Re: Empty body in received email

Hello,

I did a quick test with your reproducer using an in-memory Apache James Mail 
Server, and it is working fine, the only change I had to make was the 
following, in ImapRoute.configure I modified the *from* clause to

from("imap://" + host + ":" + port + "?username=" + username + "=" + 
password)

and in the processor, I could verify that exchange.getIn().getBody() contains 
the expected String message.

Regards,

Federico

Disclaimer
Dit bericht met eventuele bijlagen is vertrouwelijk en uitsluitend bestemd voor 
de geadresseerde. Indien u niet de bedoelde ontvanger bent, wordt u verzocht de 
afzender te waarschuwen en dit bericht met eventuele bijlagen direct te 
verwijderen en/of te vernietigen. Het is niet toegestaan dit bericht en 
eventuele bijlagen te vermenigvuldigen, door te sturen, openbaar te maken, op 
te slaan of op andere wijze te gebruiken. Ordina Holding B.V. en/of haar 
groepsmaatschappijen accepteren geen verantwoordelijkheid of aansprakelijkheid 
voor schade die voortvloeit uit de inhoud en/of de verzending van dit bericht.

This e-mail and any attachments are confidential and are solely intended for 
the addressee. If you are not the intended recipient, please notify the sender 
and delete and/or destroy this message and any attachments immediately. It is 
prohibited to copy, to distribute, to disclose or to use this e-mail and any 
attachments in any other way. Ordina Holding B.V. and/or its group companies do 
not accept any responsibility nor liability for any damage resulting from the 
content of and/or the transmission of this message.