[jira] [Commented] (CAMEL-17492) CamelBeanPostProcessor fails if @Producer is used in EventNotifier
[
https://issues.apache.org/jira/browse/CAMEL-17492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17483612#comment-17483612
]
Michael Rambichler commented on CAMEL-17492:
Hi [~davsclaus] the NPE is fixed. But CamelContext Autoconfigure does not spin
ab the SPI ServiceEventNotifier bean. Can you please reopen the bug.
> CamelBeanPostProcessor fails if @Producer is used in EventNotifier
> --
>
> Key: CAMEL-17492
> URL: https://issues.apache.org/jira/browse/CAMEL-17492
> Project: Camel
> Issue Type: Bug
> Components: camel-core, camel-spring-boot
>Affects Versions: 3.12.0, 3.13.0, 3.14.0
>Reporter: Michael Rambichler
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.14.1, 3.15.0
>
>
> If you use a @Produce annotation in an EventNotifier Camel fails at startup.
> *Reproducable with:* Custom EventNotifier in a plain Camel + Springboot
> Routebuilder.
> I have reproduced it with the spring boot example:
> [https://github.com/apache/camel-spring-boot-examples/tree/main/spring-boot]
> and added the EventNotifier below.
>
> Fails since Camel > 3.11
>
> Initialization of bean failed; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error post
> processing bean: testEventNotifier; nested exception is
> java.lang.NullPointerException
>
> Caused by: org.springframework.beans.factory.BeanCreationException: Error
> post processing bean: testEventNotifier; nested exception is
> java.lang.NullPointerException
> at
> org.apache.camel.spring.spi.CamelBeanPostProcessor.postProcessBeforeInitialization(CamelBeanPostProcessor.java:160)
> ~[camel-spring-3.14.0.jar:3.14.0]
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:440)
> ~[spring-beans-5.3.14.jar:5.3.14]
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1796)
> ~[spring-beans-5.3.14.jar:5.3.14]
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:620)
> ~[spring-beans-5.3.14.jar:5.3.14]
> ... 122 common frames omitted
>
>
> *Example*
> [https://github.com/apache/camel-spring-boot-examples/tree/main/spring-boot]
> and added the EventNotifier below.
> {{TestEventNotifier.java}}
>
> {{@Component}}
> {{public class TestEventNotifier extends EventNotifierSupport {}}
> {{ @Produce("stream:out")}}
> {{ TestProducer producer;}}
> {{ @Override}}
> {{ public void notify(CamelEvent event) throws Exception {}}
> {{ System.err.println(event);}}
> {{ //producer.publish("some notification");}}
> {{ }}}
> {{}}}
> {{---}}
> {{TestProducer.java:}}
> {{import org.apache.camel.InOnly;}}
> {{@InOnly}}
> {{public interface TestProducer {}}
> {{ void publish(String event);}}
> {{}}}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (CAMEL-17554) camel-quickfix - lazy-create-engines option is not working
[
https://issues.apache.org/jira/browse/CAMEL-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-17554:
Fix Version/s: 3.14.2
> camel-quickfix - lazy-create-engines option is not working
> --
>
> Key: CAMEL-17554
> URL: https://issues.apache.org/jira/browse/CAMEL-17554
> Project: Camel
> Issue Type: Bug
> Components: camel-quickfix
>Affects Versions: 3.14.0
>Reporter: Alexander Anpilov
>Priority: Minor
> Fix For: 3.14.2
>
>
> After upgrade to camel-3.14.0 for checking
> https://issues.apache.org/jira/browse/CAMEL-17190 i have founded that this
> option is not working:
> camel.component.quickfix.lazy-create-engines=true
> In logs i can see:
> INFO o.a.c.c.quickfixj.QuickfixjComponent - QuickFIX/J engine: \{...} will
> start lazily
> After starting route that consumes from("quickfix") QuickFIX/J engine is not
> started.
> After manual stop|start route, engine starting, but not on startup.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (CAMEL-17554) camel-quickfix - lazy-create-engines option is not working
[
https://issues.apache.org/jira/browse/CAMEL-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-17554:
Fix Version/s: 3.16.0
> camel-quickfix - lazy-create-engines option is not working
> --
>
> Key: CAMEL-17554
> URL: https://issues.apache.org/jira/browse/CAMEL-17554
> Project: Camel
> Issue Type: Bug
> Components: camel-quickfix
>Affects Versions: 3.14.0
>Reporter: Alexander Anpilov
>Priority: Minor
> Fix For: 3.14.2, 3.16.0
>
>
> After upgrade to camel-3.14.0 for checking
> https://issues.apache.org/jira/browse/CAMEL-17190 i have founded that this
> option is not working:
> camel.component.quickfix.lazy-create-engines=true
> In logs i can see:
> INFO o.a.c.c.quickfixj.QuickfixjComponent - QuickFIX/J engine: \{...} will
> start lazily
> After starting route that consumes from("quickfix") QuickFIX/J engine is not
> started.
> After manual stop|start route, engine starting, but not on startup.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (CAMEL-17557) undertow-spring-security camel-spring-boot-examples is broken
[
https://issues.apache.org/jira/browse/CAMEL-17557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-17557:
Issue Type: Task (was: Bug)
> undertow-spring-security camel-spring-boot-examples is broken
> -
>
> Key: CAMEL-17557
> URL: https://issues.apache.org/jira/browse/CAMEL-17557
> Project: Camel
> Issue Type: Task
> Components: camel-spring-boot, examples
>Reporter: Freeman Yue Fang
>Assignee: Freeman Yue Fang
>Priority: Minor
> Fix For: 3.15.0
>
>
> Error like
> {code}
> org.apache.camel.FailedToCreateRouteException: Failed to create route route1
> at: >>> Transform[simple{Hello
> ${in.header.org.apache.camel.component.spring.security.SpringSecurityProvider_principal}!}]
> <<< in route:
> Route(route1)[From[undertow:http://localhost:8082/hi?allowed... because of No
> language could be found for: bean
> at
> org.apache.camel.reifier.RouteReifier.doCreateRoute(RouteReifier.java:240)
> ~[camel-core-reifier-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.reifier.RouteReifier.createRoute(RouteReifier.java:74)
> ~[camel-core-reifier-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.impl.DefaultModelReifierFactory.createRoute(DefaultModelReifierFactory.java:49)
> ~[camel-core-engine-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:868)
> ~[camel-core-engine-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:758)
> ~[camel-core-engine-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.impl.engine.AbstractCamelContext.doInit(AbstractCamelContext.java:2901)
> ~[camel-base-engine-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.support.service.BaseService.init(BaseService.java:83)
> ~[camel-api-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.impl.engine.AbstractCamelContext.init(AbstractCamelContext.java:2585)
> ~[camel-base-engine-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.support.service.BaseService.start(BaseService.java:111)
> ~[camel-api-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.impl.engine.AbstractCamelContext.start(AbstractCamelContext.java:2604)
> ~[camel-base-engine-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:247)
> ~[camel-core-engine-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.spring.SpringCamelContext.start(SpringCamelContext.java:119)
> ~[camel-spring-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:151)
> ~[camel-spring-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:176)
> ~[spring-context-5.3.15.jar:5.3.15]
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:169)
> ~[spring-context-5.3.15.jar:5.3.15]
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:143)
> ~[spring-context-5.3.15.jar:5.3.15]
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:421)
> ~[spring-context-5.3.15.jar:5.3.15]
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:378)
> ~[spring-context-5.3.15.jar:5.3.15]
> at
> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:938)
> ~[spring-context-5.3.15.jar:5.3.15]
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:586)
> ~[spring-context-5.3.15.jar:5.3.15]
> at
> org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:145)
> ~[spring-boot-2.6.3.jar:2.6.3]
> at
> org.springframework.boot.SpringApplication.refresh(SpringApplication.java:732)
> ~[spring-boot-2.6.3.jar:2.6.3]
> at
> org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:414)
> ~[spring-boot-2.6.3.jar:2.6.3]
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:302)
> ~[spring-boot-2.6.3.jar:2.6.3]
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:1303)
>
[jira] [Updated] (CAMEL-17558) camel-salesforce: don't complain about missing credentials with lazy login
[jira] [Updated] (CAMEL-17558) camel-salesforce: don't complain about missing credentials with lazy login
[ https://issues.apache.org/jira/browse/CAMEL-17558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-17558: Fix Version/s: 3.14.2 > camel-salesforce: don't complain about missing credentials with lazy login > -- > > Key: CAMEL-17558 > URL: https://issues.apache.org/jira/browse/CAMEL-17558 > Project: Camel > Issue Type: Bug > Components: camel-salesforce >Affects Versions: 3.14.1 >Reporter: Jeremy Ross >Assignee: Jeremy Ross >Priority: Minor > Fix For: 3.14.2 > > > When using lazy login, we shouldn't validate credentials at start up. > Instead, give the application a chance to retrieve the credentials prior to > invoking a salesforce operation. > Workaround is to provide bogus credentials at startup. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17500) Make dynamic router eip component subscription easier
[
https://issues.apache.org/jira/browse/CAMEL-17500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17483592#comment-17483592
]
Claus Ibsen commented on CAMEL-17500:
-
I assume this work is complete so we can resolve this ticket.
And if there is more work then create a new ticket for 3.16.0 release.
> Make dynamic router eip component subscription easier
> -
>
> Key: CAMEL-17500
> URL: https://issues.apache.org/jira/browse/CAMEL-17500
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, eip
>Reporter: Steve Storck
>Assignee: Steve Storck
>Priority: Minor
> Fix For: 3.15.0
>
>
> {*}User Story{*}:
> As a user of the Dynamic Router EIP component, I want to be able to subscribe
> with URL parameters so that I am not required to create a control message
> POJO to send as the message body.
> {*}Description / Explanation{*}:
> While a control channel POJO gives full control over the subscription or
> unsubscription, it would be more convenient to be able to send these messages
> from a routing participant by using URL parameters. Creating the control
> channel message for subscription looks like this:
> {code:java}
> DynamicRouterControlMessage billingSubMsg = new SubscribeMessageBuilder()
> .id("billingSubscription")
> .channel("billing")
> .priority(10)
> .endpointUri(myBillingNotificationUri)
> .predicate(new SomeBillingPredicate())
> .build(); {code}
> Then this is sent to the dynamic router control channel by:
> {code:java}
> template.sendBody("dynamic-router:control", billingSubMsg);{code}
> The above could be simplified and combined by using the URI to specify the
> message:
> {code:java}
> template.sendBody("dynamic-router:control/subscribe/billing?subscriptionId=billingSubscription=jms:billing=10=${bodyAs(String)}
> regex '^\\d*[02468]$'");{code}
> Alternatives can include:
> * Creating a {{Predicate}} as a bean, and referencing that bean as the
> {{predicate}}
> * Instantiating a {{Predicate}} and sending that predicate as the message
> body
> * Omitting the {{subscriptionId}} parameter, so that a subscription ID is
> generated and returned
> Similarly, unsubscribing can be achieved by:
>
> {code:java}
> template.sendBody("dynamic-router:control/unsubscribe/billing?subscriptionId=billingSubscription);{code}
>
> {*}Acceptance Criteria{*}:
> # Subscribing with all URI params:
> ** given: All necessary dependencies present for setting up a route with the
> dynamic router component
> ** when: Routing participant sends empty message body to the dynamic router
> with the subscription URI beginning with
> "dynamic-router:control/subscribe/\{channel name}" and all other params
> ** then: Routing participant is subscribed with all supplied values
> # Unsubscribing:
> ** given: All necessary dependencies present for setting up a route with the
> dynamic router component, and routing participant has a valid subscription ID
> and channel name
> ** when: Routing participant sends empty message body to the dynamic router
> with the subscription URI beginning with
> "dynamic-router:control/unsubscribe/\{channel name}" and the subscription ID
> ** then: Routing participant is unsubscribed for that channel and that
> subscription ID
> # Subscribing with URI params and Predicate bean:
> ** given: All necessary dependencies present for setting up a route with the
> dynamic router component, and a Predicate bean has been registered in the
> registry
> ** when: Routing participant sends an empty message to the dynamic router
> with the subscription URI beginning with
> "dynamic-router:control/subscribe/\{channel name}", the predicate parameter
> referencing the predicate bean, and all other params
> ** then: Routing participant is subscribed with all supplied values
> # Subscribing with URI params and Predicate as message body:
> ** given: All necessary dependencies present for setting up a route with the
> dynamic router component and a Predicate has been instantiated
> ** when: Routing participant sends an empty message to the dynamic router
> with the subscription URI beginning with
> "dynamic-router:control/subscribe/\{channel name}", and all other params, and
> the predicate instance is set as the message body
> ** then: Routing participant is subscribed with all supplied values
> # Subscribing with control message POJO operates without change:
> ** given: All necessary dependencies present for setting up a route with the
> dynamic router component and a control message POJO has been instantiated
> ** when: Routing participant sends subscribe POJO as message body to the
> control channel
> ** then: Routing participant is
[jira] [Commented] (CAMEL-17558) camel-salesforce: don't complain about missing credentials with lazy login
[ https://issues.apache.org/jira/browse/CAMEL-17558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17483593#comment-17483593 ] Claus Ibsen commented on CAMEL-17558: - Are you able to fix this today? > camel-salesforce: don't complain about missing credentials with lazy login > -- > > Key: CAMEL-17558 > URL: https://issues.apache.org/jira/browse/CAMEL-17558 > Project: Camel > Issue Type: Bug > Components: camel-salesforce >Affects Versions: 3.14.1 >Reporter: Jeremy Ross >Assignee: Jeremy Ross >Priority: Minor > > When using lazy login, we shouldn't validate credentials at start up. > Instead, give the application a chance to retrieve the credentials prior to > invoking a salesforce operation. > Workaround is to provide bogus credentials at startup. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17500) Make dynamic router eip component subscription easier
[
https://issues.apache.org/jira/browse/CAMEL-17500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-17500:
Fix Version/s: 3.15.0
> Make dynamic router eip component subscription easier
> -
>
> Key: CAMEL-17500
> URL: https://issues.apache.org/jira/browse/CAMEL-17500
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, eip
>Reporter: Steve Storck
>Assignee: Steve Storck
>Priority: Minor
> Fix For: 3.15.0
>
>
> {*}User Story{*}:
> As a user of the Dynamic Router EIP component, I want to be able to subscribe
> with URL parameters so that I am not required to create a control message
> POJO to send as the message body.
> {*}Description / Explanation{*}:
> While a control channel POJO gives full control over the subscription or
> unsubscription, it would be more convenient to be able to send these messages
> from a routing participant by using URL parameters. Creating the control
> channel message for subscription looks like this:
> {code:java}
> DynamicRouterControlMessage billingSubMsg = new SubscribeMessageBuilder()
> .id("billingSubscription")
> .channel("billing")
> .priority(10)
> .endpointUri(myBillingNotificationUri)
> .predicate(new SomeBillingPredicate())
> .build(); {code}
> Then this is sent to the dynamic router control channel by:
> {code:java}
> template.sendBody("dynamic-router:control", billingSubMsg);{code}
> The above could be simplified and combined by using the URI to specify the
> message:
> {code:java}
> template.sendBody("dynamic-router:control/subscribe/billing?subscriptionId=billingSubscription=jms:billing=10=${bodyAs(String)}
> regex '^\\d*[02468]$'");{code}
> Alternatives can include:
> * Creating a {{Predicate}} as a bean, and referencing that bean as the
> {{predicate}}
> * Instantiating a {{Predicate}} and sending that predicate as the message
> body
> * Omitting the {{subscriptionId}} parameter, so that a subscription ID is
> generated and returned
> Similarly, unsubscribing can be achieved by:
>
> {code:java}
> template.sendBody("dynamic-router:control/unsubscribe/billing?subscriptionId=billingSubscription);{code}
>
> {*}Acceptance Criteria{*}:
> # Subscribing with all URI params:
> ** given: All necessary dependencies present for setting up a route with the
> dynamic router component
> ** when: Routing participant sends empty message body to the dynamic router
> with the subscription URI beginning with
> "dynamic-router:control/subscribe/\{channel name}" and all other params
> ** then: Routing participant is subscribed with all supplied values
> # Unsubscribing:
> ** given: All necessary dependencies present for setting up a route with the
> dynamic router component, and routing participant has a valid subscription ID
> and channel name
> ** when: Routing participant sends empty message body to the dynamic router
> with the subscription URI beginning with
> "dynamic-router:control/unsubscribe/\{channel name}" and the subscription ID
> ** then: Routing participant is unsubscribed for that channel and that
> subscription ID
> # Subscribing with URI params and Predicate bean:
> ** given: All necessary dependencies present for setting up a route with the
> dynamic router component, and a Predicate bean has been registered in the
> registry
> ** when: Routing participant sends an empty message to the dynamic router
> with the subscription URI beginning with
> "dynamic-router:control/subscribe/\{channel name}", the predicate parameter
> referencing the predicate bean, and all other params
> ** then: Routing participant is subscribed with all supplied values
> # Subscribing with URI params and Predicate as message body:
> ** given: All necessary dependencies present for setting up a route with the
> dynamic router component and a Predicate has been instantiated
> ** when: Routing participant sends an empty message to the dynamic router
> with the subscription URI beginning with
> "dynamic-router:control/subscribe/\{channel name}", and all other params, and
> the predicate instance is set as the message body
> ** then: Routing participant is subscribed with all supplied values
> # Subscribing with control message POJO operates without change:
> ** given: All necessary dependencies present for setting up a route with the
> dynamic router component and a control message POJO has been instantiated
> ** when: Routing participant sends subscribe POJO as message body to the
> control channel
> ** then: Routing participant is subscribed with all supplied values
> # Unsubscribing with control message POJO operates without change:
> ** given: All necessary dependencies
[jira] [Updated] (CAMEL-17560) camel-yaml-dsl - Remove deprecated spec/flow from loader
[ https://issues.apache.org/jira/browse/CAMEL-17560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-17560: Priority: Minor (was: Major) > camel-yaml-dsl - Remove deprecated spec/flow from loader > > > Key: CAMEL-17560 > URL: https://issues.apache.org/jira/browse/CAMEL-17560 > Project: Camel > Issue Type: Task > Components: camel-yaml-dsl >Reporter: Claus Ibsen >Priority: Minor > Fix For: 3.16.0 > > > See PR > https://github.com/apache/camel-kamelets/pull/750 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17560) camel-yaml-dsl - Remove deprecated spec/flow from loader
[ https://issues.apache.org/jira/browse/CAMEL-17560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17483590#comment-17483590 ] Claus Ibsen commented on CAMEL-17560: - We need a new camel-kamelet release that has migrated, before we can do this. > camel-yaml-dsl - Remove deprecated spec/flow from loader > > > Key: CAMEL-17560 > URL: https://issues.apache.org/jira/browse/CAMEL-17560 > Project: Camel > Issue Type: Task > Components: camel-yaml-dsl >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.16.0 > > > See PR > https://github.com/apache/camel-kamelets/pull/750 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17560) camel-yaml-dsl - Remove deprecated spec/flow from loader
[ https://issues.apache.org/jira/browse/CAMEL-17560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-17560: Fix Version/s: 3.16.0 (was: 3.15.0) > camel-yaml-dsl - Remove deprecated spec/flow from loader > > > Key: CAMEL-17560 > URL: https://issues.apache.org/jira/browse/CAMEL-17560 > Project: Camel > Issue Type: Task > Components: camel-yaml-dsl >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.16.0 > > > See PR > https://github.com/apache/camel-kamelets/pull/750 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17560) camel-yaml-dsl - Remove deprecated spec/flow from loader
Claus Ibsen created CAMEL-17560: --- Summary: camel-yaml-dsl - Remove deprecated spec/flow from loader Key: CAMEL-17560 URL: https://issues.apache.org/jira/browse/CAMEL-17560 Project: Camel Issue Type: Task Components: camel-yaml-dsl Reporter: Claus Ibsen Fix For: 3.15.0 See PR https://github.com/apache/camel-kamelets/pull/750 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17321) Add HuaweiCloud FaceRecognitionService(FRS) Component
[ https://issues.apache.org/jira/browse/CAMEL-17321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-17321. - Resolution: Fixed > Add HuaweiCloud FaceRecognitionService(FRS) Component > - > > Key: CAMEL-17321 > URL: https://issues.apache.org/jira/browse/CAMEL-17321 > Project: Camel > Issue Type: New Feature >Reporter: Hokutor >Priority: Major > Fix For: 3.15.0 > > > Add HuaweiCloud FaceRecognitionService(FRS) Component. The service > introduction is here: > https://support.huaweicloud.com/intl/en-us/productdesc-face/face_01_0001.html > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17556) camel-aws-2-ses: add configuration set parameter
[ https://issues.apache.org/jira/browse/CAMEL-17556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Billy Jaime Beltran resolved CAMEL-17556. - Fix Version/s: 3.15.0 (was: Future) Resolution: Fixed > camel-aws-2-ses: add configuration set parameter > > > Key: CAMEL-17556 > URL: https://issues.apache.org/jira/browse/CAMEL-17556 > Project: Camel > Issue Type: Improvement > Components: camel-aws2 >Affects Versions: 3.14.0 >Reporter: Billy Jaime Beltran >Priority: Major > Labels: pull-request-available > Fix For: 3.15.0 > > > Currently you cannot set the configuration set parameter. > This should be configurable. > > > Fixes a use case we have where we need to always send a configuration set > with every request to SES. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17559) camel-file: investigate performance improvements
[
https://issues.apache.org/jira/browse/CAMEL-17559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17483406#comment-17483406
]
Otavio Rodolfo Piske commented on CAMEL-17559:
--
On a different tree with more files and depths (note that this one is in ms):
{code:java}
Benchmark Mode Cnt Score Error Units
MyBenchmark.testNewIo avgt 15 7312.966 ± 79.059 ms/op
MyBenchmark.testNewIoWithStream avgt 15 7474.397 ± 130.335 ms/op
MyBenchmark.testNewIoWithTraverse avgt 15 8491.756 ± 123.993 ms/op
MyBenchmark.testOldIo avgt 15 8699.885 ± 128.870 ms/op{code}
> camel-file: investigate performance improvements
>
>
> Key: CAMEL-17559
> URL: https://issues.apache.org/jira/browse/CAMEL-17559
> Project: Camel
> Issue Type: Improvement
> Components: camel-file
>Reporter: Otavio Rodolfo Piske
>Priority: Major
>
> While working on CAMEL-15562, with a very large directory tree, I noticed
> that sometimes it tends to perform a bit poorly when traversing very large
> directory trees.
> I think we could explore migrating some of the camel-file code to use newer
> (and, sometimes better/faster) I/O APIs to improve the
> performance/scalability for extreme use cases.
> Simulating the way Camel works now and comparing with some alternatives,
> indicates that there can be some possible performance gains (testOldIo is the
> current way the code works).
> Testing in not-so-large directory with 100k files (10 directories with 10k
> files within each):
> {code:java}
> Java 17
> Benchmark Mode Cnt Score Error Units
> MyBenchmark.testNewIo avgt 15 29468.995 ± 653.226 us/op
> MyBenchmark.testNewIoWithStream avgt 15 29563.389 ± 462.856 us/op
> MyBenchmark.testNewIoWithTraverse avgt 15 145232.034 ± 1467.996 us/op
> MyBenchmark.testOldIo avgt 15 44147.684 ± 723.055
> us/op{code}
>
> {code:java}
> Java 11
> Benchmark Mode Cnt Score Error Units
> MyBenchmark.testNewIo avgt 15 29471.651 ± 1105.507 us/op
> MyBenchmark.testNewIoWithStream avgt 15 28745.984 ± 616.324 us/op
> MyBenchmark.testNewIoWithTraverse avgt 15 149459.744 ± 2185.104 us/op
> MyBenchmark.testOldIo avgt 15 44486.002 ± 487.449 us/op
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (CAMEL-17559) camel-file: investigate performance improvements
[
https://issues.apache.org/jira/browse/CAMEL-17559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske updated CAMEL-17559:
-
Description:
While working on CAMEL-15562, with a very large directory tree, I noticed that
sometimes it tends to perform a bit poorly when traversing very large directory
trees.
I think we could explore migrating some of the camel-file code to use newer
(and, sometimes better/faster) I/O APIs to improve the performance/scalability
for extreme use cases.
Simulating the way Camel works now and comparing with some alternatives,
indicates that there can be some possible performance gains (testOldIo is the
current way the code works).
Testing in not-so-large directory with 100k files (10 directories with 10k
files within each):
{code:java}
Java 17
Benchmark Mode Cnt Score Error Units
MyBenchmark.testNewIo avgt 15 29468.995 ± 653.226 us/op
MyBenchmark.testNewIoWithStream avgt 15 29563.389 ± 462.856 us/op
MyBenchmark.testNewIoWithTraverse avgt 15 145232.034 ± 1467.996 us/op
MyBenchmark.testOldIo avgt 15 44147.684 ± 723.055 us/op{code}
{code:java}
Java 11
Benchmark Mode Cnt Score Error Units
MyBenchmark.testNewIo avgt 15 29471.651 ± 1105.507 us/op
MyBenchmark.testNewIoWithStream avgt 15 28745.984 ± 616.324 us/op
MyBenchmark.testNewIoWithTraverse avgt 15 149459.744 ± 2185.104 us/op
MyBenchmark.testOldIo avgt 15 44486.002 ± 487.449 us/op
{code}
was:
While working on CAMEL-15562, with a very large directory tree, I noticed that
sometimes it tends to perform a bit poorly when traversing very large directory
trees.
I think we could explore migrating some of the camel-file code to use newer
(and, sometimes better/faster) I/O APIs to improve the performance/scalability
for extreme use cases.
Simulating the way Camel works now and comparing with some alternatives,
indicates that there can be some possible performance gains (testOldIo is the
current way the code works).
{code:java}
Java 17
Benchmark Mode Cnt Score Error Units
MyBenchmark.testNewIo avgt 15 29468.995 ± 653.226 us/op
MyBenchmark.testNewIoWithStream avgt 15 29563.389 ± 462.856 us/op
MyBenchmark.testNewIoWithTraverse avgt 15 145232.034 ± 1467.996 us/op
MyBenchmark.testOldIo avgt 15 44147.684 ± 723.055 us/op
{code}
> camel-file: investigate performance improvements
>
>
> Key: CAMEL-17559
> URL: https://issues.apache.org/jira/browse/CAMEL-17559
> Project: Camel
> Issue Type: Improvement
> Components: camel-file
>Reporter: Otavio Rodolfo Piske
>Priority: Major
>
> While working on CAMEL-15562, with a very large directory tree, I noticed
> that sometimes it tends to perform a bit poorly when traversing very large
> directory trees.
> I think we could explore migrating some of the camel-file code to use newer
> (and, sometimes better/faster) I/O APIs to improve the
> performance/scalability for extreme use cases.
> Simulating the way Camel works now and comparing with some alternatives,
> indicates that there can be some possible performance gains (testOldIo is the
> current way the code works).
> Testing in not-so-large directory with 100k files (10 directories with 10k
> files within each):
> {code:java}
> Java 17
> Benchmark Mode Cnt Score Error Units
> MyBenchmark.testNewIo avgt 15 29468.995 ± 653.226 us/op
> MyBenchmark.testNewIoWithStream avgt 15 29563.389 ± 462.856 us/op
> MyBenchmark.testNewIoWithTraverse avgt 15 145232.034 ± 1467.996 us/op
> MyBenchmark.testOldIo avgt 15 44147.684 ± 723.055
> us/op{code}
>
> {code:java}
> Java 11
> Benchmark Mode Cnt Score Error Units
> MyBenchmark.testNewIo avgt 15 29471.651 ± 1105.507 us/op
> MyBenchmark.testNewIoWithStream avgt 15 28745.984 ± 616.324 us/op
> MyBenchmark.testNewIoWithTraverse avgt 15 149459.744 ± 2185.104 us/op
> MyBenchmark.testOldIo avgt 15 44486.002 ± 487.449 us/op
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (CAMEL-17559) camel-file: investigate performance improvements
Otavio Rodolfo Piske created CAMEL-17559:
Summary: camel-file: investigate performance improvements
Key: CAMEL-17559
URL: https://issues.apache.org/jira/browse/CAMEL-17559
Project: Camel
Issue Type: Improvement
Components: camel-file
Reporter: Otavio Rodolfo Piske
While working on CAMEL-15562, with a very large directory tree, I noticed that
sometimes it tends to perform a bit poorly when traversing very large directory
trees.
I think we could explore migrating some of the camel-file code to use newer
(and, sometimes better/faster) I/O APIs to improve the performance/scalability
for extreme use cases.
Simulating the way Camel works now and comparing with some alternatives,
indicates that there can be some possible performance gains (testOldIo is the
current way the code works).
{code:java}
Java 17
Benchmark Mode Cnt Score Error Units
MyBenchmark.testNewIo avgt 15 29468.995 ± 653.226 us/op
MyBenchmark.testNewIoWithStream avgt 15 29563.389 ± 462.856 us/op
MyBenchmark.testNewIoWithTraverse avgt 15 145232.034 ± 1467.996 us/op
MyBenchmark.testOldIo avgt 15 44147.684 ± 723.055 us/op
{code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (CAMEL-17558) camel-salesforce: don't complain about missing credentials with lazy login
Jeremy Ross created CAMEL-17558: --- Summary: camel-salesforce: don't complain about missing credentials with lazy login Key: CAMEL-17558 URL: https://issues.apache.org/jira/browse/CAMEL-17558 Project: Camel Issue Type: Bug Components: camel-salesforce Affects Versions: 3.14.1 Reporter: Jeremy Ross Assignee: Jeremy Ross When using lazy login, we shouldn't validate credentials at start up. Instead, give the application a chance to retrieve the credentials prior to invoking a salesforce operation. Workaround is to provide bogus credentials at startup. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17557) undertow-spring-security camel-spring-boot-examples is broken
[
https://issues.apache.org/jira/browse/CAMEL-17557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Yue Fang resolved CAMEL-17557.
--
Fix Version/s: 3.15.0
Resolution: Fixed
> undertow-spring-security camel-spring-boot-examples is broken
> -
>
> Key: CAMEL-17557
> URL: https://issues.apache.org/jira/browse/CAMEL-17557
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-boot, examples
>Reporter: Freeman Yue Fang
>Assignee: Freeman Yue Fang
>Priority: Minor
> Fix For: 3.15.0
>
>
> Error like
> {code}
> org.apache.camel.FailedToCreateRouteException: Failed to create route route1
> at: >>> Transform[simple{Hello
> ${in.header.org.apache.camel.component.spring.security.SpringSecurityProvider_principal}!}]
> <<< in route:
> Route(route1)[From[undertow:http://localhost:8082/hi?allowed... because of No
> language could be found for: bean
> at
> org.apache.camel.reifier.RouteReifier.doCreateRoute(RouteReifier.java:240)
> ~[camel-core-reifier-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.reifier.RouteReifier.createRoute(RouteReifier.java:74)
> ~[camel-core-reifier-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.impl.DefaultModelReifierFactory.createRoute(DefaultModelReifierFactory.java:49)
> ~[camel-core-engine-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:868)
> ~[camel-core-engine-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:758)
> ~[camel-core-engine-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.impl.engine.AbstractCamelContext.doInit(AbstractCamelContext.java:2901)
> ~[camel-base-engine-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.support.service.BaseService.init(BaseService.java:83)
> ~[camel-api-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.impl.engine.AbstractCamelContext.init(AbstractCamelContext.java:2585)
> ~[camel-base-engine-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.support.service.BaseService.start(BaseService.java:111)
> ~[camel-api-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.impl.engine.AbstractCamelContext.start(AbstractCamelContext.java:2604)
> ~[camel-base-engine-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:247)
> ~[camel-core-engine-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.spring.SpringCamelContext.start(SpringCamelContext.java:119)
> ~[camel-spring-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:151)
> ~[camel-spring-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:176)
> ~[spring-context-5.3.15.jar:5.3.15]
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:169)
> ~[spring-context-5.3.15.jar:5.3.15]
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:143)
> ~[spring-context-5.3.15.jar:5.3.15]
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:421)
> ~[spring-context-5.3.15.jar:5.3.15]
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:378)
> ~[spring-context-5.3.15.jar:5.3.15]
> at
> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:938)
> ~[spring-context-5.3.15.jar:5.3.15]
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:586)
> ~[spring-context-5.3.15.jar:5.3.15]
> at
> org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:145)
> ~[spring-boot-2.6.3.jar:2.6.3]
> at
> org.springframework.boot.SpringApplication.refresh(SpringApplication.java:732)
> ~[spring-boot-2.6.3.jar:2.6.3]
> at
> org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:414)
> ~[spring-boot-2.6.3.jar:2.6.3]
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:302)
> ~[spring-boot-2.6.3.jar:2.6.3]
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:1303)
>
[jira] [Assigned] (CAMEL-17557) undertow-spring-security camel-spring-boot-examples is broken
[
https://issues.apache.org/jira/browse/CAMEL-17557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Yue Fang reassigned CAMEL-17557:
Assignee: Freeman Yue Fang
Issue Type: Bug (was: Task)
Priority: Minor (was: Major)
> undertow-spring-security camel-spring-boot-examples is broken
> -
>
> Key: CAMEL-17557
> URL: https://issues.apache.org/jira/browse/CAMEL-17557
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-boot, examples
>Reporter: Freeman Yue Fang
>Assignee: Freeman Yue Fang
>Priority: Minor
>
> Error like
> {code}
> org.apache.camel.FailedToCreateRouteException: Failed to create route route1
> at: >>> Transform[simple{Hello
> ${in.header.org.apache.camel.component.spring.security.SpringSecurityProvider_principal}!}]
> <<< in route:
> Route(route1)[From[undertow:http://localhost:8082/hi?allowed... because of No
> language could be found for: bean
> at
> org.apache.camel.reifier.RouteReifier.doCreateRoute(RouteReifier.java:240)
> ~[camel-core-reifier-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.reifier.RouteReifier.createRoute(RouteReifier.java:74)
> ~[camel-core-reifier-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.impl.DefaultModelReifierFactory.createRoute(DefaultModelReifierFactory.java:49)
> ~[camel-core-engine-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:868)
> ~[camel-core-engine-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:758)
> ~[camel-core-engine-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.impl.engine.AbstractCamelContext.doInit(AbstractCamelContext.java:2901)
> ~[camel-base-engine-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.support.service.BaseService.init(BaseService.java:83)
> ~[camel-api-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.impl.engine.AbstractCamelContext.init(AbstractCamelContext.java:2585)
> ~[camel-base-engine-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.support.service.BaseService.start(BaseService.java:111)
> ~[camel-api-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.impl.engine.AbstractCamelContext.start(AbstractCamelContext.java:2604)
> ~[camel-base-engine-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:247)
> ~[camel-core-engine-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.spring.SpringCamelContext.start(SpringCamelContext.java:119)
> ~[camel-spring-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:151)
> ~[camel-spring-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:176)
> ~[spring-context-5.3.15.jar:5.3.15]
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:169)
> ~[spring-context-5.3.15.jar:5.3.15]
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:143)
> ~[spring-context-5.3.15.jar:5.3.15]
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:421)
> ~[spring-context-5.3.15.jar:5.3.15]
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:378)
> ~[spring-context-5.3.15.jar:5.3.15]
> at
> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:938)
> ~[spring-context-5.3.15.jar:5.3.15]
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:586)
> ~[spring-context-5.3.15.jar:5.3.15]
> at
> org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:145)
> ~[spring-boot-2.6.3.jar:2.6.3]
> at
> org.springframework.boot.SpringApplication.refresh(SpringApplication.java:732)
> ~[spring-boot-2.6.3.jar:2.6.3]
> at
> org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:414)
> ~[spring-boot-2.6.3.jar:2.6.3]
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:302)
> ~[spring-boot-2.6.3.jar:2.6.3]
> at
>
[jira] [Created] (CAMEL-17557) undertow-spring-security camel-spring-boot-examples is broken
Freeman Yue Fang created CAMEL-17557:
Summary: undertow-spring-security camel-spring-boot-examples is
broken
Key: CAMEL-17557
URL: https://issues.apache.org/jira/browse/CAMEL-17557
Project: Camel
Issue Type: Task
Components: camel-spring-boot, examples
Reporter: Freeman Yue Fang
Error like
{code}
org.apache.camel.FailedToCreateRouteException: Failed to create route route1
at: >>> Transform[simple{Hello
${in.header.org.apache.camel.component.spring.security.SpringSecurityProvider_principal}!}]
<<< in route: Route(route1)[From[undertow:http://localhost:8082/hi?allowed...
because of No language could be found for: bean
at
org.apache.camel.reifier.RouteReifier.doCreateRoute(RouteReifier.java:240)
~[camel-core-reifier-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
at
org.apache.camel.reifier.RouteReifier.createRoute(RouteReifier.java:74)
~[camel-core-reifier-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
at
org.apache.camel.impl.DefaultModelReifierFactory.createRoute(DefaultModelReifierFactory.java:49)
~[camel-core-engine-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
at
org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:868)
~[camel-core-engine-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
at
org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:758)
~[camel-core-engine-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
at
org.apache.camel.impl.engine.AbstractCamelContext.doInit(AbstractCamelContext.java:2901)
~[camel-base-engine-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
at
org.apache.camel.support.service.BaseService.init(BaseService.java:83)
~[camel-api-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
at
org.apache.camel.impl.engine.AbstractCamelContext.init(AbstractCamelContext.java:2585)
~[camel-base-engine-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
at
org.apache.camel.support.service.BaseService.start(BaseService.java:111)
~[camel-api-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
at
org.apache.camel.impl.engine.AbstractCamelContext.start(AbstractCamelContext.java:2604)
~[camel-base-engine-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
at
org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:247)
~[camel-core-engine-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
at
org.apache.camel.spring.SpringCamelContext.start(SpringCamelContext.java:119)
~[camel-spring-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
at
org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:151)
~[camel-spring-3.15.0-SNAPSHOT.jar:3.15.0-SNAPSHOT]
at
org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:176)
~[spring-context-5.3.15.jar:5.3.15]
at
org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:169)
~[spring-context-5.3.15.jar:5.3.15]
at
org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:143)
~[spring-context-5.3.15.jar:5.3.15]
at
org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:421)
~[spring-context-5.3.15.jar:5.3.15]
at
org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:378)
~[spring-context-5.3.15.jar:5.3.15]
at
org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:938)
~[spring-context-5.3.15.jar:5.3.15]
at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:586)
~[spring-context-5.3.15.jar:5.3.15]
at
org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:145)
~[spring-boot-2.6.3.jar:2.6.3]
at
org.springframework.boot.SpringApplication.refresh(SpringApplication.java:732)
~[spring-boot-2.6.3.jar:2.6.3]
at
org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:414)
~[spring-boot-2.6.3.jar:2.6.3]
at
org.springframework.boot.SpringApplication.run(SpringApplication.java:302)
~[spring-boot-2.6.3.jar:2.6.3]
at
org.springframework.boot.SpringApplication.run(SpringApplication.java:1303)
~[spring-boot-2.6.3.jar:2.6.3]
at
org.springframework.boot.SpringApplication.run(SpringApplication.java:1292)
~[spring-boot-2.6.3.jar:2.6.3]
at
org.apache.camel.undertow.spring.boot.Application.main(Application.java:30)
~[classes/:na]
Caused by: org.apache.camel.language.simple.types.SimpleIllegalSyntaxException:
No language could be found for: bean
at
[jira] [Updated] (CAMEL-17556) camel-aws-2-ses: add configuration set parameter
[ https://issues.apache.org/jira/browse/CAMEL-17556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Billy Jaime Beltran updated CAMEL-17556: Priority: Major (was: Minor) > camel-aws-2-ses: add configuration set parameter > > > Key: CAMEL-17556 > URL: https://issues.apache.org/jira/browse/CAMEL-17556 > Project: Camel > Issue Type: Improvement > Components: camel-aws2 >Affects Versions: 3.14.0 >Reporter: Billy Jaime Beltran >Priority: Major > Labels: pull-request-available > Fix For: Future > > > Currently you cannot set the configuration set parameter. > This should be configurable. > > > Fixes a use case we have where we need to always send a configuration set > with every request to SES. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17556) camel-aws-2-ses: add configuration set parameter
[ https://issues.apache.org/jira/browse/CAMEL-17556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Billy Jaime Beltran updated CAMEL-17556: Description: Currently you cannot set the configuration set parameter. This should be configurable. Fixes a use case we have where we need to always send a configuration set with every request to SES. was: Currently you cannot set the configuration set parameter. This should be configurable. > camel-aws-2-ses: add configuration set parameter > > > Key: CAMEL-17556 > URL: https://issues.apache.org/jira/browse/CAMEL-17556 > Project: Camel > Issue Type: Improvement > Components: camel-aws2 >Affects Versions: 3.14.0 >Reporter: Billy Jaime Beltran >Priority: Minor > Labels: pull-request-available > Fix For: Future > > > Currently you cannot set the configuration set parameter. > This should be configurable. > > > Fixes a use case we have where we need to always send a configuration set > with every request to SES. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17556) camel-aws-2-ses: add configuration set parameter
[ https://issues.apache.org/jira/browse/CAMEL-17556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Billy Jaime Beltran updated CAMEL-17556: External issue URL: https://github.com/apache/camel/pull/6840 > camel-aws-2-ses: add configuration set parameter > > > Key: CAMEL-17556 > URL: https://issues.apache.org/jira/browse/CAMEL-17556 > Project: Camel > Issue Type: Improvement > Components: camel-aws2 >Affects Versions: 3.14.0 >Reporter: Billy Jaime Beltran >Priority: Minor > Labels: pull-request-available > Fix For: Future > > > Currently you cannot set the configuration set parameter. > This should be configurable. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17556) camel-aws-2-ses: add configuration set parameter
Billy Jaime Beltran created CAMEL-17556: --- Summary: camel-aws-2-ses: add configuration set parameter Key: CAMEL-17556 URL: https://issues.apache.org/jira/browse/CAMEL-17556 Project: Camel Issue Type: Improvement Components: camel-aws2 Affects Versions: 3.14.0 Reporter: Billy Jaime Beltran Fix For: Future Currently you cannot set the configuration set parameter. This should be configurable. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17500) Make dynamic router eip component subscription easier
[
https://issues.apache.org/jira/browse/CAMEL-17500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17483181#comment-17483181
]
Freeman Yue Fang commented on CAMEL-17500:
--
Fix up camel-spring-boot-examples caused by API changes here
https://github.com/apache/camel-spring-boot-examples/commit/90e1c2aedda0fabced86e04ab9e622ee0628beca
> Make dynamic router eip component subscription easier
> -
>
> Key: CAMEL-17500
> URL: https://issues.apache.org/jira/browse/CAMEL-17500
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, eip
>Reporter: Steve Storck
>Assignee: Steve Storck
>Priority: Minor
>
> {*}User Story{*}:
> As a user of the Dynamic Router EIP component, I want to be able to subscribe
> with URL parameters so that I am not required to create a control message
> POJO to send as the message body.
> {*}Description / Explanation{*}:
> While a control channel POJO gives full control over the subscription or
> unsubscription, it would be more convenient to be able to send these messages
> from a routing participant by using URL parameters. Creating the control
> channel message for subscription looks like this:
> {code:java}
> DynamicRouterControlMessage billingSubMsg = new SubscribeMessageBuilder()
> .id("billingSubscription")
> .channel("billing")
> .priority(10)
> .endpointUri(myBillingNotificationUri)
> .predicate(new SomeBillingPredicate())
> .build(); {code}
> Then this is sent to the dynamic router control channel by:
> {code:java}
> template.sendBody("dynamic-router:control", billingSubMsg);{code}
> The above could be simplified and combined by using the URI to specify the
> message:
> {code:java}
> template.sendBody("dynamic-router:control/subscribe/billing?subscriptionId=billingSubscription=jms:billing=10=${bodyAs(String)}
> regex '^\\d*[02468]$'");{code}
> Alternatives can include:
> * Creating a {{Predicate}} as a bean, and referencing that bean as the
> {{predicate}}
> * Instantiating a {{Predicate}} and sending that predicate as the message
> body
> * Omitting the {{subscriptionId}} parameter, so that a subscription ID is
> generated and returned
> Similarly, unsubscribing can be achieved by:
>
> {code:java}
> template.sendBody("dynamic-router:control/unsubscribe/billing?subscriptionId=billingSubscription);{code}
>
> {*}Acceptance Criteria{*}:
> # Subscribing with all URI params:
> ** given: All necessary dependencies present for setting up a route with the
> dynamic router component
> ** when: Routing participant sends empty message body to the dynamic router
> with the subscription URI beginning with
> "dynamic-router:control/subscribe/\{channel name}" and all other params
> ** then: Routing participant is subscribed with all supplied values
> # Unsubscribing:
> ** given: All necessary dependencies present for setting up a route with the
> dynamic router component, and routing participant has a valid subscription ID
> and channel name
> ** when: Routing participant sends empty message body to the dynamic router
> with the subscription URI beginning with
> "dynamic-router:control/unsubscribe/\{channel name}" and the subscription ID
> ** then: Routing participant is unsubscribed for that channel and that
> subscription ID
> # Subscribing with URI params and Predicate bean:
> ** given: All necessary dependencies present for setting up a route with the
> dynamic router component, and a Predicate bean has been registered in the
> registry
> ** when: Routing participant sends an empty message to the dynamic router
> with the subscription URI beginning with
> "dynamic-router:control/subscribe/\{channel name}", the predicate parameter
> referencing the predicate bean, and all other params
> ** then: Routing participant is subscribed with all supplied values
> # Subscribing with URI params and Predicate as message body:
> ** given: All necessary dependencies present for setting up a route with the
> dynamic router component and a Predicate has been instantiated
> ** when: Routing participant sends an empty message to the dynamic router
> with the subscription URI beginning with
> "dynamic-router:control/subscribe/\{channel name}", and all other params, and
> the predicate instance is set as the message body
> ** then: Routing participant is subscribed with all supplied values
> # Subscribing with control message POJO operates without change:
> ** given: All necessary dependencies present for setting up a route with the
> dynamic router component and a control message POJO has been instantiated
> ** when: Routing participant sends subscribe POJO as message body to the
> control channel
> ** then: Routing participant
[jira] [Updated] (CAMEL-17284) camel-kafka - Upgrade to kafka clients 3.1.x
[ https://issues.apache.org/jira/browse/CAMEL-17284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-17284: Summary: camel-kafka - Upgrade to kafka clients 3.1.x (was: camel-kafka - Upgrade to kafka clients 3.0.x) > camel-kafka - Upgrade to kafka clients 3.1.x > > > Key: CAMEL-17284 > URL: https://issues.apache.org/jira/browse/CAMEL-17284 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-kafka >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.15.0 > > > We should upgrade to newer kafka clients. > They should be backwards compatible and major runtimes like SB and Quarkus > is/have upgraded too. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17284) camel-kafka - Upgrade to kafka clients 3.0.x
[ https://issues.apache.org/jira/browse/CAMEL-17284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-17284. - Resolution: Fixed > camel-kafka - Upgrade to kafka clients 3.0.x > > > Key: CAMEL-17284 > URL: https://issues.apache.org/jira/browse/CAMEL-17284 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-kafka >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.15.0 > > > We should upgrade to newer kafka clients. > They should be backwards compatible and major runtimes like SB and Quarkus > is/have upgraded too. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17321) Add HuaweiCloud FaceRecognitionService(FRS) Component
[ https://issues.apache.org/jira/browse/CAMEL-17321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hokutor updated CAMEL-17321: Fix Version/s: 3.15.0 (was: 3.16.0) > Add HuaweiCloud FaceRecognitionService(FRS) Component > - > > Key: CAMEL-17321 > URL: https://issues.apache.org/jira/browse/CAMEL-17321 > Project: Camel > Issue Type: New Feature >Reporter: Hokutor >Priority: Major > Fix For: 3.15.0 > > > Add HuaweiCloud FaceRecognitionService(FRS) Component. The service > introduction is here: > https://support.huaweicloud.com/intl/en-us/productdesc-face/face_01_0001.html > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (CAMEL-17284) camel-kafka - Upgrade to kafka clients 3.0.x
[ https://issues.apache.org/jira/browse/CAMEL-17284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17483063#comment-17483063 ] Otavio Rodolfo Piske edited comment on CAMEL-17284 at 1/27/22, 10:57 AM: - I tried it and it seems the upgrade is simple. I did not find any problems on my local test. Since we want to squeeze this one for 3.15, I did the PR myself and dropped a note to [~ramu11] that I was cutting the line. As we are in a different TZ, it would be good to have some tests on CI for this and use most of the time we have. was (Author: orpiske): I tried it and it seems the upgrade is simple. I did not find any problems on my local test. Since we want to squeeze this one for 3.15, I did the PR myself and dropped a note to [~ramu11] for cutting the line. As we are in a different TZ, it would be good to have some tests on CI for this and use most of the time we have. > camel-kafka - Upgrade to kafka clients 3.0.x > > > Key: CAMEL-17284 > URL: https://issues.apache.org/jira/browse/CAMEL-17284 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-kafka >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.15.0 > > > We should upgrade to newer kafka clients. > They should be backwards compatible and major runtimes like SB and Quarkus > is/have upgraded too. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17284) camel-kafka - Upgrade to kafka clients 3.0.x
[ https://issues.apache.org/jira/browse/CAMEL-17284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17483063#comment-17483063 ] Otavio Rodolfo Piske commented on CAMEL-17284: -- I tried it and it seems the upgrade is simple. I did not find any problems on my local test. Since we want to squeeze this one for 3.15, I did the PR myself and dropped a note to [~ramu11] for cutting the line. As we are in a different TZ, it would be good to have some tests on CI for this and use most of the time we have. > camel-kafka - Upgrade to kafka clients 3.0.x > > > Key: CAMEL-17284 > URL: https://issues.apache.org/jira/browse/CAMEL-17284 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-kafka >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.15.0 > > > We should upgrade to newer kafka clients. > They should be backwards compatible and major runtimes like SB and Quarkus > is/have upgraded too. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17555) camel-core - Flag to include/exclude routes in route templates
Claus Ibsen created CAMEL-17555: --- Summary: camel-core - Flag to include/exclude routes in route templates Key: CAMEL-17555 URL: https://issues.apache.org/jira/browse/CAMEL-17555 Project: Camel Issue Type: New Feature Components: camel-core Reporter: Claus Ibsen Fix For: 3.16.0 To make route templates (aka kamelets) more flexible it can benefit that we allow to declare routes whether they should be included or excluded. This allows to parameterize these routes and therefore only include them if the template has a parameter included for this. A bit like the new doSwitch which optimizes the when and only select the one that has a parameter from the template. Now we need to come up with a good name for such an option, and should it be include/exclude, filter, or pattern or enabled/disabled or something else. We can use simple language so you can say something like: -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17554) lazy-create-engines option is not working
Alexander Anpilov created CAMEL-17554:
-
Summary: lazy-create-engines option is not working
Key: CAMEL-17554
URL: https://issues.apache.org/jira/browse/CAMEL-17554
Project: Camel
Issue Type: Bug
Components: camel-quickfix
Affects Versions: 3.14.0
Reporter: Alexander Anpilov
After upgrade to camel-3.14.0 for checking
https://issues.apache.org/jira/browse/CAMEL-17190 i have founded that this
option is not working:
camel.component.quickfix.lazy-create-engines=true
In logs i can see:
INFO o.a.c.c.quickfixj.QuickfixjComponent - QuickFIX/J engine: \{...} will
start lazily
After starting route that consumes from("quickfix") QuickFIX/J engine is not
started.
After manual stop|start route, engine starting, but not on startup.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (CAMEL-17554) camel-quickfix - lazy-create-engines option is not working
[
https://issues.apache.org/jira/browse/CAMEL-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-17554:
Summary: camel-quickfix - lazy-create-engines option is not working (was:
lazy-create-engines option is not working)
> camel-quickfix - lazy-create-engines option is not working
> --
>
> Key: CAMEL-17554
> URL: https://issues.apache.org/jira/browse/CAMEL-17554
> Project: Camel
> Issue Type: Bug
> Components: camel-quickfix
>Affects Versions: 3.14.0
>Reporter: Alexander Anpilov
>Priority: Minor
>
> After upgrade to camel-3.14.0 for checking
> https://issues.apache.org/jira/browse/CAMEL-17190 i have founded that this
> option is not working:
> camel.component.quickfix.lazy-create-engines=true
> In logs i can see:
> INFO o.a.c.c.quickfixj.QuickfixjComponent - QuickFIX/J engine: \{...} will
> start lazily
> After starting route that consumes from("quickfix") QuickFIX/J engine is not
> started.
> After manual stop|start route, engine starting, but not on startup.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
