[jira] [Updated] (CAMEL-20458) Writing custom dev console does not work
[ https://issues.apache.org/jira/browse/CAMEL-20458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20458: Fix Version/s: 4.4.2 (was: 4.4.1) > Writing custom dev console does not work > > > Key: CAMEL-20458 > URL: https://issues.apache.org/jira/browse/CAMEL-20458 > Project: Camel > Issue Type: Bug > Components: camel-core, camel-platform-http >Affects Versions: 4.4.0 >Reporter: Ivan Kulaga >Assignee: Ivan Kulaga >Priority: Minor > Labels: help-wanted > Fix For: 4.5.0, 4.4.2 > > > There is documentation saying you can write custom @DevConsole: > [https://camel.apache.org/manual/camel-console.html#_writing_custom_dev_consoles] > Tried to copy the example from this documentation and my console was not > discovered: > [https://github.com/kulagaIA/camel-examples/tree/custom-dev-console-not-working] > I believe this happens because this cycle in > org.apache.camel.maven.packaging.SpiGeneratorMojo.java does not work as > intended: > [https://github.com/apache/camel/blob/1b8d9827dcb82e899cc5b0740f4ba9fff6b65029/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/SpiGeneratorMojo.java#L120] > It iterates specifically over @ServiceFactory annotations, while the logic > suggests it should also iterate over any annotation that is itself annotated > with @ServiceFactory . -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20540) Add RouteExchangeIn and RouteExchangeOut events
[
https://issues.apache.org/jira/browse/CAMEL-20540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17824841#comment-17824841
]
Raymond commented on CAMEL-20540:
-
To give some info on how it looks for end users:
[https://academy.dovetail.world/docs/pages/flow_manager/flow_tracing]
An exchange (or multiple exchanges) tied to a breadcrumbid are called a
transaction. Each route is a step in the transactions log where users can view
headers and body. On the background, the event notifier gets exchanges, sets
basic information to json, and that is send to Elastic. The frontend show these
directly from Elastic. The message history is thus independent if routes are
running or not.
Based on your idea of the message history I also considered wrapping the routes
in a Camel step (https://camel.apache.org/components/4.4.x/eips/step-eip.html),
and then filter the steps out from the message history. However this not going
to work. I also want to leave people make their own routes or use kamelets from
the catalog, and they don't have logical grouping by step.
> Add RouteExchangeIn and RouteExchangeOut events
> ---
>
> Key: CAMEL-20540
> URL: https://issues.apache.org/jira/browse/CAMEL-20540
> Project: Camel
> Issue Type: Wish
>Affects Versions: 4.4.0
>Reporter: Raymond
>Priority: Minor
>
> In my Camel based platform I currently use Camel 3. There, users can add a
> route or kamelet per task.
> Example:
> {code:java}
>
>
> //some task
>
>
>
>
> //some task
>
>
>
>
> //some task
>
> {code}
> I use the Event Notifier to get events to show the message that goes into
> each route. For this the event *ExchangeCreated* is used
> ([https://www.javadoc.io/doc/org.apache.camel/camel-api/latest/org/apache/camel/spi/CamelEvent.html)].
> For each route I get a copy of the message Exchange with the breadcrumbid.
> This works because the routes are connected either through:
> 1. direct-vm
> 2. vm
> 3. activemq
> Now I like to migrate to Camel 4. The issue is that direct-vm and vm aren't
> available anymore since Camel 4.0:
> [https://camel.apache.org/manual/camel-4-migration-guide.html]
> The problem is that a direct endpoint has only 1 ExchangeCreated event over
> multiple routes.
> I wish to have a RouteExchangeIn and RouteExchangeOut CamelEvent, so that I
> can still offer this functionality. The nice thing is that this then would
> work for all endpoints.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-16557) Catalog: add a free form key value map on components, dataformats, languages, etc
[ https://issues.apache.org/jira/browse/CAMEL-16557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli updated CAMEL-16557: Summary: Catalog: add a free form key value map on components, dataformats, languages, etc (was: Catalog: add a free form key value map on components) > Catalog: add a free form key value map on components, dataformats, languages, > etc > - > > Key: CAMEL-16557 > URL: https://issues.apache.org/jira/browse/CAMEL-16557 > Project: Camel > Issue Type: New Feature > Components: Catalog >Reporter: Peter Palaga >Assignee: Peter Palaga >Priority: Major > Fix For: 3.10.0 > > > Camel K would like to receive the info which Camel components are included in > a given Camel Quarkus extension, see > https://github.com/apache/camel-quarkus/issues/2368 > Adding a free form key value map for storing this and any other subproject > specific info seems to make more sense than adding dedicated attributes that > would have little to no meaning in the context of Camel Core. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20540) Add RouteExchangeIn and RouteExchangeOut events
[
https://issues.apache.org/jira/browse/CAMEL-20540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17824837#comment-17824837
]
Raymond commented on CAMEL-20540:
-
Good call on the message history. Basically, I want something very close to
this (basically the message history what goes into a route and out of route as
json).
The message history however has the same issue. I could for example check the
"ExchangeCompleted" event, instead of the "ExchangeCreated" event, but this
leaves some issues:
1. Message history logs every processing step, while for me a route is one
atomic step.
2. There is no way to determine what the beginning of the route is or not. This
is because message history doesn't have this information as it sees multiple
routes connected with the direct endpoint as one exchange.
3. Message history doesn't log "from" steps. These are the ones I'm most
interested in (just start and end of the route).
As a sidenote, I would prefer this syntax:
List messages = exchange.getHistory(){color:#cc7832};{color}
Instead of
List messages =
exchange.getProperty(Exchange.{color:#9876aa}MESSAGE_HISTORY{color}{color:#cc7832},
{color}List.{color:#cc7832}class{color}){color:#cc7832};{color}
Second syntax means you need to read the documentation, but with first you can
discover it by using Javadoc or just try to API in IntelliJ.
> Add RouteExchangeIn and RouteExchangeOut events
> ---
>
> Key: CAMEL-20540
> URL: https://issues.apache.org/jira/browse/CAMEL-20540
> Project: Camel
> Issue Type: Wish
>Affects Versions: 4.4.0
>Reporter: Raymond
>Priority: Minor
>
> In my Camel based platform I currently use Camel 3. There, users can add a
> route or kamelet per task.
> Example:
> {code:java}
>
>
> //some task
>
>
>
>
> //some task
>
>
>
>
> //some task
>
> {code}
> I use the Event Notifier to get events to show the message that goes into
> each route. For this the event *ExchangeCreated* is used
> ([https://www.javadoc.io/doc/org.apache.camel/camel-api/latest/org/apache/camel/spi/CamelEvent.html)].
> For each route I get a copy of the message Exchange with the breadcrumbid.
> This works because the routes are connected either through:
> 1. direct-vm
> 2. vm
> 3. activemq
> Now I like to migrate to Camel 4. The issue is that direct-vm and vm aren't
> available anymore since Camel 4.0:
> [https://camel.apache.org/manual/camel-4-migration-guide.html]
> The problem is that a direct endpoint has only 1 ExchangeCreated event over
> multiple routes.
> I wish to have a RouteExchangeIn and RouteExchangeOut CamelEvent, so that I
> can still offer this functionality. The nice thing is that this then would
> work for all endpoints.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20542) camel-spring-boot - Using Duration as option may fail
[ https://issues.apache.org/jira/browse/CAMEL-20542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20542. - Resolution: Fixed > camel-spring-boot - Using Duration as option may fail > - > > Key: CAMEL-20542 > URL: https://issues.apache.org/jira/browse/CAMEL-20542 > Project: Camel > Issue Type: Bug > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.4.1, 4.5.0 > > > https://github.com/dylanpiergies/camel-spring-duration-issue > https://camel.zulipchat.com/#narrow/stream/257301-camel-spring-boot/topic/camel-azure-servicebus-starter.20breaks.20Duration.20property.20bind -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20542) camel-spring-boot - Using Duration as option may fail
[ https://issues.apache.org/jira/browse/CAMEL-20542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17824808#comment-17824808 ] Claus Ibsen commented on CAMEL-20542: - Have a fix for this 2024-03-08T15:34:43.942+01:00 INFO 85752 --- [ main] org.example.Application : Configured duration is PT1H 2024-03-08T15:34:43.942+01:00 INFO 85752 --- [ main] org.example.Application : Configured inner duration is PT2H > camel-spring-boot - Using Duration as option may fail > - > > Key: CAMEL-20542 > URL: https://issues.apache.org/jira/browse/CAMEL-20542 > Project: Camel > Issue Type: Bug > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.4.1, 4.5.0 > > > https://github.com/dylanpiergies/camel-spring-duration-issue > https://camel.zulipchat.com/#narrow/stream/257301-camel-spring-boot/topic/camel-azure-servicebus-starter.20breaks.20Duration.20property.20bind -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20542) camel-spring-boot - Using Duration as option may fail
[ https://issues.apache.org/jira/browse/CAMEL-20542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20542: Fix Version/s: 4.4.1 4.5.0 (was: 4.x) > camel-spring-boot - Using Duration as option may fail > - > > Key: CAMEL-20542 > URL: https://issues.apache.org/jira/browse/CAMEL-20542 > Project: Camel > Issue Type: Bug > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.4.1, 4.5.0 > > > https://github.com/dylanpiergies/camel-spring-duration-issue > https://camel.zulipchat.com/#narrow/stream/257301-camel-spring-boot/topic/camel-azure-servicebus-starter.20breaks.20Duration.20property.20bind -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20542) camel-spring-boot - Using Duration as option may fail
[ https://issues.apache.org/jira/browse/CAMEL-20542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-20542: --- Assignee: Claus Ibsen > camel-spring-boot - Using Duration as option may fail > - > > Key: CAMEL-20542 > URL: https://issues.apache.org/jira/browse/CAMEL-20542 > Project: Camel > Issue Type: Bug > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.x > > > https://github.com/dylanpiergies/camel-spring-duration-issue > https://camel.zulipchat.com/#narrow/stream/257301-camel-spring-boot/topic/camel-azure-servicebus-starter.20breaks.20Duration.20property.20bind -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20540) Add RouteExchangeIn and RouteExchangeOut events
[
https://issues.apache.org/jira/browse/CAMEL-20540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17824799#comment-17824799
]
Claus Ibsen commented on CAMEL-20540:
-
There is also message history
> Add RouteExchangeIn and RouteExchangeOut events
> ---
>
> Key: CAMEL-20540
> URL: https://issues.apache.org/jira/browse/CAMEL-20540
> Project: Camel
> Issue Type: Wish
>Affects Versions: 4.4.0
>Reporter: Raymond
>Priority: Minor
>
> In my Camel based platform I currently use Camel 3. There, users can add a
> route or kamelet per task.
> Example:
> {code:java}
>
>
> //some task
>
>
>
>
> //some task
>
>
>
>
> //some task
>
> {code}
> I use the Event Notifier to get events to show the message that goes into
> each route. For this the event *ExchangeCreated* is used
> ([https://www.javadoc.io/doc/org.apache.camel/camel-api/latest/org/apache/camel/spi/CamelEvent.html)].
> For each route I get a copy of the message Exchange with the breadcrumbid.
> This works because the routes are connected either through:
> 1. direct-vm
> 2. vm
> 3. activemq
> Now I like to migrate to Camel 4. The issue is that direct-vm and vm aren't
> available anymore since Camel 4.0:
> [https://camel.apache.org/manual/camel-4-migration-guide.html]
> The problem is that a direct endpoint has only 1 ExchangeCreated event over
> multiple routes.
> I wish to have a RouteExchangeIn and RouteExchangeOut CamelEvent, so that I
> can still offer this functionality. The nice thing is that this then would
> work for all endpoints.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20536) Camel-AWS-Bedrock: Add the component for Bedrock Agent
[ https://issues.apache.org/jira/browse/CAMEL-20536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20536. -- Resolution: Fixed > Camel-AWS-Bedrock: Add the component for Bedrock Agent > -- > > Key: CAMEL-20536 > URL: https://issues.apache.org/jira/browse/CAMEL-20536 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.5.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20544) Camel-AWS-Bedrock-Agent: Add a consumer for polling the status of ingestion or more ingestions
Andrea Cosentino created CAMEL-20544: Summary: Camel-AWS-Bedrock-Agent: Add a consumer for polling the status of ingestion or more ingestions Key: CAMEL-20544 URL: https://issues.apache.org/jira/browse/CAMEL-20544 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.5.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20543) Camel-AWS-Bedrock-Agent: Support more operations on the producer side
Andrea Cosentino created CAMEL-20543: Summary: Camel-AWS-Bedrock-Agent: Support more operations on the producer side Key: CAMEL-20543 URL: https://issues.apache.org/jira/browse/CAMEL-20543 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.5.0 Like listing ingestionjob, create resource etc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20542) camel-spring-boot - Using Duration as option may fail
Claus Ibsen created CAMEL-20542: --- Summary: camel-spring-boot - Using Duration as option may fail Key: CAMEL-20542 URL: https://issues.apache.org/jira/browse/CAMEL-20542 Project: Camel Issue Type: Bug Components: camel-spring-boot Reporter: Claus Ibsen Fix For: 4.x https://github.com/dylanpiergies/camel-spring-duration-issue https://camel.zulipchat.com/#narrow/stream/257301-camel-spring-boot/topic/camel-azure-servicebus-starter.20breaks.20Duration.20property.20bind -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20540) Add RouteExchangeIn and RouteExchangeOut events
[
https://issues.apache.org/jira/browse/CAMEL-20540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17824716#comment-17824716
]
Raymond commented on CAMEL-20540:
-
1. I tried the ExchangeSending / ExchangeSent events, but they are not 1 to 1
mapped to routes. You can have a lot more events than expected.
2. The backlog tracer looks interesting as well, but based on the
documentation, I couldn't find out how it works and how to use it
(programmatically). The documentation lists options and operations, and then
shows how to enable it, but there are no examples. Left me a bit in the dark
tbh.
> Add RouteExchangeIn and RouteExchangeOut events
> ---
>
> Key: CAMEL-20540
> URL: https://issues.apache.org/jira/browse/CAMEL-20540
> Project: Camel
> Issue Type: Wish
>Affects Versions: 4.4.0
>Reporter: Raymond
>Priority: Minor
>
> In my Camel based platform I currently use Camel 3. There, users can add a
> route or kamelet per task.
> Example:
> {code:java}
>
>
> //some task
>
>
>
>
> //some task
>
>
>
>
> //some task
>
> {code}
> I use the Event Notifier to get events to show the message that goes into
> each route. For this the event *ExchangeCreated* is used
> ([https://www.javadoc.io/doc/org.apache.camel/camel-api/latest/org/apache/camel/spi/CamelEvent.html)].
> For each route I get a copy of the message Exchange with the breadcrumbid.
> This works because the routes are connected either through:
> 1. direct-vm
> 2. vm
> 3. activemq
> Now I like to migrate to Camel 4. The issue is that direct-vm and vm aren't
> available anymore since Camel 4.0:
> [https://camel.apache.org/manual/camel-4-migration-guide.html]
> The problem is that a direct endpoint has only 1 ExchangeCreated event over
> multiple routes.
> I wish to have a RouteExchangeIn and RouteExchangeOut CamelEvent, so that I
> can still offer this functionality. The nice thing is that this then would
> work for all endpoints.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work started] (CAMEL-20541) Include arbitrary metadata to the camel-catalog
[
https://issues.apache.org/jira/browse/CAMEL-20541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-20541 started by Luca Burgazzoli.
---
> Include arbitrary metadata to the camel-catalog
> ---
>
> Key: CAMEL-20541
> URL: https://issues.apache.org/jira/browse/CAMEL-20541
> Project: Camel
> Issue Type: Improvement
> Components: camel-catalog
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 4.x
>
>
> It would be nice to include some additional and arbitrary metadata in the
> camel-catalog, as example, for components:
> {code:json}
> {
> "component": {
> "metadata": {
> "camel.apache.org/capabilities": "tracing,metrics"
> }
> }
> {code}
> This would helps tools to gather some additional information about the
> various element of the catalog as well as generating custom catalog with
> additional information needed by 3rd party tools.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20541) Include arbitrary metadata to the camel-catalog
Luca Burgazzoli created CAMEL-20541:
---
Summary: Include arbitrary metadata to the camel-catalog
Key: CAMEL-20541
URL: https://issues.apache.org/jira/browse/CAMEL-20541
Project: Camel
Issue Type: Improvement
Components: camel-catalog
Reporter: Luca Burgazzoli
Assignee: Luca Burgazzoli
Fix For: 4.x
It would be nice to include some additional and arbitrary metadata in the
camel-catalog, as example, for components:
{code:json}
{
"component": {
"metadata": {
"camel.apache.org/capabilities": "tracing,metrics"
}
}
{code}
This would helps tools to gather some additional information about the various
element of the catalog as well as generating custom catalog with additional
information needed by 3rd party tools.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20478) camel-jms: review and split Integration tests from Unit tests
[ https://issues.apache.org/jira/browse/CAMEL-20478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske resolved CAMEL-20478. -- Fix Version/s: 4.5.0 Resolution: Fixed Resolved with the linked PRs. > camel-jms: review and split Integration tests from Unit tests > - > > Key: CAMEL-20478 > URL: https://issues.apache.org/jira/browse/CAMEL-20478 > Project: Camel > Issue Type: Test >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 4.5.0 > > > *Unit tests* > * Test component features > *Integration tests* > * Test broker features > * Test global camel features (i.e.: EIPs) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20532) camel-test-infra: singleton services should not be allowed to stop/start services manually
[ https://issues.apache.org/jira/browse/CAMEL-20532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske resolved CAMEL-20532. -- Resolution: Fixed Resolved with the linked PRs. > camel-test-infra: singleton services should not be allowed to stop/start > services manually > -- > > Key: CAMEL-20532 > URL: https://issues.apache.org/jira/browse/CAMEL-20532 > Project: Camel > Issue Type: Bug >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > > This can lead to multiple problems: > - in parallel tests, this can lead to services becoming unavailable while the > test is running > - in non-parallel tests, this can lead to loss of configuration for some > embedded services > Lastly, service lifecycle should be managed by JUnit and the JVM. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20532) camel-test-infra: singleton services should not be allowed to stop/start services manually
[ https://issues.apache.org/jira/browse/CAMEL-20532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-20532: - Fix Version/s: 4.5.0 > camel-test-infra: singleton services should not be allowed to stop/start > services manually > -- > > Key: CAMEL-20532 > URL: https://issues.apache.org/jira/browse/CAMEL-20532 > Project: Camel > Issue Type: Bug >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 4.5.0 > > > This can lead to multiple problems: > - in parallel tests, this can lead to services becoming unavailable while the > test is running > - in non-parallel tests, this can lead to loss of configuration for some > embedded services > Lastly, service lifecycle should be managed by JUnit and the JVM. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20479) camel-test-infra-artemis: delay broker configuration
[ https://issues.apache.org/jira/browse/CAMEL-20479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske resolved CAMEL-20479. -- Resolution: Fixed Resolved with the linked PRs. > camel-test-infra-artemis: delay broker configuration > - > > Key: CAMEL-20479 > URL: https://issues.apache.org/jira/browse/CAMEL-20479 > Project: Camel > Issue Type: Improvement >Affects Versions: 4.5.0 >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 4.5.0 > > > Configuring the broker in the AbstractArtemisEmbeddedService constructor is > likely unnecessary and as, in many cases, we are using a singleton instance > of the broker. > We should delay the configuration to the startup phase once we verified that > no broker has been configured. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20540) Add RouteExchangeIn and RouteExchangeOut events
[
https://issues.apache.org/jira/browse/CAMEL-20540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17824681#comment-17824681
]
Claus Ibsen commented on CAMEL-20540:
-
There is already the ExchangeSending / Sent events where you have the endpoint
(look for direct). Also you can use message history that tracks everything a
message does during routing. Or the backlog tracer.
> Add RouteExchangeIn and RouteExchangeOut events
> ---
>
> Key: CAMEL-20540
> URL: https://issues.apache.org/jira/browse/CAMEL-20540
> Project: Camel
> Issue Type: Wish
>Affects Versions: 4.4.0
>Reporter: Raymond
>Priority: Minor
>
> In my Camel based platform I currently use Camel 3. There, users can add a
> route or kamelet per task.
> Example:
> {code:java}
>
>
> //some task
>
>
>
>
> //some task
>
>
>
>
> //some task
>
> {code}
> I use the Event Notifier to get events to show the message that goes into
> each route. For this the event *ExchangeCreated* is used
> ([https://www.javadoc.io/doc/org.apache.camel/camel-api/latest/org/apache/camel/spi/CamelEvent.html)].
> For each route I get a copy of the message Exchange with the breadcrumbid.
> This works because the routes are connected either through:
> 1. direct-vm
> 2. vm
> 3. activemq
> Now I like to migrate to Camel 4. The issue is that direct-vm and vm aren't
> available anymore since Camel 4.0:
> [https://camel.apache.org/manual/camel-4-migration-guide.html]
> The problem is that a direct endpoint has only 1 ExchangeCreated event over
> multiple routes.
> I wish to have a RouteExchangeIn and RouteExchangeOut CamelEvent, so that I
> can still offer this functionality. The nice thing is that this then would
> work for all endpoints.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20537) Camel-AWS-Bedrock: Add more headers to retrieve and generate operation for Bedrock Agent Runtime
[ https://issues.apache.org/jira/browse/CAMEL-20537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17824655#comment-17824655 ] Andrea Cosentino commented on CAMEL-20537: -- https://github.com/apache/camel/pull/13411 > Camel-AWS-Bedrock: Add more headers to retrieve and generate operation for > Bedrock Agent Runtime > > > Key: CAMEL-20537 > URL: https://issues.apache.org/jira/browse/CAMEL-20537 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.5.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20537) Camel-AWS-Bedrock: Add more headers to retrieve and generate operation for Bedrock Agent Runtime
[ https://issues.apache.org/jira/browse/CAMEL-20537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20537. -- Resolution: Fixed > Camel-AWS-Bedrock: Add more headers to retrieve and generate operation for > Bedrock Agent Runtime > > > Key: CAMEL-20537 > URL: https://issues.apache.org/jira/browse/CAMEL-20537 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.5.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20540) Add RouteExchangeIn and RouteExchangeOut events
[
https://issues.apache.org/jira/browse/CAMEL-20540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20540:
Priority: Minor (was: Major)
> Add RouteExchangeIn and RouteExchangeOut events
> ---
>
> Key: CAMEL-20540
> URL: https://issues.apache.org/jira/browse/CAMEL-20540
> Project: Camel
> Issue Type: Wish
>Affects Versions: 4.4.0
>Reporter: Raymond
>Priority: Minor
>
> In my Camel based platform I currently use Camel 3. There, users can add a
> route or kamelet per task.
> Example:
> {code:java}
>
>
> //some task
>
>
>
>
> //some task
>
>
>
>
> //some task
>
> {code}
> I use the Event Notifier to get events to show the message that goes into
> each route. For this the event *ExchangeCreated* is used
> ([https://www.javadoc.io/doc/org.apache.camel/camel-api/latest/org/apache/camel/spi/CamelEvent.html)].
> For each route I get a copy of the message Exchange with the breadcrumbid.
> This works because the routes are connected either through:
> 1. direct-vm
> 2. vm
> 3. activemq
> Now I like to migrate to Camel 4. The issue is that direct-vm and vm aren't
> available anymore since Camel 4.0:
> [https://camel.apache.org/manual/camel-4-migration-guide.html]
> The problem is that a direct endpoint has only 1 ExchangeCreated event over
> multiple routes.
> I wish to have a RouteExchangeIn and RouteExchangeOut CamelEvent, so that I
> can still offer this functionality. The nice thing is that this then would
> work for all endpoints.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
