[jira] [Updated] (CAMEL-13696) Upgrade to slf4j ver 1.7.26
[ https://issues.apache.org/jira/browse/CAMEL-13696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13696: Fix Version/s: 3.0.0.M4 2.25.0 3.0.0 > Upgrade to slf4j ver 1.7.26 > --- > > Key: CAMEL-13696 > URL: https://issues.apache.org/jira/browse/CAMEL-13696 > Project: Camel > Issue Type: Improvement >Reporter: Darius Cooper >Priority: Minor > Fix For: 3.0.0, 2.25.0, 3.0.0.M4 > > > Version 1.7.25 of slf4j contains a known vulnerability. Though this might not > be easy to exploit, it results in application being flagged by monitoring > tools. > Upgrade Camel, to use the latest patch version: 1.7.26 > > For reference, see this Splunk JIRA: [https://jira.qos.ch/browse/SLF4J-430] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13696) Upgrade to slf4j ver 1.7.26
[ https://issues.apache.org/jira/browse/CAMEL-13696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16874651#comment-16874651 ] Claus Ibsen commented on CAMEL-13696: - Thanks are you working on a PR > Upgrade to slf4j ver 1.7.26 > --- > > Key: CAMEL-13696 > URL: https://issues.apache.org/jira/browse/CAMEL-13696 > Project: Camel > Issue Type: Improvement >Reporter: Darius Cooper >Priority: Minor > > Version 1.7.25 of slf4j contains a known vulnerability. Though this might not > be easy to exploit, it results in application being flagged by monitoring > tools. > Upgrade Camel, to use the latest patch version: 1.7.26 > > For reference, see this Splunk JIRA: [https://jira.qos.ch/browse/SLF4J-430] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13696) Upgrade to slf4j ver 1.7.26
Darius Cooper created CAMEL-13696: - Summary: Upgrade to slf4j ver 1.7.26 Key: CAMEL-13696 URL: https://issues.apache.org/jira/browse/CAMEL-13696 Project: Camel Issue Type: Improvement Reporter: Darius Cooper Version 1.7.25 of slf4j contains a known vulnerability. Though this might not be easy to exploit, it results in application being flagged by monitoring tools. Upgrade Camel, to use the latest patch version: 1.7.26 For reference, see this Splunk JIRA: [https://jira.qos.ch/browse/SLF4J-430] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13695) camel-core - Injector allow to create beans via static factory methods
[ https://issues.apache.org/jira/browse/CAMEL-13695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13695. - Resolution: Fixed > camel-core - Injector allow to create beans via static factory methods > -- > > Key: CAMEL-13695 > URL: https://issues.apache.org/jira/browse/CAMEL-13695 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > We should support creating beans via static factory methods that they > sometime have instead of constructors, such as > camel.component.quartz2.scheduler-factory=#class:org.quartz.impl.DirectSchedulerFactory#getInstance -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13692) Don't use ssh-rsa as the default keytype for client keys
[ https://issues.apache.org/jira/browse/CAMEL-13692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CAMEL-13692. - Resolution: Fixed > Don't use ssh-rsa as the default keytype for client keys > > > Key: CAMEL-13692 > URL: https://issues.apache.org/jira/browse/CAMEL-13692 > Project: Camel > Issue Type: Improvement > Components: camel-ssh >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0, 2.25.0 > > > By default, Camel SSH enforces that ssh-rsa is used as the default key for > clients. Instead we should just use whatever key is provided by the client, > and only enforce the type if the client specifies it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13342) Introduce JUnit 5 testing support
[ https://issues.apache.org/jira/browse/CAMEL-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-13342: --- Description: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Exploratory preparation work happens in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. was:Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. > Introduce JUnit 5 testing support > - > > Key: CAMEL-13342 > URL: https://issues.apache.org/jira/browse/CAMEL-13342 > Project: Camel > Issue Type: New Feature > Components: camel-test >Reporter: Eric Deandrea >Assignee: Alex Dettinger >Priority: Minor > > Off-shoot from CAMEL-11807 to allow building support for users to be able to > write Camel tests using JUnit 5. > > Exploratory preparation work happens in [a dedicated > branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-13342) Introduce JUnit 5 testing support
[ https://issues.apache.org/jira/browse/CAMEL-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger reassigned CAMEL-13342: -- Assignee: Alex Dettinger > Introduce JUnit 5 testing support > - > > Key: CAMEL-13342 > URL: https://issues.apache.org/jira/browse/CAMEL-13342 > Project: Camel > Issue Type: New Feature > Components: camel-test >Reporter: Eric Deandrea >Assignee: Alex Dettinger >Priority: Minor > > Off-shoot from CAMEL-11807 to allow building support for users to be able to > write Camel tests using JUnit 5. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13695) camel-core - Injector allow to create beans via static factory methods
Claus Ibsen created CAMEL-13695: --- Summary: camel-core - Injector allow to create beans via static factory methods Key: CAMEL-13695 URL: https://issues.apache.org/jira/browse/CAMEL-13695 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.0.0, 3.0.0.M4 We should support creating beans via static factory methods that they sometime have instead of constructors, such as camel.component.quartz2.scheduler-factory=#class:org.quartz.impl.DirectSchedulerFactory#getInstance -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13694) Easier way to extend PropertiesComponent
Luca Burgazzoli created CAMEL-13694:
---
Summary: Easier way to extend PropertiesComponent
Key: CAMEL-13694
URL: https://issues.apache.org/jira/browse/CAMEL-13694
Project: Camel
Issue Type: Improvement
Components: camel-properties
Reporter: Luca Burgazzoli
Fix For: 3.0.0
The current implementation of the PropertiesComponent is very oriented to paths
and location and it is not very easy to provide alternative back-ends i.e MP
Config or HashiCorp Vault.
We may need to re-think the PropertiesComponent interface and reason in term of
ordered "property sources", like:
{code}
ProertiesComponent cp = new ProertiesComponent()
cp.addSource(new ValutPropertiesSource())
cp.addSource(new PathPropertiesSource())
cp.addSource(PropertiesSource.wrap(properties))
...
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13693) avoid useOverridePropertiesWithPropertiesComponent being invoked twice when running a unit-test with OSGI Blueprint XML.
[
https://issues.apache.org/jira/browse/CAMEL-13693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang updated CAMEL-13693:
-
Priority: Minor (was: Major)
> avoid useOverridePropertiesWithPropertiesComponent being invoked twice when
> running a unit-test with OSGI Blueprint XML.
>
>
> Key: CAMEL-13693
> URL: https://issues.apache.org/jira/browse/CAMEL-13693
> Project: Camel
> Issue Type: Test
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>Priority: Minor
>
> One from
> {code}
> at
> camelinaction.BlueprintFirstTest.useOverridePropertiesWithPropertiesComponent(BlueprintFirstTest.java:56)
> at
> org.apache.camel.test.blueprint.CamelBlueprintTestSupport.createBundleContext(CamelBlueprintTestSupport.java:132)
> at
> org.apache.camel.test.blueprint.CamelBlueprintTestSupport.setUp(CamelBlueprintTestSupport.java:248)
> {code}
> one from
> {code}
> at
> org.apache.camel.test.junit4.CamelTestSupport.doSetUp(CamelTestSupport.java:368)
> at
> org.apache.camel.test.junit4.CamelTestSupport.setUp(CamelTestSupport.java:281)
> at
> org.apache.camel.test.blueprint.CamelBlueprintTestSupport.setUp(CamelBlueprintTestSupport.java:251)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13693) avoid useOverridePropertiesWithPropertiesComponent being invoked twice when running a unit-test with OSGI Blueprint XML.
Freeman Fang created CAMEL-13693:
Summary: avoid useOverridePropertiesWithPropertiesComponent being
invoked twice when running a unit-test with OSGI Blueprint XML.
Key: CAMEL-13693
URL: https://issues.apache.org/jira/browse/CAMEL-13693
Project: Camel
Issue Type: Test
Reporter: Freeman Fang
One from
{code}
at
camelinaction.BlueprintFirstTest.useOverridePropertiesWithPropertiesComponent(BlueprintFirstTest.java:56)
at
org.apache.camel.test.blueprint.CamelBlueprintTestSupport.createBundleContext(CamelBlueprintTestSupport.java:132)
at
org.apache.camel.test.blueprint.CamelBlueprintTestSupport.setUp(CamelBlueprintTestSupport.java:248)
{code}
one from
{code}
at
org.apache.camel.test.junit4.CamelTestSupport.doSetUp(CamelTestSupport.java:368)
at
org.apache.camel.test.junit4.CamelTestSupport.setUp(CamelTestSupport.java:281)
at
org.apache.camel.test.blueprint.CamelBlueprintTestSupport.setUp(CamelBlueprintTestSupport.java:251)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (CAMEL-13693) avoid useOverridePropertiesWithPropertiesComponent being invoked twice when running a unit-test with OSGI Blueprint XML.
[
https://issues.apache.org/jira/browse/CAMEL-13693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang reassigned CAMEL-13693:
Assignee: Freeman Fang
> avoid useOverridePropertiesWithPropertiesComponent being invoked twice when
> running a unit-test with OSGI Blueprint XML.
>
>
> Key: CAMEL-13693
> URL: https://issues.apache.org/jira/browse/CAMEL-13693
> Project: Camel
> Issue Type: Test
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>Priority: Major
>
> One from
> {code}
> at
> camelinaction.BlueprintFirstTest.useOverridePropertiesWithPropertiesComponent(BlueprintFirstTest.java:56)
> at
> org.apache.camel.test.blueprint.CamelBlueprintTestSupport.createBundleContext(CamelBlueprintTestSupport.java:132)
> at
> org.apache.camel.test.blueprint.CamelBlueprintTestSupport.setUp(CamelBlueprintTestSupport.java:248)
> {code}
> one from
> {code}
> at
> org.apache.camel.test.junit4.CamelTestSupport.doSetUp(CamelTestSupport.java:368)
> at
> org.apache.camel.test.junit4.CamelTestSupport.setUp(CamelTestSupport.java:281)
> at
> org.apache.camel.test.blueprint.CamelBlueprintTestSupport.setUp(CamelBlueprintTestSupport.java:251)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13692) Don't use ssh-rsa as the default keytype for client keys
Colm O hEigeartaigh created CAMEL-13692: --- Summary: Don't use ssh-rsa as the default keytype for client keys Key: CAMEL-13692 URL: https://issues.apache.org/jira/browse/CAMEL-13692 Project: Camel Issue Type: Improvement Components: camel-ssh Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 3.0.0, 2.25.0 By default, Camel SSH enforces that ssh-rsa is used as the default key for clients. Instead we should just use whatever key is provided by the client, and only enforce the type if the client specifies it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13690) camel-main - Add option to ignore unknown options
[ https://issues.apache.org/jira/browse/CAMEL-13690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13690. - Resolution: Later Lets not do this now as its a bit more dangerous as it will also ignore options that has a typo mistake etc. > camel-main - Add option to ignore unknown options > - > > Key: CAMEL-13690 > URL: https://issues.apache.org/jira/browse/CAMEL-13690 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > For example if you have OS ENV variables set that will not be in use because > a component is not being used or something. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13683) camel-main - configuring properties report better error if missing JARs on classpath
[ https://issues.apache.org/jira/browse/CAMEL-13683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13683. - Resolution: Fixed > camel-main - configuring properties report better error if missing JARs on > classpath > > > Key: CAMEL-13683 > URL: https://issues.apache.org/jira/browse/CAMEL-13683 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > Look into if we are not reporting a good error if you configure an option for > a component that is not on the classpath etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13691) Add resilience4j circuit breaker
Christoph Giera created CAMEL-13691:
---
Summary: Add resilience4j circuit breaker
Key: CAMEL-13691
URL: https://issues.apache.org/jira/browse/CAMEL-13691
Project: Camel
Issue Type: New Feature
Reporter: Christoph Giera
Hystrix is no longer in active development, netflix uses resilience4j for new
internal projects, see [https://github.com/Netflix/Hystrix#Hystrix%20Status]
Camel should also add a resilience4j component/java dsl.
Idea for java dsl: instead of adding resilience4j on the same level like
hystrix add an additional level "circuitBreaker" with the childs hystrix,
resilience4j...
{noformat}
from(endpoint)
.circuitBreaker()
.useHystrix()
.to(endpoint)
.endCircuitBreaker();{noformat}
{noformat}
from(endpoint)
.circuitBreaker()
.useResilience4j()
.to(endpoint)
.endCircuitBreaker();{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-13689) camel-core - Converting string to boolean should only accept true or false literals
[ https://issues.apache.org/jira/browse/CAMEL-13689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13689. - Resolution: Fixed > camel-core - Converting string to boolean should only accept true or false > literals > --- > > Key: CAMEL-13689 > URL: https://issues.apache.org/jira/browse/CAMEL-13689 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
