[jira] [Updated] (CAMEL-11640) SupervisingRouteController : Add a SPI to filter routes not to be supervised
[ https://issues.apache.org/jira/browse/CAMEL-11640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli updated CAMEL-11640: Summary: SupervisingRouteController : Add a SPI to filter routes not to be supervised (was: SupervisingRouteController) > SupervisingRouteController : Add a SPI to filter routes not to be supervised > > > Key: CAMEL-11640 > URL: https://issues.apache.org/jira/browse/CAMEL-11640 > Project: Camel > Issue Type: Improvement > Components: camel-core, camel-spring-boot >Reporter: Luca Burgazzoli >Assignee: Luca Burgazzoli >Priority: Minor > Labels: route-controller > Fix For: 2.20.0 > > > Add a SPI to filter routes not to be supervised -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-11640) SupervisingRouteController
Luca Burgazzoli created CAMEL-11640: --- Summary: SupervisingRouteController Key: CAMEL-11640 URL: https://issues.apache.org/jira/browse/CAMEL-11640 Project: Camel Issue Type: Improvement Components: camel-core, camel-spring-boot Reporter: Luca Burgazzoli Assignee: Luca Burgazzoli Priority: Minor Fix For: 2.20.0 Add a SPI to filter routes not to be supervised -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (CAMEL-11584) Add javadoc to spring boot auto configuration of camel.supervising.controller
[ https://issues.apache.org/jira/browse/CAMEL-11584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-11584 started by Luca Burgazzoli. --- > Add javadoc to spring boot auto configuration of camel.supervising.controller > - > > Key: CAMEL-11584 > URL: https://issues.apache.org/jira/browse/CAMEL-11584 > Project: Camel > Issue Type: Improvement > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Luca Burgazzoli > Labels: route-controller > Fix For: 2.20.0 > > > There is no javadoc for that auto configuration classes which means there is > no end user documentation in the tooling etc. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (CAMEL-11639) camel-jms - Add support for changing JMS message selector on consumer at runtime via jmx
[ https://issues.apache.org/jira/browse/CAMEL-11639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-11639. - Resolution: Fixed > camel-jms - Add support for changing JMS message selector on consumer at > runtime via jmx > > > Key: CAMEL-11639 > URL: https://issues.apache.org/jira/browse/CAMEL-11639 > Project: Camel > Issue Type: Improvement > Components: camel-jms >Reporter: Claus Ibsen >Assignee: Claus Ibsen > Fix For: 2.20.0 > > > Currently you cannot do this. However it can be changed at runtime via > spring-jms, but it requires to turn off caching, so its an advanced feature > and can be slower on the consumer -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-11639) camel-jms - Add support for changing JMS message selector on consumer at runtime via jmx
Claus Ibsen created CAMEL-11639: --- Summary: camel-jms - Add support for changing JMS message selector on consumer at runtime via jmx Key: CAMEL-11639 URL: https://issues.apache.org/jira/browse/CAMEL-11639 Project: Camel Issue Type: Improvement Components: camel-jms Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.20.0 Currently you cannot do this. However it can be changed at runtime via spring-jms, but it requires to turn off caching, so its an advanced feature and can be slower on the consumer -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11638) Upgrade to Apache SSHD 1.6.x
[
https://issues.apache.org/jira/browse/CAMEL-11638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Babak Vahdat updated CAMEL-11638:
-
Description: Currently on the master branch we make use of Apache SSHD
version {{0.14.0}} which is apparently not binary compatible with {{1.6.x}}, so
that it needs a bit of code adjustment to compile and make the tests run green.
Probably the corresponding Karaf feature needs some changes as well. (was:
Currently on the master branch we make use of Apache SSHD version {{0.14.0}}
which is apparently not binary compatible with {{1.6.x}}, so that it needs a
bit of code adjustment to compile and make the tests run green. Probably the
corresponding Karaf future needs some changes as well. )
> Upgrade to Apache SSHD 1.6.x
>
>
> Key: CAMEL-11638
> URL: https://issues.apache.org/jira/browse/CAMEL-11638
> Project: Camel
> Issue Type: Task
> Components: camel-ssh
>Reporter: Babak Vahdat
>Assignee: Babak Vahdat
>Priority: Minor
> Fix For: 2.19.3
>
>
> Currently on the master branch we make use of Apache SSHD version {{0.14.0}}
> which is apparently not binary compatible with {{1.6.x}}, so that it needs a
> bit of code adjustment to compile and make the tests run green. Probably the
> corresponding Karaf feature needs some changes as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (CAMEL-11638) Upgrade to Apache SSHD 1.6.x
Babak Vahdat created CAMEL-11638:
Summary: Upgrade to Apache SSHD 1.6.x
Key: CAMEL-11638
URL: https://issues.apache.org/jira/browse/CAMEL-11638
Project: Camel
Issue Type: Task
Components: camel-ssh
Reporter: Babak Vahdat
Assignee: Babak Vahdat
Priority: Minor
Fix For: 2.19.3
Currently on the master branch we make use of Apache SSHD version {{0.14.0}}
which is apparently not binary compatible with {{1.6.x}}, so that it needs a
bit of code adjustment to compile and make the tests run green. Probably the
corresponding Karaf future needs some changes as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CAMEL-9751) Add support for security requirements to swagger java component
[ https://issues.apache.org/jira/browse/CAMEL-9751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16115900#comment-16115900 ] Marco Santarelli commented on CAMEL-9751: - Agree with [~tdudgeon], it would be nice to have the option to specify the security requirements as defined in https://swagger.io/specification/#securitySchemeObject Swagger-UI 3+ does not allow to override headers easily anymore, and relies solely on these specs in the swagger.json to build the UI accordingly. > Add support for security requirements to swagger java component > --- > > Key: CAMEL-9751 > URL: https://issues.apache.org/jira/browse/CAMEL-9751 > Project: Camel > Issue Type: New Feature > Components: camel-swagger >Reporter: Tim Dudgeon >Priority: Minor > Fix For: 2.20.0 > > > Swagger Java component does not currently allow security requirements to be > specified. Would be useful to be able to do so. > But as security is usually applied at the container level its not clear what > the best approach would be. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11634) clean up dbcp 1 dependencies and move it (where possible) to dbcp 2
[ https://issues.apache.org/jira/browse/CAMEL-11634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16115756#comment-16115756 ] ASF GitHub Bot commented on CAMEL-11634: Github user valdar closed the pull request at: https://github.com/apache/camel/pull/1873 > clean up dbcp 1 dependencies and move it (where possible) to dbcp 2 > --- > > Key: CAMEL-11634 > URL: https://issues.apache.org/jira/browse/CAMEL-11634 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Tarocchi >Assignee: Andrea Cosentino > Fix For: 2.20.0 > > > dbcp 1 is quite old and I've noticed a couple of places where that dependency > is declared but actually never used. Would be good to have them cleaned up > and bumped to version 2 when possible. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11615) WorkerPool is null for auto-configured RxJava-based application
[ https://issues.apache.org/jira/browse/CAMEL-11615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16115684#comment-16115684 ] Claus Ibsen commented on CAMEL-11615: - Yeah I thought a bit on the same line to look at CamelSubscription so its subscribe method would only start after camel context has been started. There is ways to hook into this. Take a look at https://github.com/apache/camel/blob/master/camel-core/src/main/java/org/apache/camel/StartupListener.java And then see how its used in other Camel components and see if you can find out how to hook that into this component/subscriber. > WorkerPool is null for auto-configured RxJava-based application > --- > > Key: CAMEL-11615 > URL: https://issues.apache.org/jira/browse/CAMEL-11615 > Project: Camel > Issue Type: Bug > Components: camel-reactive-streams >Affects Versions: 2.19.1 > Environment: OS: OSX 10.11.6 > JDK: Oracle 1.8.0_141 > MVN: 3.5.0 >Reporter: Qaiser Abbasi > Fix For: 2.20.0, 2.19.3 > > > In https://github.com/qabbasi/reactive-camel-demo I'm using the > camel-reactive-streams-starter project to create a application based on > RxJava2. Currently I'm getting a NPE during runtime. > I also tried to test the sample route inside > https://github.com/apache/camel/tree/master/examples/camel-example-reactive-streams, > but unfortunately this also results in the same exception: > java.lang.NullPointerException: null > at > org.apache.camel.component.reactive.streams.engine.CamelSubscription.checkAndFlush(CamelSubscription.java:123) > ~[camel-reactive-streams-2.19.1.jar:2.19.1] > at > org.apache.camel.component.reactive.streams.engine.CamelSubscription.publish(CamelSubscription.java:247) > ~[camel-reactive-streams-2.19.1.jar:2.19.1] > at > org.apache.camel.component.reactive.streams.engine.CamelPublisher.publish(CamelPublisher.java:100) > ~[camel-reactive-streams-2.19.1.jar:2.19.1] > at > org.apache.camel.component.reactive.streams.engine.DefaultCamelReactiveStreamsService.sendCamelExchange(DefaultCamelReactiveStreamsService.java:123) > ~[camel-reactive-streams-2.19.1.jar:2.19.1] > at > org.apache.camel.component.reactive.streams.ReactiveStreamsProducer.process(ReactiveStreamsProducer.java:44) > ~[camel-reactive-streams-2.19.1.jar:2.19.1] > at > org.apache.camel.processor.SendProcessor.process(SendProcessor.java:145) > ~[camel-core-2.19.1.jar:2.19.1] > at > org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77) > ~[camel-core-2.19.1.jar:2.19.1] > at > org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:541) > ~[camel-core-2.19.1.jar:2.19.1] > at > org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:198) > [camel-core-2.19.1.jar:2.19.1] > at org.apache.camel.processor.Pipeline.process(Pipeline.java:120) > ~[camel-core-2.19.1.jar:2.19.1] > at org.apache.camel.processor.Pipeline.process(Pipeline.java:83) > ~[camel-core-2.19.1.jar:2.19.1] > at > org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:198) > [camel-core-2.19.1.jar:2.19.1] > at > org.apache.camel.component.timer.TimerConsumer.sendTimerExchange(TimerConsumer.java:197) > [camel-core-2.19.1.jar:2.19.1] > at > org.apache.camel.component.timer.TimerConsumer$1.run(TimerConsumer.java:79) > [camel-core-2.19.1.jar:2.19.1] > at java.util.TimerThread.mainLoop(Timer.java:555) [na:1.8.0_141] > at java.util.TimerThread.run(Timer.java:505) [na:1.8.0_141] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
