[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=16875376#comment-16875376 ] Darius Cooper commented on CAMEL-13696: --- Created 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 > Fix For: 3.0.0, 2.25.0, 3.0.0.M4 > > Time Spent: 10m > Remaining Estimate: 0h > > 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] [Work logged] (CAMEL-13696) Upgrade to slf4j ver 1.7.26
[ https://issues.apache.org/jira/browse/CAMEL-13696?focusedWorklogId=269673=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-269673 ] ASF GitHub Bot logged work on CAMEL-13696: -- Author: ASF GitHub Bot Created on: 29/Jun/19 04:24 Start Date: 29/Jun/19 04:24 Worklog Time Spent: 10m Work Description: DariusX commented on pull request #3004: Incremented to SlfJ 1.7.26 (CAMEL-13696) URL: https://github.com/apache/camel/pull/3004 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 269673) Time Spent: 10m Remaining Estimate: 0h > 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 > > Time Spent: 10m > Remaining Estimate: 0h > > 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-12957) camel-cxf - Swagger/OpenAPI feature should not involve the Camel route
[ https://issues.apache.org/jira/browse/CAMEL-12957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16875192#comment-16875192 ] Freeman Fang commented on CAMEL-12957: -- As for OpenApiFeature(OpenApi V3), created CXF-8064 on CXF side to address this issue > camel-cxf - Swagger/OpenAPI feature should not involve the Camel route > -- > > Key: CAMEL-12957 > URL: https://issues.apache.org/jira/browse/CAMEL-12957 > Project: Camel > Issue Type: Improvement > Components: camel-cxfrs >Affects Versions: 2.22.2 >Reporter: Jens Kleine-Herzbruch >Assignee: Freeman Fang >Priority: Minor > Attachments: camel-openapi-test-swagger2feature.tar, > camel-openapi-test.zip > > > Currently, when adding Swagger2Feature or OpenApiFeature to a CXFRS endpoint, > the calls to the API descriptions go through the Camel route, ie. one has to > implement an additional Camel route in order to make those features work. > Using runAsFilter=false a call to > http://localhost:8080/services/myCamelService/openapi.json > results in a call of the Camel route with an operation "getOpenApi" > http://localhost:8080/services/myCamelServive/api-docs?url=openapi.json > results in call of the Camel route with an operation "getResource" > Using runAsFilter=true the situation improves marginally: > http://localhost:8080/services/myCamelService/openapi.json > still results in a call of the Camel route with an operation "getOpenApi" > http://localhost:8080/services/myCamelServive/api-docs?url=openapi.json > at least now shows the Swagger UI page frame but still fails to load the > actual service description since it again calls the Camel route with the > "getOpenApi" operation. > Supposedly that means the filter correctly intercepts the getResource call > but not the getOpenApi call. It would be great if this worked out of the box. > A custom implementation would still be possible by not running as a filter. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (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 resolved CAMEL-13693.
--
Resolution: Fixed
Fix Version/s: 2.25.0
> 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
> Components: camel-blueprint, camel-test
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 3.0.0, 2.25.0, 3.0.0.M4
>
>
> 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] [Resolved] (CAMEL-13642) Testing for an expected Header in a MockEndpoint doesnt happen if there is no Exchange received
[
https://issues.apache.org/jira/browse/CAMEL-13642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-13642.
-
Resolution: Fixed
Fix Version/s: (was: 2.23.0)
2.25.0
2.24.2
2.23.4
> Testing for an expected Header in a MockEndpoint doesnt happen if there is no
> Exchange received
> ---
>
> Key: CAMEL-13642
> URL: https://issues.apache.org/jira/browse/CAMEL-13642
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.21.0
>Reporter: Jonathan Vila
>Priority: Major
> Fix For: 2.23.4, 2.24.2, 2.25.0
>
>
> Context
> {quote}
> When we have a MockEndpoint that expects for any header to be received, now
> there is no error raised if there is no Exchange received.
> So , it only checks for the expression if there is an Exchange, therefore the
> test doesn't fail.
> {quote}
> Where
> {quote}MockEndpoint.expectedHeaderReceived:519
> {quote}
> Fix
> {quote}Add an assert for getReceivedExchanges > 0
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-13656) reifiers classes should be public
[ https://issues.apache.org/jira/browse/CAMEL-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13656. - Resolution: Fixed Fix Version/s: 3.0.0 > reifiers classes should be public > - > > Key: CAMEL-13656 > URL: https://issues.apache.org/jira/browse/CAMEL-13656 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Luca Burgazzoli >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.0.0, 3.0.0.M4 > > > Refiers classes are now package private that make it impossible to reuse them > for example in a custom processor factory like what it is done by Hystrix: > https://github.com/apache/camel/blob/master/components/camel-hystrix/src/main/java/org/apache/camel/component/hystrix/processor/HystrixProcessorFactory.java -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13649) Enhance documentation for twitter search of multiple words
[ https://issues.apache.org/jira/browse/CAMEL-13649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13649. - Resolution: Fixed Fix Version/s: 3.0.0.M4 3.0.0 > Enhance documentation for twitter search of multiple words > -- > > Key: CAMEL-13649 > URL: https://issues.apache.org/jira/browse/CAMEL-13649 > Project: Camel > Issue Type: Improvement > Components: camel-twitter >Reporter: Claudio Miranda >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > Time Spent: 10m > Remaining Estimate: 0h > > To search tweets with multiple words the comma is not a valid character > separator, it should use the [twitter search standard > operators|https://developer.twitter.com/en/docs/tweets/search/guides/standard-operators]. > The documentation should be changed to let users know how to use twitter > search operators. Examples of a search query: > * java OR scala > * (apache camel) AND integration > * camel -knative -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-13656) reifiers classes should be public
[ https://issues.apache.org/jira/browse/CAMEL-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-13656: --- Assignee: Claus Ibsen (was: Luca Burgazzoli) > reifiers classes should be public > - > > Key: CAMEL-13656 > URL: https://issues.apache.org/jira/browse/CAMEL-13656 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Luca Burgazzoli >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.0.0.M4 > > > Refiers classes are now package private that make it impossible to reuse them > for example in a custom processor factory like what it is done by Hystrix: > https://github.com/apache/camel/blob/master/components/camel-hystrix/src/main/java/org/apache/camel/component/hystrix/processor/HystrixProcessorFactory.java -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13657) Simpler attribute names in the XML DSL
[
https://issues.apache.org/jira/browse/CAMEL-13657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-13657.
-
Resolution: Fixed
> Simpler attribute names in the XML DSL
> --
>
> Key: CAMEL-13657
> URL: https://issues.apache.org/jira/browse/CAMEL-13657
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.0.0, 3.0.0.M4
>
>
> Some part of the DSL expose verbose properties as example, the set header
> definition, has ha setHeaderName property which leads to an XML like:
> {code:xml}
>
> {code}
> This is not wrong but the context gives enough information so it can be
> rewritten as:
> {code:xml}
>
> {code}
> Which makes it shorter and does not impact comprehension.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (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:comment-tabpanel=16874888#comment-16874888
]
Freeman Fang commented on CAMEL-13693:
--
Hi [~davsclaus],
Yes, I believe so, will do it.
Freeman
> 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
> Components: camel-blueprint, camel-test
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 3.0.0, 3.0.0.M4
>
>
> 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] [Commented] (CAMEL-13657) Simpler attribute names in the XML DSL
[
https://issues.apache.org/jira/browse/CAMEL-13657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16874887#comment-16874887
]
Claus Ibsen commented on CAMEL-13657:
-
And as well. Its only these 2 so lets migrate and it would only
be XML DSL that needs to migrate, which is easy to do anyway.
> Simpler attribute names in the XML DSL
> --
>
> Key: CAMEL-13657
> URL: https://issues.apache.org/jira/browse/CAMEL-13657
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.0.0, 3.0.0.M4
>
>
> Some part of the DSL expose verbose properties as example, the set header
> definition, has ha setHeaderName property which leads to an XML like:
> {code:xml}
>
> {code}
> This is not wrong but the context gives enough information so it can be
> rewritten as:
> {code:xml}
>
> {code}
> Which makes it shorter and does not impact comprehension.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (CAMEL-13657) Simpler attribute names in the XML DSL
[
https://issues.apache.org/jira/browse/CAMEL-13657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-13657:
---
Assignee: Claus Ibsen
> Simpler attribute names in the XML DSL
> --
>
> Key: CAMEL-13657
> URL: https://issues.apache.org/jira/browse/CAMEL-13657
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.0.0, 3.0.0.M4
>
>
> Some part of the DSL expose verbose properties as example, the set header
> definition, has ha setHeaderName property which leads to an XML like:
> {code:xml}
>
> {code}
> This is not wrong but the context gives enough information so it can be
> rewritten as:
> {code:xml}
>
> {code}
> Which makes it shorter and does not impact comprehension.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-13698) The flattern pom has broken all the maven-archetypes
[ https://issues.apache.org/jira/browse/CAMEL-13698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13698. - Resolution: Fixed > The flattern pom has broken all the maven-archetypes > > > Key: CAMEL-13698 > URL: https://issues.apache.org/jira/browse/CAMEL-13698 > Project: Camel > Issue Type: Bug > Components: tooling >Reporter: Claus Ibsen >Priority: Critical > Fix For: 3.0.0, 3.0.0.M4 > > > The archetypes dont work, > M! worked > http://repo2.maven.org/maven2/org/apache/camel/archetypes/3.0.0-M1/archetypes-3.0.0-M1.pom > M3 fails > http://repo2.maven.org/maven2/org/apache/camel/archetypes/3.0.0-M3/archetypes-3.0.0-M3.pom -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13669) camel-maven-archetype-main - To create a standalone Camel Main project
[ https://issues.apache.org/jira/browse/CAMEL-13669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13669. - Resolution: Fixed > camel-maven-archetype-main - To create a standalone Camel Main project > -- > > Key: CAMEL-13669 > URL: https://issues.apache.org/jira/browse/CAMEL-13669 > Project: Camel > Issue Type: Improvement > Components: tooling > Environment: We need a new maven archetype to create a camel main > project, a like camel-example-main. >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)
[jira] [Created] (CAMEL-13699) Add Json to Json transformation using JSLT
Hemang Ajmera created CAMEL-13699: - Summary: Add Json to Json transformation using JSLT Key: CAMEL-13699 URL: https://issues.apache.org/jira/browse/CAMEL-13699 Project: Camel Issue Type: New Feature Components: camel-jolt Reporter: Hemang Ajmera It will be really great to have an additional component camel-jslt similar to camel-jolt. This component should use [https://github.com/schibsted/jslt] library for transformation. I think JSLT is much simpler yet can do more complex transformation compared to Jolt. Please have a look at [https://github.com/schibsted/jslt/blob/master/tutorial.md] for brief tutorial. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13698) The flattern pom has broken all the maven-archetypes
Claus Ibsen created CAMEL-13698: --- Summary: The flattern pom has broken all the maven-archetypes Key: CAMEL-13698 URL: https://issues.apache.org/jira/browse/CAMEL-13698 Project: Camel Issue Type: Bug Components: tooling Reporter: Claus Ibsen Fix For: 3.0.0, 3.0.0.M4 The archetypes dont work, M! worked http://repo2.maven.org/maven2/org/apache/camel/archetypes/3.0.0-M1/archetypes-3.0.0-M1.pom M3 fails http://repo2.maven.org/maven2/org/apache/camel/archetypes/3.0.0-M3/archetypes-3.0.0-M3.pom -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-13669) camel-maven-archetype-main - To create a standalone Camel Main project
[ https://issues.apache.org/jira/browse/CAMEL-13669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-13669: --- Assignee: Claus Ibsen > camel-maven-archetype-main - To create a standalone Camel Main project > -- > > Key: CAMEL-13669 > URL: https://issues.apache.org/jira/browse/CAMEL-13669 > Project: Camel > Issue Type: Improvement > Components: tooling > Environment: We need a new maven archetype to create a camel main > project, a like camel-example-main. >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)
[jira] [Resolved] (CAMEL-13682) Wrong bean injection from OSGI
[
https://issues.apache.org/jira/browse/CAMEL-13682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-13682.
-
Resolution: Not A Bug
This is now @BeanInject work and was designed, to lookup beans of a given type
from the registry, its not really taking those osgi specifics into account with
that you setup in osgi blueprint with the component-name filtering.
> Wrong bean injection from OSGI
> --
>
> Key: CAMEL-13682
> URL: https://issues.apache.org/jira/browse/CAMEL-13682
> Project: Camel
> Issue Type: Bug
> Environment: Camel 2.16.1, Windows 10 x64, JbossFuse 6.2.1
>Reporter: Adam Ostrožlík
>Priority: Minor
> Attachments: stacktrace.log
>
>
> We issued strange behaviour with our OSGI container setup using services -
> references and injecting services into out beans using @BeanInject
> *bundle1*
> {code:java}
>
>
>
>
>
>
>
>
>
>
>
> {code}
>
> *bundle2*
> {code:java}
> interface="eu.unicorn.basse.ms.audit.api.store.AuditStore"/>
>
> {code}
> *-> injecting reference info bean*
> {code:java}
> class SomeBean {
>@BeanInject
>AuditStore auditStore;
> }
> {code}
> From this point, I would expect that OSGI serves only one specific
> implementation of interface by specifying component-name attribute but it
> does not.
> As a workaround we managed to inject the reverence using setter or specifing
> name in @BeanInject annotation - *@BeanInject("auditStore")*
> I do not know if this is normal behaviour. Please, check this.
> Camel version 2.16.1
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-13480) camel3 - docs - Cleanup reference to camel 2.x
[ https://issues.apache.org/jira/browse/CAMEL-13480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13480. - Resolution: Fixed Fix Version/s: 3.0.0.M4 > camel3 - docs - Cleanup reference to camel 2.x > -- > > Key: CAMEL-13480 > URL: https://issues.apache.org/jira/browse/CAMEL-13480 > Project: Camel > Issue Type: Task > Components: documentation >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > Time Spent: 1h > Remaining Estimate: 0h > > For Camel 3 release we should cleanup all the docs with references for Camel > 2.x version stuff, so we can start from a "fresh". As all the docs going > forward will be versioned and part of the release. > So for example if you look at Camel 3.3.0 then the docs are for this release, > and if you use Camel 3.1.0, then you can find its docs and so on. > People are welcome to help, the current set of docs are the adoc files in the > source code, which you can help cleanup and submit PRs. We love contributions -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (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:comment-tabpanel=16874739#comment-16874739
]
Claus Ibsen commented on CAMEL-13693:
-
Can we backport this to camel-2.x branch?
> 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
> Components: camel-blueprint, camel-test
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 3.0.0, 3.0.0.M4
>
>
> 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] [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
]
Claus Ibsen updated CAMEL-13693:
Fix Version/s: 3.0.0.M4
3.0.0
> 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
> Fix For: 3.0.0, 3.0.0.M4
>
>
> 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] [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
]
Claus Ibsen updated CAMEL-13693:
Component/s: camel-test
camel-blueprint
> 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
> Components: camel-blueprint, camel-test
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 3.0.0, 3.0.0.M4
>
>
> 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] [Resolved] (CAMEL-13697) URISupport - Mask accessToken and clientSecret in uri logging
[ https://issues.apache.org/jira/browse/CAMEL-13697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13697. - Resolution: Fixed Fix Version/s: 2.24.2 > URISupport - Mask accessToken and clientSecret in uri logging > - > > Key: CAMEL-13697 > URL: https://issues.apache.org/jira/browse/CAMEL-13697 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 2.24.2, 2.25.0, 3.0.0.M4 > > > We should also mask accessToken and clientSecret in uri outputs as they are > sensitive data. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13697) URISupport - Mask accessToken and clientSecret in uri logging
Claus Ibsen created CAMEL-13697: --- Summary: URISupport - Mask accessToken and clientSecret in uri logging Key: CAMEL-13697 URL: https://issues.apache.org/jira/browse/CAMEL-13697 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.0.0, 2.25.0, 3.0.0.M4 We should also mask accessToken and clientSecret in uri outputs as they are sensitive data. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13686) camel-main - Add option for verbose logging of configuration
[ https://issues.apache.org/jira/browse/CAMEL-13686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13686. - Resolution: Fixed > camel-main - Add option for verbose logging of configuration > > > Key: CAMEL-13686 > URL: https://issues.apache.org/jira/browse/CAMEL-13686 > Project: Camel > Issue Type: Improvement > Components: came-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > So end users can just set an option > camel.main.configuration-logging=true > Or something like that to get verbose INFO logging of how all these > configurations are computed so you can use that to track if something seems > not correct. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
