[jira] [Resolved] (CAMEL-13565) Why TracingInterceptor has been deprecated?
[ https://issues.apache.org/jira/browse/CAMEL-13565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13565. - Resolution: Invalid > Why TracingInterceptor has been deprecated? > --- > > Key: CAMEL-13565 > URL: https://issues.apache.org/jira/browse/CAMEL-13565 > Project: Camel > Issue Type: Wish > Components: came-core >Reporter: Pedro Henrique Calais Guerra >Priority: Major > > [https://camel.apache.org/tracer.html] > "Implementing custom tracing via TracingInterceptor has been deprecated." > Being able to customize and persoanlize the tracing logs seemed like a very > useful capability. Can anyone explain this decision? Thanks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13565) Why TracingInterceptor has been deprecated?
[ https://issues.apache.org/jira/browse/CAMEL-13565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pedro Henrique Calais Guerra updated CAMEL-13565: - Description: [https://camel.apache.org/tracer.html] "Implementing custom tracing via TracingInterceptor has been deprecated." Being able to customize and persoanlize the tracing logs seemed like a very useful capability. Can anyone explain this decision? Thanks! was: [https://camel.apache.org/tracer.html] "Implementing custom tracing via TracingInterceptor has been deprecated." Being able to customize and persoanlize the tracing logs seemed like a very useful capability. Can anyone explain this decision? Thanks! > Why TracingInterceptor has been deprecated? > --- > > Key: CAMEL-13565 > URL: https://issues.apache.org/jira/browse/CAMEL-13565 > Project: Camel > Issue Type: Wish > Components: came-core >Reporter: Pedro Henrique Calais Guerra >Priority: Major > > [https://camel.apache.org/tracer.html] > "Implementing custom tracing via TracingInterceptor has been deprecated." > Being able to customize and persoanlize the tracing logs seemed like a very > useful capability. Can anyone explain this decision? Thanks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13565) Why TracingInterceptor has been deprecated?
[ https://issues.apache.org/jira/browse/CAMEL-13565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pedro Henrique Calais Guerra updated CAMEL-13565: - Summary: Why TracingInterceptor has been deprecated? (was: Why TracingIntercepor has been deprecated?) > Why TracingInterceptor has been deprecated? > --- > > Key: CAMEL-13565 > URL: https://issues.apache.org/jira/browse/CAMEL-13565 > Project: Camel > Issue Type: Wish > Components: came-core >Reporter: Pedro Henrique Calais Guerra >Priority: Major > > [https://camel.apache.org/tracer.html] > > "Implementing custom tracing via TracingInterceptor has been deprecated." > Being able to customize and persoanlize the tracing logs seemed like a very > useful capability. Can anyone explain this decision? Thanks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13565) Why TracingIntercepor has been deprecated?
Pedro Henrique Calais Guerra created CAMEL-13565: Summary: Why TracingIntercepor has been deprecated? Key: CAMEL-13565 URL: https://issues.apache.org/jira/browse/CAMEL-13565 Project: Camel Issue Type: Wish Components: came-core Reporter: Pedro Henrique Calais Guerra [https://camel.apache.org/tracer.html] "Implementing custom tracing via TracingInterceptor has been deprecated." Being able to customize and persoanlize the tracing logs seemed like a very useful capability. Can anyone explain this decision? Thanks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13557) Support for nested properties binding
[
https://issues.apache.org/jira/browse/CAMEL-13557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846973#comment-16846973
]
Claus Ibsen commented on CAMEL-13557:
-
Got the CXF error fixed.
We should add option on component/endpoint to turn this on|off, as this can
also be used to configure endpoints with nested options.
> Support for nested properties binding
> -
>
> Key: CAMEL-13557
> URL: https://issues.apache.org/jira/browse/CAMEL-13557
> Project: Camel
> Issue Type: New Feature
> Components: came-core
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.0.0, 3.0.0-M3
>
>
> As today properties binding does not work for nested objects so assuming I
> have a class like:
> {code:java}
> class MyComponent {
>
> public void setFoo(String foo) {
> this.foo = foo;
> }
> public String getFoo() {
> return foo;
> }
> public void setConfiguration(Configuration conf) {
> this.conf = conf;
> }
> public Configuration getConfiguration() {
> return conf;
> }
> static class Configuration {
>
> public void setBar(String bar) {
> this.bar = bar
> }
> public String getBar() {
> return bar
> }
> }
> }
> {code}
> And a set of properties like:
> {code}
> myComponent.foo = "foo"
> myComponent.conf.bar = "bar"
> {code}
> Then only MyComponent.foo will be set but it would be nice if the binding
> framework could navigate the property using dot notation and set any
> dependent object.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13557) Support for nested properties binding
[
https://issues.apache.org/jira/browse/CAMEL-13557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846873#comment-16846873
]
Claus Ibsen commented on CAMEL-13557:
-
Okay there is a weird error in camel-cxf - which I need to figure out why
> Support for nested properties binding
> -
>
> Key: CAMEL-13557
> URL: https://issues.apache.org/jira/browse/CAMEL-13557
> Project: Camel
> Issue Type: New Feature
> Components: came-core
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.0.0, 3.0.0-M3
>
>
> As today properties binding does not work for nested objects so assuming I
> have a class like:
> {code:java}
> class MyComponent {
>
> public void setFoo(String foo) {
> this.foo = foo;
> }
> public String getFoo() {
> return foo;
> }
> public void setConfiguration(Configuration conf) {
> this.conf = conf;
> }
> public Configuration getConfiguration() {
> return conf;
> }
> static class Configuration {
>
> public void setBar(String bar) {
> this.bar = bar
> }
> public String getBar() {
> return bar
> }
> }
> }
> {code}
> And a set of properties like:
> {code}
> myComponent.foo = "foo"
> myComponent.conf.bar = "bar"
> {code}
> Then only MyComponent.foo will be set but it would be nice if the binding
> framework could navigate the property using dot notation and set any
> dependent object.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13564) Split exception/error handling model from runtime
Guillaume Nodet created CAMEL-13564: --- Summary: Split exception/error handling model from runtime Key: CAMEL-13564 URL: https://issues.apache.org/jira/browse/CAMEL-13564 Project: Camel Issue Type: Improvement Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 3.0.0.M4, 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13563) Update Jetty to 9.4.18 + fix client authentication issues
Colm O hEigeartaigh created CAMEL-13563: --- Summary: Update Jetty to 9.4.18 + fix client authentication issues Key: CAMEL-13563 URL: https://issues.apache.org/jira/browse/CAMEL-13563 Project: Camel Issue Type: Improvement Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 3.0.0, 2.23.3, 2.24.1 This task is to update Jetty to 9.4.18, as there are several CVEs associated with the versions under this that we are picking up. In addition, a number of components have client authentication issues due to the upgrade to Jetty 9.4.15. I'll fix this as part of this upgrade + add tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13557) Support for nested properties binding
[
https://issues.apache.org/jira/browse/CAMEL-13557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846649#comment-16846649
]
Luca Burgazzoli commented on CAMEL-13557:
-
Sounds good to me
> Support for nested properties binding
> -
>
> Key: CAMEL-13557
> URL: https://issues.apache.org/jira/browse/CAMEL-13557
> Project: Camel
> Issue Type: New Feature
> Components: came-core
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.0.0, 3.0.0-M3
>
>
> As today properties binding does not work for nested objects so assuming I
> have a class like:
> {code:java}
> class MyComponent {
>
> public void setFoo(String foo) {
> this.foo = foo;
> }
> public String getFoo() {
> return foo;
> }
> public void setConfiguration(Configuration conf) {
> this.conf = conf;
> }
> public Configuration getConfiguration() {
> return conf;
> }
> static class Configuration {
>
> public void setBar(String bar) {
> this.bar = bar
> }
> public String getBar() {
> return bar
> }
> }
> }
> {code}
> And a set of properties like:
> {code}
> myComponent.foo = "foo"
> myComponent.conf.bar = "bar"
> {code}
> Then only MyComponent.foo will be set but it would be nice if the binding
> framework could navigate the property using dot notation and set any
> dependent object.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13557) Support for nested properties binding
[
https://issues.apache.org/jira/browse/CAMEL-13557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846648#comment-16846648
]
Claus Ibsen commented on CAMEL-13557:
-
Okay got most of it working now. I am thinking about adding an option to
CamelContext so you can turn this on|off globally as we can then introduce this
enabled in M3 (as a tech preview. and then in case something is wrong then it
can be turned off)
> Support for nested properties binding
> -
>
> Key: CAMEL-13557
> URL: https://issues.apache.org/jira/browse/CAMEL-13557
> Project: Camel
> Issue Type: New Feature
> Components: came-core
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.0.0, 3.0.0-M3
>
>
> As today properties binding does not work for nested objects so assuming I
> have a class like:
> {code:java}
> class MyComponent {
>
> public void setFoo(String foo) {
> this.foo = foo;
> }
> public String getFoo() {
> return foo;
> }
> public void setConfiguration(Configuration conf) {
> this.conf = conf;
> }
> public Configuration getConfiguration() {
> return conf;
> }
> static class Configuration {
>
> public void setBar(String bar) {
> this.bar = bar
> }
> public String getBar() {
> return bar
> }
> }
> }
> {code}
> And a set of properties like:
> {code}
> myComponent.foo = "foo"
> myComponent.conf.bar = "bar"
> {code}
> Then only MyComponent.foo will be set but it would be nice if the binding
> framework could navigate the property using dot notation and set any
> dependent object.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-13562) Camel-AWS-SQS: Add an operation to list existing queues
[ https://issues.apache.org/jira/browse/CAMEL-13562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-13562. -- Resolution: Fixed > Camel-AWS-SQS: Add an operation to list existing queues > --- > > Key: CAMEL-13562 > URL: https://issues.apache.org/jira/browse/CAMEL-13562 > Project: Camel > Issue Type: New Feature > Components: camel-aws-sqs >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.0.0, 3.0.0-M3 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13562) Camel-AWS-SQS: Add an operation to list existing queues
Andrea Cosentino created CAMEL-13562: Summary: Camel-AWS-SQS: Add an operation to list existing queues Key: CAMEL-13562 URL: https://issues.apache.org/jira/browse/CAMEL-13562 Project: Camel Issue Type: New Feature Components: camel-aws-sqs Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.0.0, 3.0.0-M3 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13558) Move EIP and language docs back to camel-core and camel-base
[
https://issues.apache.org/jira/browse/CAMEL-13558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart resolved CAMEL-13558.
---
Resolution: Implemented
I completely forgot that symlinks are not supported in Antora, so like with the
component documentation the .adoc files are copied over to the user manual.
Also navigation table of content should be updated and any stale EIPs/languages
will be automatically removed.
> Move EIP and language docs back to camel-core and camel-base
>
>
> Key: CAMEL-13558
> URL: https://issues.apache.org/jira/browse/CAMEL-13558
> Project: Camel
> Issue Type: Bug
> Components: documentation
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
> Fix For: 3.0.0-M3
>
>
> We need to move all {{-eip.adoc}} and {{-language.adoc}} files from
> {{docs/user-manual/modules/ROOT/pages}} to their respective places in
> {{camel-core}} and {{camel-base}} and create symlinks from
> {{docs/user-manual/modules/ROOT/pages}} to them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13561) camel-hystrix - HystrixBadRequestException is swallowed
christian ohr created CAMEL-13561: - Summary: camel-hystrix - HystrixBadRequestException is swallowed Key: CAMEL-13561 URL: https://issues.apache.org/jira/browse/CAMEL-13561 Project: Camel Issue Type: Bug Components: camel-hystrix Reporter: christian ohr CAMEL-13066 fixed a problem that HystrixBadRequestExceptions caused the fallback processor being executed. However, it seems that due to this fix the exception is simply thrown away and the route proceeds as if no error has occurred. This is certainly not the intended behavior. As I understand it, the HystrixBadRequestExceptions should simply be thrown out of the HystrixProcessor, but without any fallback processor being triggered or circuit being opened -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13557) Support for nested properties binding
[
https://issues.apache.org/jira/browse/CAMEL-13557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846522#comment-16846522
]
Claus Ibsen commented on CAMEL-13557:
-
Okay got a bunch of stuff implemented, a few more things to improve and we
would have something useable.
We can then see whether we can make this the default for all configuration of
components, endpoints etc.
> Support for nested properties binding
> -
>
> Key: CAMEL-13557
> URL: https://issues.apache.org/jira/browse/CAMEL-13557
> Project: Camel
> Issue Type: New Feature
> Components: came-core
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.0.0, 3.0.0-M3
>
>
> As today properties binding does not work for nested objects so assuming I
> have a class like:
> {code:java}
> class MyComponent {
>
> public void setFoo(String foo) {
> this.foo = foo;
> }
> public String getFoo() {
> return foo;
> }
> public void setConfiguration(Configuration conf) {
> this.conf = conf;
> }
> public Configuration getConfiguration() {
> return conf;
> }
> static class Configuration {
>
> public void setBar(String bar) {
> this.bar = bar
> }
> public String getBar() {
> return bar
> }
> }
> }
> {code}
> And a set of properties like:
> {code}
> myComponent.foo = "foo"
> myComponent.conf.bar = "bar"
> {code}
> Then only MyComponent.foo will be set but it would be nice if the binding
> framework could navigate the property using dot notation and set any
> dependent object.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-13529) camel-jdbc - Improve to work with the spring Tx Manager
[
https://issues.apache.org/jira/browse/CAMEL-13529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-13529.
--
Resolution: Fixed
> camel-jdbc - Improve to work with the spring Tx Manager
> ---
>
> Key: CAMEL-13529
> URL: https://issues.apache.org/jira/browse/CAMEL-13529
> Project: Camel
> Issue Type: Improvement
> Components: camel-jdbc
>Reporter: Zheng Feng
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.0.0, 3.0.0-M3, 2.25.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> currently the camel-jdbc does not work correctly with the spring
> [DataSourceTransactionManager|https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/jdbc/datasource/DataSourceTransactionManager.html]
> {noformat}
> Application code is required to retrieve the JDBC Connection via
> DataSourceUtils.getConnection(DataSource) instead of a standard Java EE-style
> DataSource.getConnection() call. Spring classes such as JdbcTemplate use this
> strategy implicitly. If not used in combination with this transaction
> manager, the DataSourceUtils lookup strategy behaves exactly like the native
> DataSource lookup; it can thus be used in a portable fashion.
> {noformat}
> So we have to add the extra dependency on the spring-jdbc to support to work
> with the spring Tx Manager by replacing to use
> DataSourceUtils.getConnection(DataSource).
> Quote from [~davsclaus]
> {noformat}
> Well in light of that using transactions with spring TX managers and JDBC
> seems to not work together, then its limited.
> So yeah I think its an okay trade-off to have that extra set of dependencies
> to make it work well with both Spring and I assume also plain JEE. If not we
> can add an option to use either the spring datasource lookup or the current
> approach. However I would be puzzled if that spring-jdbc didn't work OOTB
> with JEE API too.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Work logged] (CAMEL-13529) camel-jdbc - Improve to work with the spring Tx Manager
[
https://issues.apache.org/jira/browse/CAMEL-13529?focusedWorklogId=247312=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-247312
]
ASF GitHub Bot logged work on CAMEL-13529:
--
Author: ASF GitHub Bot
Created on: 23/May/19 07:11
Start Date: 23/May/19 07:11
Worklog Time Spent: 10m
Work Description: oscerd commented on pull request #2944: [CAMEL-13529]
backport to camel-2.x
URL: https://github.com/apache/camel/pull/2944
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: 247312)
Time Spent: 40m (was: 0.5h)
> camel-jdbc - Improve to work with the spring Tx Manager
> ---
>
> Key: CAMEL-13529
> URL: https://issues.apache.org/jira/browse/CAMEL-13529
> Project: Camel
> Issue Type: Improvement
> Components: camel-jdbc
>Reporter: Zheng Feng
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.0.0, 3.0.0-M3, 2.25.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> currently the camel-jdbc does not work correctly with the spring
> [DataSourceTransactionManager|https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/jdbc/datasource/DataSourceTransactionManager.html]
> {noformat}
> Application code is required to retrieve the JDBC Connection via
> DataSourceUtils.getConnection(DataSource) instead of a standard Java EE-style
> DataSource.getConnection() call. Spring classes such as JdbcTemplate use this
> strategy implicitly. If not used in combination with this transaction
> manager, the DataSourceUtils lookup strategy behaves exactly like the native
> DataSource lookup; it can thus be used in a portable fashion.
> {noformat}
> So we have to add the extra dependency on the spring-jdbc to support to work
> with the spring Tx Manager by replacing to use
> DataSourceUtils.getConnection(DataSource).
> Quote from [~davsclaus]
> {noformat}
> Well in light of that using transactions with spring TX managers and JDBC
> seems to not work together, then its limited.
> So yeah I think its an okay trade-off to have that extra set of dependencies
> to make it work well with both Spring and I assume also plain JEE. If not we
> can add an option to use either the spring datasource lookup or the current
> approach. However I would be puzzled if that spring-jdbc didn't work OOTB
> with JEE API too.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
