[jira] [Resolved] (CAMEL-12360) Add logRetryAttemptedInterval to RedeliveryPolicy
[ https://issues.apache.org/jira/browse/CAMEL-12360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Quinn Stevenson resolved CAMEL-12360. - Resolution: Fixed Added Spring support for retryAttemptedLogInterval with commit 73c76e30d268447b810c6985fd009f02aec8917c > Add logRetryAttemptedInterval to RedeliveryPolicy > - > > Key: CAMEL-12360 > URL: https://issues.apache.org/jira/browse/CAMEL-12360 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Quinn Stevenson >Assignee: Quinn Stevenson >Priority: Minor > Fix For: 2.22.0 > > > A logRetryAttemptedInterval configuration property will be added to the > RedeliveryPolicy to provide a little more control over how much information > winds up the logs when Camel is attempting to redeliver an exchange. > When this option is set to a value greater than zero and logRetryAttempted is > true, the retry attempt will be logged for the first attempt and then every > Nth attempt after the first attempt - reducing the number of log entries for > this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (CAMEL-12360) Add logRetryAttemptedInterval to RedeliveryPolicy
[ https://issues.apache.org/jira/browse/CAMEL-12360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494257#comment-16494257 ] Quinn Stevenson edited comment on CAMEL-12360 at 5/29/18 9:00 PM: -- Missed configuration for Spring - will follow with another commit was (Author: hqstevenson): Missed configuration for Spring - will follow with another PR > Add logRetryAttemptedInterval to RedeliveryPolicy > - > > Key: CAMEL-12360 > URL: https://issues.apache.org/jira/browse/CAMEL-12360 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Quinn Stevenson >Assignee: Quinn Stevenson >Priority: Minor > Fix For: 2.22.0 > > > A logRetryAttemptedInterval configuration property will be added to the > RedeliveryPolicy to provide a little more control over how much information > winds up the logs when Camel is attempting to redeliver an exchange. > When this option is set to a value greater than zero and logRetryAttempted is > true, the retry attempt will be logged for the first attempt and then every > Nth attempt after the first attempt - reducing the number of log entries for > this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (CAMEL-12360) Add logRetryAttemptedInterval to RedeliveryPolicy
[ https://issues.apache.org/jira/browse/CAMEL-12360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Quinn Stevenson reopened CAMEL-12360: - Missed configuration for Spring - will follow with another PR > Add logRetryAttemptedInterval to RedeliveryPolicy > - > > Key: CAMEL-12360 > URL: https://issues.apache.org/jira/browse/CAMEL-12360 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Quinn Stevenson >Assignee: Quinn Stevenson >Priority: Minor > Fix For: 2.22.0 > > > A logRetryAttemptedInterval configuration property will be added to the > RedeliveryPolicy to provide a little more control over how much information > winds up the logs when Camel is attempting to redeliver an exchange. > When this option is set to a value greater than zero and logRetryAttempted is > true, the retry attempt will be logged for the first attempt and then every > Nth attempt after the first attempt - reducing the number of log entries for > this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12360) Add logRetryAttemptedInterval to RedeliveryPolicy
[ https://issues.apache.org/jira/browse/CAMEL-12360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Quinn Stevenson resolved CAMEL-12360. - Resolution: Fixed Fix Version/s: 2.22.0 Added functionality with commit 60d285f55dd0ba1139256932e5b0a09608ecaf14 > Add logRetryAttemptedInterval to RedeliveryPolicy > - > > Key: CAMEL-12360 > URL: https://issues.apache.org/jira/browse/CAMEL-12360 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Quinn Stevenson >Assignee: Quinn Stevenson >Priority: Minor > Fix For: 2.22.0 > > > A logRetryAttemptedInterval configuration property will be added to the > RedeliveryPolicy to provide a little more control over how much information > winds up the logs when Camel is attempting to redeliver an exchange. > When this option is set to a value greater than zero and logRetryAttempted is > true, the retry attempt will be logged for the first attempt and then every > Nth attempt after the first attempt - reducing the number of log entries for > this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-10793) camel cloud: expose routes as a service
[
https://issues.apache.org/jira/browse/CAMEL-10793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493767#comment-16493767
]
ASF GitHub Bot commented on CAMEL-10793:
GitHub user lburgazzoli opened a pull request:
https://github.com/apache/camel/pull/2353
camel service registry
This PR is the initial work to ease the process to expose routes as
services [CAMEL-10793](https://issues.apache.org/jira/browse/CAMEL-10793).
A simple example is:
```java
from("service:my-service:undertow:http://0.0.0.0:8080/the/context/path;)
.log("Route ${routeId} has been invoked");
```
As undertow component, supports service registration, this endpoint will be
registered to a given Service Registry (we now have a binding for consul,
zookeeper and spring-cloud) as `my-service` along with some metadata such as
the protocol and the context path. This allow to invoke the service on another
jvm instance by name, like:
```java
from("direct:call")
.serviceCall("my-service")
```
**NOTE**: The implementation is not yet complete so you still need to do
some manual configuration and the number of supported component that support
service registration is limited to those extending `camel-http-common` and
`undertow` .
**NOTE**: integration with spring-cloud is not as easy as it should be so I
had to introduce two new modules: camel-spring-cloud-zookeeper and
camel-spring-cloud-consul.
Any feedback would be really appreciated.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/lburgazzoli/apache-camel CAMEL-12485-pr
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/2353.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2353
commit c927df33aca97744ede41b76e726d4ecef8d3563
Author: lburgazzoli
Date: 2018-05-29T15:08:00Z
CAMEL-12485: camel cloud : create camel-service component
commit 349639992a22a5c67978c3620ac2af0f003c1d86
Author: lburgazzoli
Date: 2018-05-10T16:33:38Z
CAMEL-12502: camel cloud : create a service route policy
commit 95dbeb2794d23538a218a275896a51ad723db550
Author: lburgazzoli
Date: 2018-05-10T20:31:49Z
CAMEL-12485: camel cloud : create camel-service component
commit dfb11b311717cf25068728703ce1542af087cd69
Author: lburgazzoli
Date: 2018-05-11T10:33:33Z
CAMEL-12505: service-call : include ServiceDefinition metatdata when
computing the final URI
commit 8f5486d5e8920daa2d80367a0148c6f4aec5f059
Author: lburgazzoli
Date: 2018-05-14T12:49:37Z
CAMEL-12485: camel cloud : create camel-service component
commit 3e368ca037bc243a8d6678bfcd734f485e8c319c
Author: lburgazzoli
Date: 2018-05-15T13:06:54Z
fix consul kv test
commit c08e704a29954c41d2a13c690424df68bd951ce3
Author: lburgazzoli
Date: 2018-05-17T15:02:40Z
CAMEL-12518: camel cloud : leverage spring-cloud ServiceRegistry to
register routes
commit 4988f0c4ff40f83c6d9fe18f1b6d5be6a3a17ad4
Author: lburgazzoli
Date: 2018-05-23T10:57:51Z
CAMEL-12502: camel cloud : create a service route policy
commit ea88ec23da3e9e886e2cdbbe87992615c11b6c6d
Author: lburgazzoli
Date: 2018-05-23T14:35:40Z
CAMEL-12531: camel cloud : create a spring cloud based camel-service example
commit 5ec6c5ed1f10c369e23296aba2671577fb2d3334
Author: lburgazzoli
Date: 2018-05-23T18:23:40Z
CAMEL-12518: camel cloud : leverage spring-cloud ServiceRegistry to
register routes
commit 086bdfff5fa13e58976f6a77b5b0ef3e05769046
Author: lburgazzoli
Date: 2018-05-23T18:25:12Z
CAMEL-12531: camel cloud : create a spring cloud based camel-service example
commit bbc6e5fc7fe686d37ee085bd4600dfd1166c28b2
Author: lburgazzoli
Date: 2018-05-24T13:16:08Z
CAMEL-12518: camel cloud : leverage spring-cloud ServiceRegistry to
register routes
commit b02d2da88b9459149dcedd1f37d83f5c63eef70b
Author: lburgazzoli
Date: 2018-05-28T11:38:55Z
CAMEL-12502: camel cloud : create a service route policy
commit b412b6282298fe03e9bf80d4cccae675130a27a5
Author: lburgazzoli
Date: 2018-05-28T13:00:08Z
CAMEL-12502: camel cloud : create a service route policy
commit 2adbaab0ebda6a5c6a27dbd2ccd29ec558b09ab3
Author: lburgazzoli
Date: 2018-05-28T13:03:57Z
CAMEL-12502: camel cloud : create a service route policy
commit 14666bfe1b3d81458aee1cf383b7262a513c61e8
Author: lburgazzoli
Date: 2018-05-28T14:08:27Z
service registry doc
commit c09d5fc8ce116fe11d0726cd1839688d9eaf3103
Author: lburgazzoli
Date: 2018-05-29T14:48:19Z
service registry
commit 67a86f57424b976053d86f316b64d44e27437b51
Author: lburgazzoli
Date: 2018-05-29T15:14:24Z
fix typos
commit 2a7e54e9fea7d8e00d8e104a3b14d3756e33a6dc
Author: lburgazzoli
[jira] [Comment Edited] (CAMEL-11162) camel-rest - Should we add content-type check for server side
[ https://issues.apache.org/jira/browse/CAMEL-11162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493507#comment-16493507 ] Claus Ibsen edited comment on CAMEL-11162 at 5/29/18 2:22 PM: -- We would possible need to add a new option to turn this validation on|off. And then add some logic that checks for this: * server side consumes vs content-type provided by client (error 415) * server side produces vs accept header from client (error 406) * required parameters is included (body, path, query) * ??? was (Author: davsclaus): We would possible need to add a new option to turn this validation on|off. And then add some logic that checks for this: * server side consumes vs content-type provided by client * server side produces vs accept header from client (wonder if there is some special HTTP error code for this) * required parameters is included (body, path, query) * ??? > camel-rest - Should we add content-type check for server side > - > > Key: CAMEL-11162 > URL: https://issues.apache.org/jira/browse/CAMEL-11162 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 2.22.0 > > > For example setting up a rest-dsl which consumes application/json and then a > client calls it with text/plain or application/xml, should we then automatic > let rest consumer detect this and return a HTTP status 415 (unsuported media > type) > Not all the HTTP server components does this today, eg jetty etc. But when > using restlet which is more natual REST it would do so. > We could then add an option to turn this on|off. > The check is only if the media-type is within the list that may have been > specified on consumes in the rest-dsl. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-11162) camel-rest - Should we add content-type check for server side
[ https://issues.apache.org/jira/browse/CAMEL-11162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493507#comment-16493507 ] Claus Ibsen commented on CAMEL-11162: - We would possible need to add a new option to turn this validation on|off. And then add some logic that checks for this: * server side consumes vs content-type provided by client * server side produces vs accept header from client (wonder if there is some special HTTP error code for this) * required parameters is included (body, path, query) * ??? > camel-rest - Should we add content-type check for server side > - > > Key: CAMEL-11162 > URL: https://issues.apache.org/jira/browse/CAMEL-11162 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 2.22.0 > > > For example setting up a rest-dsl which consumes application/json and then a > client calls it with text/plain or application/xml, should we then automatic > let rest consumer detect this and return a HTTP status 415 (unsuported media > type) > Not all the HTTP server components does this today, eg jetty etc. But when > using restlet which is more natual REST it would do so. > We could then add an option to turn this on|off. > The check is only if the media-type is within the list that may have been > specified on consumes in the rest-dsl. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-12533) rest-dsl - Should check for required parameters generally
[ https://issues.apache.org/jira/browse/CAMEL-12533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-12533: --- Assignee: Claus Ibsen > rest-dsl - Should check for required parameters generally > - > > Key: CAMEL-12533 > URL: https://issues.apache.org/jira/browse/CAMEL-12533 > Project: Camel > Issue Type: Improvement > Components: camel-core, rest >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 2.22.0 > > > See SO > [https://stackoverflow.com/questions/50489713/camel-rest-dsl-required-param-ignored] > There is AFAIR a little bit of required validation. But we could might as > well do this if the user has specified those in the rest-dsl. > Currently we rely a bit on the chosen http component to do its own > validation. But since we have the rest-dsl contract at hand in the rest-dsl > we should let camel-core figure this out. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-11162) camel-rest - Should we add content-type check for server side
[ https://issues.apache.org/jira/browse/CAMEL-11162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-11162: --- Assignee: Claus Ibsen > camel-rest - Should we add content-type check for server side > - > > Key: CAMEL-11162 > URL: https://issues.apache.org/jira/browse/CAMEL-11162 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 2.22.0 > > > For example setting up a rest-dsl which consumes application/json and then a > client calls it with text/plain or application/xml, should we then automatic > let rest consumer detect this and return a HTTP status 415 (unsuported media > type) > Not all the HTTP server components does this today, eg jetty etc. But when > using restlet which is more natual REST it would do so. > We could then add an option to turn this on|off. > The check is only if the media-type is within the list that may have been > specified on consumes in the rest-dsl. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-10793) camel cloud: expose routes as a service
[
https://issues.apache.org/jira/browse/CAMEL-10793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493470#comment-16493470
]
ASF GitHub Bot commented on CAMEL-10793:
Github user lburgazzoli closed the pull request at:
https://github.com/apache/camel/pull/2352
> camel cloud: expose routes as a service
> ---
>
> Key: CAMEL-10793
> URL: https://issues.apache.org/jira/browse/CAMEL-10793
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
> Labels: cloud
> Fix For: 2.22.0
>
>
> As today we have a ServiceCall EIP that makes it easy to call external
> services in a cloud environment leveraging external service registry such as
> kubernetes, consul, etcd, spring-cloud & co so It could make sense to add a
> way for a route to register itself in such registries and be available as a
> service for other to consume.
> Something like:
> {code:java}
> // programmatic config
> from("jetty:http://0.0.0.0:8001/service1;)
> .serviceRegistry()
> .name("service-1")
> .host("")
> .port(8001)
> .meta("camel.protocol", "http")
> .meta("camel.component", "jetty")
> .meta("camel.context.path", "/service1")
> .end()
> .to("direct:service-1")
> // Inherit from a global config and eventually override it
> from("jetty:http://0.0.0.0:8002/service2;)
> .serviceRegistry("service-2")
> .configRef("service-registry-conf")
> .port(8002)
> .to("direct:service-2")
> // Smart auto configuration
> // i.e. if the endpoint implements DiscoverableService
> from("jetty:http://0.0.0.0:8003/service3;)
> .serviceRegistry("service-3")
> .to("direct:service-3")
> {code}
> Beside making camel play better in cloud environment, you can use the
> service call to connect camel based micro services with minimal configuration
> as the registration may provide some additional meta data that the service
> call can use for auto-configuration (of course not all the registries can do
> it).
> The future Health API/Service may then also be configured to remove or
> invalidate the service if the route is reported as not healthy.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-10793) camel cloud: expose routes as a service
[
https://issues.apache.org/jira/browse/CAMEL-10793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493456#comment-16493456
]
ASF GitHub Bot commented on CAMEL-10793:
GitHub user lburgazzoli opened a pull request:
https://github.com/apache/camel/pull/2352
camel service registry
This PR is the initial work to ease the process to expose routes as
services [CAMEL-10793](https://issues.apache.org/jira/browse/CAMEL-10793).
A simple example is:
```java
from("service:my-service:undertow:http://0.0.0.0:8080/the/context/path;)
.log("Route ${routeId} has been invoked");
```
As undertow component, supports service registration, this endpoint will be
registered to a given Service Registry (we now have a binding for consul,
zookeeper and spring-cloud) as `my-service` along with some metadata such as
the protocol and the context path. This allow to invoke the service on another
jvm instance by name, like:
```java
from("direct:call")
.serviceCall("my-service")
```
**NOTE**: The implementation is not yet complete so you still need to do
some manual configuration and the number of supported component that support
service registration is limited to those extending `camel-http-common` and
`undertow` .
**NOTE**: integration with spring-cloud is not as easy as it should be so I
had to introduce two new modules: camel-spring-cloud-zookeeper and
camel-spring-cloud-consul.
Any feedback would be really appreciated.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/lburgazzoli/apache-camel CAMEL-12485
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/2352.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2352
commit 8959683c39d8d8ff368c91fd2362dc149149cbd3
Author: lburgazzoli
Date: 2018-05-07T17:00:52Z
CAMEL-12485: camel cloud : create camel-service component
commit cbdb3b64c1c79886d17337517f498fb7804f5fed
Author: lburgazzoli
Date: 2018-05-10T16:33:38Z
CAMEL-12502: camel cloud : create a service route policy
commit 07594d2fa19d8987eca783a2a7afab70846094b0
Author: lburgazzoli
Date: 2018-05-10T20:31:49Z
CAMEL-12485: camel cloud : create camel-service component
commit 54b1405759298991a116502a6e60d203f3e91965
Author: lburgazzoli
Date: 2018-05-11T10:33:33Z
CAMEL-12505: service-call : include ServiceDefinition metatdata when
computing the final URI
commit 4468cc1e54f0fc2314d34b0172d06c5548de4bc4
Author: lburgazzoli
Date: 2018-05-14T12:49:37Z
CAMEL-12485: camel cloud : create camel-service component
commit bb9e10539ff0cdcc26539981534bdf39205b760e
Author: lburgazzoli
Date: 2018-05-15T13:06:54Z
fix consul kv test
commit e62ffebe643eef2897cd393a37a1a7aa4248ca94
Author: lburgazzoli
Date: 2018-05-17T15:02:40Z
CAMEL-12518: camel cloud : leverage spring-cloud ServiceRegistry to
register routes
commit e10065dcf25a0ae61a2eeeaa2c20157c577945f3
Author: lburgazzoli
Date: 2018-05-23T10:57:51Z
CAMEL-12502: camel cloud : create a service route policy
commit 5079e5335a8ee0a92fa70c4f1ff29006c2d51165
Author: lburgazzoli
Date: 2018-05-23T14:35:40Z
CAMEL-12531: camel cloud : create a spring cloud based camel-service example
commit 51ed886d139a11e9d83e57d8d3806fdbccd92f5f
Author: lburgazzoli
Date: 2018-05-23T18:23:40Z
CAMEL-12518: camel cloud : leverage spring-cloud ServiceRegistry to
register routes
commit a887bbe8b07871e2f7713e6a89f2febcf4707f33
Author: lburgazzoli
Date: 2018-05-23T18:25:12Z
CAMEL-12531: camel cloud : create a spring cloud based camel-service example
commit ad6e928bd388070020793f9c6bc72c04758a
Author: lburgazzoli
Date: 2018-05-24T13:16:08Z
CAMEL-12518: camel cloud : leverage spring-cloud ServiceRegistry to
register routes
commit 2611407c6f996a010aa5ca240c21652b45502c82
Author: lburgazzoli
Date: 2018-05-28T11:38:55Z
CAMEL-12502: camel cloud : create a service route policy
commit aaceeea8250b928fb870408cc7c3aab13e9d7a08
Author: lburgazzoli
Date: 2018-05-28T13:00:08Z
CAMEL-12502: camel cloud : create a service route policy
commit 1b655e17a7d01f8083b5cd2d76b837d279ded4bb
Author: lburgazzoli
Date: 2018-05-28T13:03:57Z
CAMEL-12502: camel cloud : create a service route policy
commit fee9b5c3b95c741526e0c768270ce0f9a0695679
Author: lburgazzoli
Date: 2018-05-28T14:08:27Z
service registry doc
> camel cloud: expose routes as a service
> ---
>
> Key: CAMEL-10793
> URL: https://issues.apache.org/jira/browse/CAMEL-10793
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>
[jira] [Created] (CAMEL-12545) create a yaml based route loader
Luca Burgazzoli created CAMEL-12545: --- Summary: create a yaml based route loader Key: CAMEL-12545 URL: https://issues.apache.org/jira/browse/CAMEL-12545 Project: Camel Issue Type: New Feature Reporter: Luca Burgazzoli Fix For: 2.23.0, 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-10956) camel-core: more flexible route loader
[ https://issues.apache.org/jira/browse/CAMEL-10956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli updated CAMEL-10956: Description: As today we can add files as "classpath:camel/*.xml" and camel picks them up but we should make it more flexible like collecting/discovering all the beans/service of type "RouteBuilderManager" (name is just an hint) and delegate the loading of the routes (and eventually theirs reload) to such managers. By default we'll provide the one to load the Java/XML but developer can add custom loaders so that routs can be load from yaml, json, scripting languages etc. and they can also have theirs custom logic to reload a route. > camel-core: more flexible route loader > -- > > Key: CAMEL-10956 > URL: https://issues.apache.org/jira/browse/CAMEL-10956 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Luca Burgazzoli >Priority: Major > Fix For: 3.0.0 > > > As today we can add files as "classpath:camel/*.xml" and camel picks them up > but we should make it more flexible like collecting/discovering all the > beans/service of type "RouteBuilderManager" (name is just an hint) and > delegate the loading of the routes (and eventually theirs reload) to such > managers. > By default we'll provide the one to load the Java/XML but developer can add > custom loaders so that routs can be load from yaml, json, scripting languages > etc. and they can also have theirs custom logic to reload a route. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-10956) camel-core: more flexible route loader
[ https://issues.apache.org/jira/browse/CAMEL-10956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli updated CAMEL-10956: Environment: (was: As today we can add files as "classpath:camel/*.xml" and camel picks them up but we should make it more flexible like collecting/doscovering all the beans/service of type "RouteBuilderManager" (name is just an hint) and delegate the loading of the routes (and eventually theirs reload) to such managers. By default we'll provide the one to load the Java/XML but developer can add custom loaders so that routs can be load from yaml, json, scripting languages etc. and they can also have theirs custom logic to reload a route. ) > camel-core: more flexible route loader > -- > > Key: CAMEL-10956 > URL: https://issues.apache.org/jira/browse/CAMEL-10956 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Luca Burgazzoli >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12544) Camel-Couchdb: Add a get method to have a complete CRUD support
[ https://issues.apache.org/jira/browse/CAMEL-12544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-12544. -- Resolution: Fixed > Camel-Couchdb: Add a get method to have a complete CRUD support > --- > > Key: CAMEL-12544 > URL: https://issues.apache.org/jira/browse/CAMEL-12544 > Project: Camel > Issue Type: Task > Components: camel-couchdb >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 2.22.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12544) Camel-Couchdb: Add a get method to have a complete CRUD support
[ https://issues.apache.org/jira/browse/CAMEL-12544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-12544: - Summary: Camel-Couchdb: Add a get method to have a complete CRUD support (was: Camel-Couchdb: Add a find method to have a complete CRUD) > Camel-Couchdb: Add a get method to have a complete CRUD support > --- > > Key: CAMEL-12544 > URL: https://issues.apache.org/jira/browse/CAMEL-12544 > Project: Camel > Issue Type: Task > Components: camel-couchdb >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 2.22.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12544) Camel-Couchdb: Add a find method to have a complete CRUD
Andrea Cosentino created CAMEL-12544: Summary: Camel-Couchdb: Add a find method to have a complete CRUD Key: CAMEL-12544 URL: https://issues.apache.org/jira/browse/CAMEL-12544 Project: Camel Issue Type: Task Components: camel-couchdb Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 2.22.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12331) camel-sql - JdbcMessageIdRepository should have a background task to delete old entries
[ https://issues.apache.org/jira/browse/CAMEL-12331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493213#comment-16493213 ] Önder Sezgin commented on CAMEL-12331: -- IMHO, clean up at the application level would not be a good practice.Instead, partitioning the table by some of group of key and dropping those partitions may be easier as a DB task. > camel-sql - JdbcMessageIdRepository should have a background task to delete > old entries > --- > > Key: CAMEL-12331 > URL: https://issues.apache.org/jira/browse/CAMEL-12331 > Project: Camel > Issue Type: New Feature > Components: camel-sql >Reporter: Claus Ibsen >Priority: Major > Fix For: 2.22.0 > > > You may want to cleanup the database table automatically by Camel so it does > not contain old data of previous processed files. > For example to say that entries that are > 24h can be deleted etc. > This works under the notion that you only use the idempoten check for > clustering where they may race for processing the same files, or that files > tomorrow are okay to process with the same name as yesterday etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12375) Spring Boot 2 - Upgrade Spring SMX bundles to latest releases
[ https://issues.apache.org/jira/browse/CAMEL-12375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493172#comment-16493172 ] Andrea Cosentino commented on CAMEL-12375: -- Actually the spring-security feature doesn't work with the last SMX release 5.0.4, while spring-data stuff (redis) updated to 2.0.5 are not bundles anymore. > Spring Boot 2 - Upgrade Spring SMX bundles to latest releases > - > > Key: CAMEL-12375 > URL: https://issues.apache.org/jira/browse/CAMEL-12375 > Project: Camel > Issue Type: Sub-task >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 2.22.0 > > > As part of the Spring 5 and SB2 upgrade, then related Spring projects were > also upgraded like: spring-security, spring-integration, spring-ws, > spring-data, etc. > As they have SMX bundles to run in OSGi, then the SMX team need to do latest > releases of these versions as well. > And then we need to update the karaf features.xml file in Camel. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-12375) Spring Boot 2 - Upgrade Spring SMX bundles to latest releases
[ https://issues.apache.org/jira/browse/CAMEL-12375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-12375: Assignee: Andrea Cosentino > Spring Boot 2 - Upgrade Spring SMX bundles to latest releases > - > > Key: CAMEL-12375 > URL: https://issues.apache.org/jira/browse/CAMEL-12375 > Project: Camel > Issue Type: Sub-task >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 2.22.0 > > > As part of the Spring 5 and SB2 upgrade, then related Spring projects were > also upgraded like: spring-security, spring-integration, spring-ws, > spring-data, etc. > As they have SMX bundles to run in OSGi, then the SMX team need to do latest > releases of these versions as well. > And then we need to update the karaf features.xml file in Camel. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12541) camel-cxfrs - rsClient does not work programmatically, only with XML
[
https://issues.apache.org/jira/browse/CAMEL-12541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang updated CAMEL-12541:
-
Fix Version/s: 2.22.0
2.21.2
2.20.4
> camel-cxfrs - rsClient does not work programmatically, only with XML
>
>
> Key: CAMEL-12541
> URL: https://issues.apache.org/jira/browse/CAMEL-12541
> Project: Camel
> Issue Type: Bug
> Components: camel-cxfrs
>Affects Versions: 2.21.1
>Reporter: Willian Antunes
>Priority: Major
> Fix For: 2.20.4, 2.21.2, 2.22.0
>
>
> As described in the documentation you can use [camel-cxfrs as
> producer|https://github.com/apache/camel/blob/39c0d63d923bfe9236834ecb1c4470bb7e9e7eaa/components/camel-cxf/src/main/docs/cxfrs-component.adoc#how-to-configure-the-rest-endpoint-in-camel].
> You have some approaches like using a proxy created from a interface which
> maps all the services available in the targeted REST web service (sample
> [here|https://github.com/willianantunes/honesto-sqn/blob/d4bf48257fc64a4725894c7f07c24bb1a516d410/src/main/java/br/com/willianantunes/serenata/JarbasAPI.java#L14]).
> As I'm using Spring Boot and Apache Camel I may create a bean through XML or
> programmatically.
> h4. Creating the test sample
> I'm testing with the following:
> [https://gist.github.com/willianantunes/58979bfb91ee30c7ff4e235940e60880]
> You can find a copy of JarbasAPI
> [here|https://github.com/willianantunes/honesto-sqn/blob/d4bf48257fc64a4725894c7f07c24bb1a516d410/src/main/java/br/com/willianantunes/serenata/JarbasAPI.java#L14].
> h4. When rsClient producer works as expected
> When I do using the first approach using the configuration below everything
> works fine:
> {code:xml}
>
> http://www.springframework.org/schema/beans;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xmlns:cxf="http://camel.apache.org/schema/cxf;
>xmlns:jaxrs="http://cxf.apache.org/jaxrs;
>xmlns:util="http://www.springframework.org/schema/util;
>xsi:schemaLocation="
>http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
>http://www.springframework.org/schema/util
> http://www.springframework.org/schema/util/spring-util.xsd
>http://camel.apache.org/schema/cxf
> http://camel.apache.org/schema/cxf/camel-cxf.xsd
>http://cxf.apache.org/jaxrs http://cxf.apache.org/schemas/jaxrs.xsd
>http://camel.apache.org/schema/spring
> http://camel.apache.org/schema/spring/camel-spring.xsd;>
>address="https://jarbas.serenata.ai;
> serviceClass="br.com.willianantunes.serenata.JarbasAPI"/>
>
> {code}
> h4. When rsClient producer does not work as expected
> XML works fine, but when I do the same thing programmatically it doesn't.
> {code:java}
> @Bean("serviceEndpoint")
> public SpringJAXRSClientFactoryBean serviceEndpoint() {
> SpringJAXRSClientFactoryBean clientFactoryBean = new
> SpringJAXRSClientFactoryBean();
> clientFactoryBean.setAddress("https://jarbas.serenata.ai;);
> clientFactoryBean.setServiceClass(JarbasAPI.class);
> return clientFactoryBean;
> }
> {code}
> Although it has no difference compared to XML, it does not work.
> h4. When does it fail?
> Debugging you can see the following:
> * The bean is correctly got
> [here|https://github.com/apache/camel/blob/a4cfea6823d31eacf57489e1ffeead9a256b/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/jaxrs/CxfRsComponent.java#L76]
> is CxfRsComponent.
> * When a message is sent and there is a _to_ command with the URI
> *cxfrs:bean:serviceEndpoint,* I see the message arriving
> [here|https://github.com/apache/camel/blob/a4cfea6823d31eacf57489e1ffeead9a256b/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/jaxrs/CxfRsProducer.java#L94]
> in CxfRsProducer.
> * The method
> [invokeProxyClient|https://github.com/apache/camel/blob/a4cfea6823d31eacf57489e1ffeead9a256b/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/jaxrs/CxfRsProducer.java#L103]
> is called.
> * The SpringJAXRSClientFactoryBean which I provided as bean is ignored. A
> new one is created
> [here|https://github.com/apache/camel/blob/834a59910e4b6b8d089e229b39f6c8673e7c3f9a/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/jaxrs/CxfRsEndpoint.java#L414]
> and when it arrives to the next line the method invoked is from
> [CxfRsSpringEndpoint|https://github.com/apache/camel/blob/834a59910e4b6b8d089e229b39f6c8673e7c3f9a/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/jaxrs/CxfRsSpringEndpoint.java]
> which uses
>
[jira] [Commented] (CAMEL-11918) Wrong parent version in connectors/examples/pom.xml
[
https://issues.apache.org/jira/browse/CAMEL-11918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493166#comment-16493166
]
Önder Sezgin commented on CAMEL-11918:
--
Releases not modifying these properly.
[https://github.com/apache/camel/blob/release/2.20.3/connectors/examples/pom.xml#L27]
[https://github.com/apache/camel/blob/release/2.21.1/connectors/examples/pom.xml#L27]
> Wrong parent version in connectors/examples/pom.xml
> ---
>
> Key: CAMEL-11918
> URL: https://issues.apache.org/jira/browse/CAMEL-11918
> Project: Camel
> Issue Type: Task
> Components: build system, camel-connector
>Affects Versions: 2.20.0
>Reporter: Paolo Antinori
>Priority: Minor
> Fix For: 2.22.0
>
>
> {{connectors/examples/pom.xml}} of the released tag {{2.20.0}} still points
> to a SNAPSHOT version:
> https://github.com/apache/camel/blob/camel-2.20.0/connectors/examples/pom.xml#L27
> This is probably the side effect of using {{maven-release-plugin}} and the
> fact that {{connectores/example}} module is detached:
> https://github.com/apache/camel/blob/camel-2.20.0/connectors/pom.xml#L40
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-12365) Upgrade consul client to 1.1.1
[ https://issues.apache.org/jira/browse/CAMEL-12365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-12365. -- Resolution: Fixed > Upgrade consul client to 1.1.1 > -- > > Key: CAMEL-12365 > URL: https://issues.apache.org/jira/browse/CAMEL-12365 > Project: Camel > Issue Type: Task > Components: camel-consul >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 2.22.0 > > > There is a newer version -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-11038) Ping Check API - Output metadata to component json file
[
https://issues.apache.org/jira/browse/CAMEL-11038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-11038:
Fix Version/s: (was: 2.22.0)
2.23.0
> Ping Check API - Output metadata to component json file
> ---
>
> Key: CAMEL-11038
> URL: https://issues.apache.org/jira/browse/CAMEL-11038
> Project: Camel
> Issue Type: Task
> Components: camel-core
>Reporter: Claus Ibsen
>Priority: Major
> Fix For: 2.23.0
>
>
> We need to add some logic to apt compiler plugin so it can detect its a
> verifiable component (ping check) and add some details in the component json
> file.
> We would need on the component section, something along the lines to denote
> what features it supports
> {code}
> "verifiable": [ "connectivity", "parameters" ]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-11325) Upgrade to Apache Spark 2.x
[ https://issues.apache.org/jira/browse/CAMEL-11325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-11325: Fix Version/s: (was: 2.22.0) 2.23.0 > Upgrade to Apache Spark 2.x > --- > > Key: CAMEL-11325 > URL: https://issues.apache.org/jira/browse/CAMEL-11325 > Project: Camel > Issue Type: Task > Components: camel-spark >Reporter: Claus Ibsen >Priority: Major > Fix For: 2.23.0 > > > We currently are on 1.x, and there is a newer 2.x release out which we should > upgrade to. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-11231) JSON Api Dataformat
[ https://issues.apache.org/jira/browse/CAMEL-11231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-11231: Fix Version/s: (was: 2.22.0) 2.23.0 > JSON Api Dataformat > --- > > Key: CAMEL-11231 > URL: https://issues.apache.org/jira/browse/CAMEL-11231 > Project: Camel > Issue Type: New Feature >Reporter: Charles Moulliard >Priority: Major > Fix For: 2.23.0 > > > Implement a new DataFormat to support to serialize/deserialize JSONApi > Objects/Strings as defined within the spec : http://jsonapi.org/ > Potential candidate projects to be evaluated : > - https://github.com/jasminb/jsonapi-converter > - https://github.com/faogustavo/JSONApi -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-11707) spring boot code generation: there should be a way to exclude some properties from the code generation
[
https://issues.apache.org/jira/browse/CAMEL-11707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-11707:
Fix Version/s: (was: 2.22.0)
2.23.0
> spring boot code generation: there should be a way to exclude some properties
> from the code generation
> --
>
> Key: CAMEL-11707
> URL: https://issues.apache.org/jira/browse/CAMEL-11707
> Project: Camel
> Issue Type: Improvement
> Components: tooling
>Reporter: Luca Burgazzoli
>Priority: Major
> Fix For: 2.23.0
>
>
> As today every property is exposed to spring boot auto configuration
> processor but sometimes you may want to hide some or them as they may be
> supposed to be used only internally or because you want to write your own
> code to manage complex configurations.
> As this may also be needed to hide info from the catalog, we may have
> something like:
> {code}
> @Metadata(key = "ignore", value = "true", labels = "spring-boot,catalog")
> {code}
> Or have specific annotations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-11262) camel-google-pubsub - Improve to work with streaming mode
[ https://issues.apache.org/jira/browse/CAMEL-11262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-11262: Fix Version/s: (was: 2.22.0) 2.23.0 > camel-google-pubsub - Improve to work with streaming mode > - > > Key: CAMEL-11262 > URL: https://issues.apache.org/jira/browse/CAMEL-11262 > Project: Camel > Issue Type: Improvement > Components: camel-google-pubsub >Affects Versions: 2.19.0 >Reporter: Claus Ibsen >Priority: Major > Fix For: 2.23.0 > > > The pubsub component > https://github.com/apache/camel/tree/master/components/camel-google-pubsub > Can likely be improved to work better with streaming mode and use Camel > asynchronous processing. > There may be other things. > Ray Tsang from Google has some ideas and want to help out. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-11708) spring boot code generation: the nested property processor does not handle object hierarchies
[
https://issues.apache.org/jira/browse/CAMEL-11708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-11708:
Fix Version/s: (was: 2.22.0)
2.23.0
> spring boot code generation: the nested property processor does not handle
> object hierarchies
> -
>
> Key: CAMEL-11708
> URL: https://issues.apache.org/jira/browse/CAMEL-11708
> Project: Camel
> Issue Type: Improvement
> Components: tooling
>Reporter: Luca Burgazzoli
>Priority: Major
> Fix For: 2.23.0
>
>
> Assuming you have complex configuration object that inherits from another
> configuration object, the spring boot code generation will creates the
> configuration properties object only for the properties of the last class so
> i.e. for a simple hierarchy like:
> {code}
> Common {
> String getX()
> void setX(String);
> }
> Specific extends Common {
> String getY()
> void setY(String);
> }
> {code}
> the generator will provides bindings only for
> {code}
> String getX()
> setX(String)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-11722) catalog: it should be possible to enrich catalogs's data with custom json
[
https://issues.apache.org/jira/browse/CAMEL-11722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-11722:
Fix Version/s: (was: 2.22.0)
2.23.0
> catalog: it should be possible to enrich catalogs's data with custom json
> -
>
> Key: CAMEL-11722
> URL: https://issues.apache.org/jira/browse/CAMEL-11722
> Project: Camel
> Issue Type: Improvement
> Components: camel-catalog
>Reporter: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.23.0
>
>
> I may be useful to have the catalog to load additional catalog properties
> like i.e. [spring-boot meta
> data|https://docs.spring.io/spring-boot/docs/current/reference/html/configuration-metadata.html#configuration-metadata-additional-metadata]
> so one can add information about additional stuffs like extensions.
> The extension files could be placed in META-INF/camel/catalog with a content
> like:
> {code}
> {
> "extensions": {
> "my.Extension.class": {
> "inheritsProperties": true,
> "properties": {
>
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-11887) JDK9 - Module names for Apache Camel
[ https://issues.apache.org/jira/browse/CAMEL-11887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-11887: Fix Version/s: (was: 2.22.0) 2.23.0 > JDK9 - Module names for Apache Camel > > > Key: CAMEL-11887 > URL: https://issues.apache.org/jira/browse/CAMEL-11887 > Project: Camel > Issue Type: Task > Components: build system >Reporter: Claus Ibsen >Priority: Major > Fix For: 2.23.0 > > > We should decide what JDK9 module name to use for Apache Camel. > There is a bit of information about this at this PR > https://github.com/apache/camel/pull/2007 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12347) Reduce the usage of 3rd party maven repos
[ https://issues.apache.org/jira/browse/CAMEL-12347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-12347. - Resolution: Fixed > Reduce the usage of 3rd party maven repos > - > > Key: CAMEL-12347 > URL: https://issues.apache.org/jira/browse/CAMEL-12347 > Project: Camel > Issue Type: Task >Reporter: Claus Ibsen >Priority: Major > Fix For: 2.22.0 > > > Some components are downloading JARs that seems to be only on 3rd party repos > - We should try to rely only on maven central whenever possible > Sometimes it may be test scoped and we can switch to something else etc. > I have been told these components may do that: > * camel-Jira > * camel-nagios > * camel-solr > * itest > * camel-restlet > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12347) Reduce the usage of 3rd party maven repos
[ https://issues.apache.org/jira/browse/CAMEL-12347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493152#comment-16493152 ] Claus Ibsen commented on CAMEL-12347: - So its only camel-restlet which have 3rd party JARs in their own repo. We cannot do something about this. > Reduce the usage of 3rd party maven repos > - > > Key: CAMEL-12347 > URL: https://issues.apache.org/jira/browse/CAMEL-12347 > Project: Camel > Issue Type: Task >Reporter: Claus Ibsen >Priority: Major > Fix For: 2.22.0 > > > Some components are downloading JARs that seems to be only on 3rd party repos > - We should try to rely only on maven central whenever possible > Sometimes it may be test scoped and we can switch to something else etc. > I have been told these components may do that: > * camel-Jira > * camel-nagios > * camel-solr > * itest > * camel-restlet > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12347) Reduce the usage of 3rd party maven repos
[
https://issues.apache.org/jira/browse/CAMEL-12347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493151#comment-16493151
]
Claus Ibsen commented on CAMEL-12347:
-
itest is using some trick to use a local built JAR file
camel-validator-test-repo
This project repository contains
camel-validator-test-resources-1.0.0.jar
file://${basedir}/lib
> Reduce the usage of 3rd party maven repos
> -
>
> Key: CAMEL-12347
> URL: https://issues.apache.org/jira/browse/CAMEL-12347
> Project: Camel
> Issue Type: Task
>Reporter: Claus Ibsen
>Priority: Major
> Fix For: 2.22.0
>
>
> Some components are downloading JARs that seems to be only on 3rd party repos
> - We should try to rely only on maven central whenever possible
> Sometimes it may be test scoped and we can switch to something else etc.
> I have been told these components may do that:
> * camel-Jira
> * camel-nagios
> * camel-solr
> * itest
> * camel-restlet
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12347) Reduce the usage of 3rd party maven repos
[ https://issues.apache.org/jira/browse/CAMEL-12347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493149#comment-16493149 ] Claus Ibsen commented on CAMEL-12347: - camel-solr has no 3rd party repo anymore > Reduce the usage of 3rd party maven repos > - > > Key: CAMEL-12347 > URL: https://issues.apache.org/jira/browse/CAMEL-12347 > Project: Camel > Issue Type: Task >Reporter: Claus Ibsen >Priority: Major > Fix For: 2.22.0 > > > Some components are downloading JARs that seems to be only on 3rd party repos > - We should try to rely only on maven central whenever possible > Sometimes it may be test scoped and we can switch to something else etc. > I have been told these components may do that: > * camel-Jira > * camel-nagios > * camel-solr > * itest > * camel-restlet > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12347) Reduce the usage of 3rd party maven repos
[ https://issues.apache.org/jira/browse/CAMEL-12347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493146#comment-16493146 ] Claus Ibsen commented on CAMEL-12347: - camel-Jira has been deprecated > Reduce the usage of 3rd party maven repos > - > > Key: CAMEL-12347 > URL: https://issues.apache.org/jira/browse/CAMEL-12347 > Project: Camel > Issue Type: Task >Reporter: Claus Ibsen >Priority: Major > Fix For: 2.22.0 > > > Some components are downloading JARs that seems to be only on 3rd party repos > - We should try to rely only on maven central whenever possible > Sometimes it may be test scoped and we can switch to something else etc. > I have been told these components may do that: > * camel-Jira > * camel-nagios > * camel-solr > * itest > * camel-restlet > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12538) camel-caffeine: do not use different caches with slightly different URIs
[
https://issues.apache.org/jira/browse/CAMEL-12538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-12538.
--
Resolution: Not A Problem
> camel-caffeine: do not use different caches with slightly different URIs
>
>
> Key: CAMEL-12538
> URL: https://issues.apache.org/jira/browse/CAMEL-12538
> Project: Camel
> Issue Type: Bug
> Components: camel-caffeine
>Affects Versions: 2.21.1
>Reporter: Nicola Ferraro
>Assignee: Andrea Cosentino
>Priority: Major
>
> I've found a problem with caffeine-cache. When I use the following:
> {code:java}
> // route 1
> .to("caffeine-cache:global?key=x=PUT")
> // route 2
> .to("caffeine-cache:global?key=x=GET"{code}
> I expect that what I save in route 1 can be retrieved in route 2, but this is
> not the case, since the two URIs differ (GET/PUT) and I get two different
> caches.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-12398) Camel components - Include component verifier details in the component json schema file
[ https://issues.apache.org/jira/browse/CAMEL-12398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-12398: Fix Version/s: (was: 2.22.0) 2.23.0 > Camel components - Include component verifier details in the component json > schema file > --- > > Key: CAMEL-12398 > URL: https://issues.apache.org/jira/browse/CAMEL-12398 > Project: Camel > Issue Type: Improvement > Components: tooling >Reporter: Claus Ibsen >Priority: Major > Fix For: 2.23.0 > > > Some components have component verifiers implemented, but we dont really know > which one without looking into the source etc. > We should make this information available in the json schema file, so we can > know this. Then we can have out build tools be able to add details about this > into the component docs, and as well 3rd party tools would know via the > camel-catalog which components has this our not. > Also we may need to include more details information how to execute a > verifier, eg which options to include, so the 3rd party tooling would know. > And we can also generate a report which component has this, and which has > not. Then we can better find out and implement this for more and more > components. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12455) camel-rabbitmq - Property DELIVERY_MODE is not set to exchange
[ https://issues.apache.org/jira/browse/CAMEL-12455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-12455. - Resolution: Fixed Thanks for the PR > camel-rabbitmq - Property DELIVERY_MODE is not set to exchange > -- > > Key: CAMEL-12455 > URL: https://issues.apache.org/jira/browse/CAMEL-12455 > Project: Camel > Issue Type: Improvement > Components: camel-rabbitmq >Affects Versions: 2.19.4 >Reporter: Tomáš >Priority: Minor > Fix For: 2.22.0 > > > *Steps to reproduce* > * configure camel to receive messages from rabbitmq server > * produce / receive message > * look into list of message properties > *Expected result* > There is rabbitmq.DELIVERY_MODE set to either 1 or 2 based on message > persistance. > *Actual result* > The rabbitmq.DELIVERY_MODE property is missing. > *Dev notes:* > class: org.apache.camel.component.rabbitmq.RabbitMQMessageConverter > method: mergeAmqpProperties > The mapping for DELIVERY_MODE property is missing. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12543) create a camel-debezium component
Luca Burgazzoli created CAMEL-12543: --- Summary: create a camel-debezium component Key: CAMEL-12543 URL: https://issues.apache.org/jira/browse/CAMEL-12543 Project: Camel Issue Type: New Feature Reporter: Luca Burgazzoli Fix For: 2.23.0 See http://debezium.io/docs/embedded/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
