[jira] [Commented] (CAMEL-11622) Rest-dsl doesn't support post() endpoints with different request body types

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16117820#comment-16117820
 ] 

ASF GitHub Bot commented on CAMEL-11622:


Github user bszeti closed the pull request at:

https://github.com/apache/camel/pull/1868


> Rest-dsl doesn't support post() endpoints with different request body types
> ---
>
> Key: CAMEL-11622
> URL: https://issues.apache.org/jira/browse/CAMEL-11622
> Project: Camel
>  Issue Type: Wish
>  Components: rest
>Affects Versions: 2.18.1
> Environment: Spring-Boot with Tomcat8 container
>Reporter: Balazs Szeti
> Fix For: 2.18.2
>
>
> The rest-dsl doesn't support two post() endpoints with different request body 
> types.
> {code:java}
> restConfiguration()
>   .component("servlet")
>   .contextPath("/api")
>   .bindingMode(RestBindingMode.json)
> ;
> rest("/user")
>   .post("/employee").type(UserPojo.class)
>   .route()
>   .log("Name: ${body.name}")
>   .endRest()
> ;
> rest("/country")
>   .post("/origin").type(CountryPojo.class)
>   .route()
>   .log("Name: ${body.country}")
>   .endRest()
> ;
> {code}
> Both endpoints (/api/user/employee, /api/country/origin) tries to unmarshal 
> the post body to CountryPojo and a JsonProcessingException is thrown when a 
> UserPojo json is sent to /user/employee.
> The problem is that they share one JascksonDataFormat instance registered 
> with name "json-jackson" and the RestDefinition.type() sets the 
> JascksonDataFormat.unmarshalType so at the end both post() endpoints will try 
> to unmarshal to the same class.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11648) camel-mongodb-gridfs - Created document cannot be read by the new MongoDB GridFS API

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16117748#comment-16117748
 ] 

ASF GitHub Bot commented on CAMEL-11648:


Github user asfgit closed the pull request at:

https://github.com/apache/camel/pull/1876


> camel-mongodb-gridfs - Created document cannot be read by the new MongoDB 
> GridFS API
> 
>
> Key: CAMEL-11648
> URL: https://issues.apache.org/jira/browse/CAMEL-11648
> Project: Camel
>  Issue Type: Bug
>  Components: camel-mongodb
>Affects Versions: 2.19.1
>Reporter: Mihály Gyöngyösi
>Priority: Minor
> Fix For: 2.20.0, 2.19.3
>
>
> The new MongoDB GridFS API 
> (http://mongodb.github.io/mongo-java-driver/3.5/driver/tutorials/gridfs/) 
> throws an exception when my application (not Camel based) iterates over the 
> GridFS documents created by Camel's {{camel-mongodb-gridfs}} component.
> The problem: the current GridFSProducer adds the "metadata" field regardless 
> it is null. Referring to https://jira.mongodb.org/browse/JAVA-2577 the 
> document should not contain a metadata field if the field is null.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (CAMEL-11648) camel-mongodb-gridfs - Created document cannot be read by the new MongoDB GridFS API

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-11648.
-
   Resolution: Fixed
 Assignee: Claus Ibsen
Fix Version/s: 2.19.3
   2.20.0

Thanks for the PR

> camel-mongodb-gridfs - Created document cannot be read by the new MongoDB 
> GridFS API
> 
>
> Key: CAMEL-11648
> URL: https://issues.apache.org/jira/browse/CAMEL-11648
> Project: Camel
>  Issue Type: Bug
>  Components: camel-mongodb
>Affects Versions: 2.19.1
>Reporter: Mihály Gyöngyösi
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.20.0, 2.19.3
>
>
> The new MongoDB GridFS API 
> (http://mongodb.github.io/mongo-java-driver/3.5/driver/tutorials/gridfs/) 
> throws an exception when my application (not Camel based) iterates over the 
> GridFS documents created by Camel's {{camel-mongodb-gridfs}} component.
> The problem: the current GridFSProducer adds the "metadata" field regardless 
> it is null. Referring to https://jira.mongodb.org/browse/JAVA-2577 the 
> document should not contain a metadata field if the field is null.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11648) camel-mongodb-gridfs - Created document cannot be read by the new MongoDB GridFS API

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16117184#comment-16117184
 ] 

ASF GitHub Bot commented on CAMEL-11648:


GitHub user mgyongyosi opened a pull request:

https://github.com/apache/camel/pull/1876

CAMEL-11648: gridfs skip metadata field if it is null

PR for https://issues.apache.org/jira/browse/CAMEL-11648

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mgyongyosi/camel 
camel-mongodb-gridfs-skip-metadata-if-null

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/1876.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 #1876


commit 71cc69d73af2ddcd87d48dbf31b85b119afee1af
Author: mgyongyosi 
Date:   2017-08-07T20:02:49Z

CAMEL-11648: skip metadata when it is null




> camel-mongodb-gridfs - Created document cannot be read by the new MongoDB 
> GridFS API
> 
>
> Key: CAMEL-11648
> URL: https://issues.apache.org/jira/browse/CAMEL-11648
> Project: Camel
>  Issue Type: Bug
>  Components: camel-mongodb
>Affects Versions: 2.19.1
>Reporter: Mihály Gyöngyösi
>Priority: Minor
>
> The new MongoDB GridFS API 
> (http://mongodb.github.io/mongo-java-driver/3.5/driver/tutorials/gridfs/) 
> throws an exception when my application (not Camel based) iterates over the 
> GridFS documents created by Camel's {{camel-mongodb-gridfs}} component.
> The problem: the current GridFSProducer adds the "metadata" field regardless 
> it is null. Referring to https://jira.mongodb.org/browse/JAVA-2577 the 
> document should not contain a metadata field if the field is null.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (CAMEL-11648) camel-mongodb-gridfs - Created document cannot be read by the new MongoDB GridFS API

[JIRA]

Mihály Gyöngyösi created CAMEL-11648:


 Summary: camel-mongodb-gridfs - Created document cannot be read by 
the new MongoDB GridFS API
 Key: CAMEL-11648
 URL: https://issues.apache.org/jira/browse/CAMEL-11648
 Project: Camel
  Issue Type: Bug
  Components: camel-mongodb
Affects Versions: 2.19.1
Reporter: Mihály Gyöngyösi
Priority: Minor


The new MongoDB GridFS API 
(http://mongodb.github.io/mongo-java-driver/3.5/driver/tutorials/gridfs/) 
throws an exception when my application (not Camel based) iterates over the 
GridFS documents created by Camel's {{camel-mongodb-gridfs}} component.

The problem: the current GridFSProducer adds the "metadata" field regardless it 
is null. Referring to https://jira.mongodb.org/browse/JAVA-2577 the document 
should not contain a metadata field if the field is null.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Work started] (CAMEL-11580) Add JMX api RouteController and SupervisingRouteController

[Luca Burgazzoli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on CAMEL-11580 started by Luca Burgazzoli.
---
> Add JMX api RouteController and SupervisingRouteController
> --
>
> Key: CAMEL-11580
> URL: https://issues.apache.org/jira/browse/CAMEL-11580
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-core, jmx
>Reporter: Claus Ibsen
>Assignee: Luca Burgazzoli
>  Labels: route-controller
> Fix For: 2.20.0
>
>
> We should have some JMX API that can expose the state of the route, with JMX 
> attributes. Then there should be an extended for SupervisingRouteController 
> which can shows the state of each of those routes, and the backoff 
> configuration etc.
> eg today there is little visibility for end users what is going on with the 
> SupervisingRouteController. We need to expose that in JMX.
> Then we can leverage that also for Spring Boot and have an actuator endpoint 
> (/camel/route-controller) where we can report this state as json.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (CAMEL-11646) Upgrade brave to allow simple MDC logging

[Radek Mensik (JIRA)]

Radek Mensik created CAMEL-11646:


 Summary: Upgrade brave to allow simple MDC logging
 Key: CAMEL-11646
 URL: https://issues.apache.org/jira/browse/CAMEL-11646
 Project: Camel
  Issue Type: New Feature
  Components: camel-opentracing
Affects Versions: 2.19.1
Reporter: Radek Mensik


It would be nice if spans are logged as we know it from spring-sleuth. Simplest 
could be usage of brave-context-slf4j 
https://github.com/openzipkin/brave/tree/master/context/slf4j.
Unfortunately this requires higher version of brave. I tried to make it work 
with 2.20.0-SNAPSHOT but no luck..



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (CAMEL-11647) SupervisingRouteController : add JMX support

[Luca Burgazzoli (JIRA)]

Luca Burgazzoli created CAMEL-11647:
---

 Summary: SupervisingRouteController : add JMX support
 Key: CAMEL-11647
 URL: https://issues.apache.org/jira/browse/CAMEL-11647
 Project: Camel
  Issue Type: Improvement
  Components: camel-core, camel-spring-boot
Reporter: Luca Burgazzoli
Assignee: Luca Burgazzoli
 Fix For: 2.20.0


SupervisingRouteController should expose info about routes it is supervising 
like:

- the back-off configuration
- the status
- when the next restart will happens (i.e. nb of seconds till attempt)
- the last error/stack trace

Camel Spring Boot should leverage this and expose the same information from an 
Endpoints



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11638) Upgrade to Apache SSHD 1.6.x

[Babak Vahdat (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Babak Vahdat updated CAMEL-11638:
-
Fix Version/s: (was: 2.19.3)
   2.20.0

> Upgrade to Apache SSHD 1.6.x
> 
>
> Key: CAMEL-11638
> URL: https://issues.apache.org/jira/browse/CAMEL-11638
> Project: Camel
>  Issue Type: Task
>  Components: camel-ssh
>Reporter: Babak Vahdat
>Assignee: Babak Vahdat
>Priority: Minor
> Fix For: 2.20.0
>
>
> Currently on the master branch we make use of Apache SSHD version {{0.14.0}} 
> which is apparently not binary compatible with {{1.6.x}}, so that it needs a 
> bit of code adjustment to compile and make the tests run green. Probably the 
> corresponding Karaf feature needs some changes as well. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11580) Add JMX api RouteController and SupervisingRouteController

[Luca Burgazzoli (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16116704#comment-16116704
 ] 

Luca Burgazzoli commented on CAMEL-11580:
-

I'm going to split this in two parts:

- this jira to provide a minimal JMX/Endpoint support for plain RouteController 
- a new JIRA to support SupervisingRouteController


> Add JMX api RouteController and SupervisingRouteController
> --
>
> Key: CAMEL-11580
> URL: https://issues.apache.org/jira/browse/CAMEL-11580
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-core, jmx
>Reporter: Claus Ibsen
>Assignee: Luca Burgazzoli
>  Labels: route-controller
> Fix For: 2.20.0
>
>
> We should have some JMX API that can expose the state of the route, with JMX 
> attributes. Then there should be an extended for SupervisingRouteController 
> which can shows the state of each of those routes, and the backoff 
> configuration etc.
> eg today there is little visibility for end users what is going on with the 
> SupervisingRouteController. We need to expose that in JMX.
> Then we can leverage that also for Spring Boot and have an actuator endpoint 
> (/camel/route-controller) where we can report this state as json.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11645) Add possibility to filter routes which will report spans

[Radek Mensik (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radek Mensik updated CAMEL-11645:
-
Description: 
Currently all routes are traced with spans.
It would be nice to somehow filter which routes will be spanned.
First step could be that some concrete endpoints will report span, for example 
only those used for REST communication.

As I had checked Decorators, which are used, modification of method boolean 
newSpan() which will reflect configuration could help us to filter at least 
which endpoint types will be spanning. 

For example RestletSpanDecorator would return true, but all others false.

Best solution would be similar as is in camel-zipkin.

  was:
Currently all routes are traced with spans.
It would be nice to somehow filter which routes will be spanned.
First step could be that some concrete endpoints will report span, for example 
only those used for REST communication.

As I had checked Decorators, which are used, modification of method boolean 
newSpan() which will reflect configuration could help us to filter at least 
which endpoint types will be spanning. 

For example RestletSpanDecorator would return true, but all others false.


> Add possibility to filter routes which will report spans
> 
>
> Key: CAMEL-11645
> URL: https://issues.apache.org/jira/browse/CAMEL-11645
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-opentracing
>Affects Versions: 2.19.1
>Reporter: Radek Mensik
>
> Currently all routes are traced with spans.
> It would be nice to somehow filter which routes will be spanned.
> First step could be that some concrete endpoints will report span, for 
> example only those used for REST communication.
> As I had checked Decorators, which are used, modification of method boolean 
> newSpan() which will reflect configuration could help us to filter at least 
> which endpoint types will be spanning. 
> For example RestletSpanDecorator would return true, but all others false.
> Best solution would be similar as is in camel-zipkin.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (CAMEL-11645) Add possibility to filter routes which will report spans

[Radek Mensik (JIRA)]

Radek Mensik created CAMEL-11645:


 Summary: Add possibility to filter routes which will report spans
 Key: CAMEL-11645
 URL: https://issues.apache.org/jira/browse/CAMEL-11645
 Project: Camel
  Issue Type: New Feature
  Components: camel-opentracing
Affects Versions: 2.19.1
Reporter: Radek Mensik


Currently all routes are traced with spans.
It would be nice to somehow filter which routes will be spanned.
First step could be that some concrete endpoints will report span, for example 
only those used for REST communication.

As I had checked Decorators, which are used, modification of method boolean 
newSpan() which will reflect configuration could help us to filter at least 
which endpoint types will be spanning. 

For example RestletSpanDecorator would return true, but all others false.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (CAMEL-11644) Create a Camel-gRPC example

[Andrea Cosentino (JIRA)]

Andrea Cosentino created CAMEL-11644:


 Summary: Create a Camel-gRPC example
 Key: CAMEL-11644
 URL: https://issues.apache.org/jira/browse/CAMEL-11644
 Project: Camel
  Issue Type: Task
  Components: examples
Reporter: Andrea Cosentino
Assignee: Andrea Cosentino
Priority: Minor
 Fix For: 2.20.0






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Work started] (CAMEL-11640) SupervisingRouteController : Add a SPI to filter routes to supervise

[Luca Burgazzoli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on CAMEL-11640 started by Luca Burgazzoli.
---
> SupervisingRouteController : Add a SPI to filter routes to supervise
> 
>
> Key: CAMEL-11640
> URL: https://issues.apache.org/jira/browse/CAMEL-11640
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core, camel-spring-boot
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
>  Labels: route-controller
> Fix For: 2.20.0
>
>
> Add a SPI to filter routes not to be supervised



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (CAMEL-11617) spring-boot - service-call tests uses hardcoded port numbers

[Luca Burgazzoli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Luca Burgazzoli closed CAMEL-11617.
---
Resolution: Fixed

> spring-boot - service-call tests uses hardcoded port numbers
> 
>
> Key: CAMEL-11617
> URL: https://issues.apache.org/jira/browse/CAMEL-11617
> Project: Camel
>  Issue Type: Test
>  Components: tests
>Reporter: Claus Ibsen
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.20.0
>
>
> They tend to fail on CI servers with Port number in use errors
> Its in camel-spring-boot, camel-spring-cloud, and camel-spring-cloud-netflix 
> etc.
> Failed
> org.apache.camel.spring.boot.cloud.CamelCloudServiceCallTest.testServiceCall
> Failing for the past 3 builds (Since Unstable#1564 )
> Took 6 ms.
> Error Message
> Failed to load ApplicationContext
> Stacktrace
> java.lang.IllegalStateException: Failed to load ApplicationContext
> Caused by: org.apache.camel.RuntimeCamelException: java.net.BindException: 
> Address already in use
> Caused by: java.net.BindException: Address already in use



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11617) spring-boot - service-call tests uses hardcoded port numbers

[Luca Burgazzoli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Luca Burgazzoli updated CAMEL-11617:

Fix Version/s: (was: Future)
   2.20.0

> spring-boot - service-call tests uses hardcoded port numbers
> 
>
> Key: CAMEL-11617
> URL: https://issues.apache.org/jira/browse/CAMEL-11617
> Project: Camel
>  Issue Type: Test
>  Components: tests
>Reporter: Claus Ibsen
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.20.0
>
>
> They tend to fail on CI servers with Port number in use errors
> Its in camel-spring-boot, camel-spring-cloud, and camel-spring-cloud-netflix 
> etc.
> Failed
> org.apache.camel.spring.boot.cloud.CamelCloudServiceCallTest.testServiceCall
> Failing for the past 3 builds (Since Unstable#1564 )
> Took 6 ms.
> Error Message
> Failed to load ApplicationContext
> Stacktrace
> java.lang.IllegalStateException: Failed to load ApplicationContext
> Caused by: org.apache.camel.RuntimeCamelException: java.net.BindException: 
> Address already in use
> Caused by: java.net.BindException: Address already in use



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (CAMEL-11617) spring-boot - service-call tests uses hardcoded port numbers

[Luca Burgazzoli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Luca Burgazzoli reassigned CAMEL-11617:
---

Assignee: Luca Burgazzoli

> spring-boot - service-call tests uses hardcoded port numbers
> 
>
> Key: CAMEL-11617
> URL: https://issues.apache.org/jira/browse/CAMEL-11617
> Project: Camel
>  Issue Type: Test
>  Components: tests
>Reporter: Claus Ibsen
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.20.0
>
>
> They tend to fail on CI servers with Port number in use errors
> Its in camel-spring-boot, camel-spring-cloud, and camel-spring-cloud-netflix 
> etc.
> Failed
> org.apache.camel.spring.boot.cloud.CamelCloudServiceCallTest.testServiceCall
> Failing for the past 3 builds (Since Unstable#1564 )
> Took 6 ms.
> Error Message
> Failed to load ApplicationContext
> Stacktrace
> java.lang.IllegalStateException: Failed to load ApplicationContext
> Caused by: org.apache.camel.RuntimeCamelException: java.net.BindException: 
> Address already in use
> Caused by: java.net.BindException: Address already in use



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11617) spring-boot - service-call tests uses hardcoded port numbers

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16116374#comment-16116374
 ] 

ASF GitHub Bot commented on CAMEL-11617:


Github user asfgit closed the pull request at:

https://github.com/apache/camel/pull/1871


> spring-boot - service-call tests uses hardcoded port numbers
> 
>
> Key: CAMEL-11617
> URL: https://issues.apache.org/jira/browse/CAMEL-11617
> Project: Camel
>  Issue Type: Test
>  Components: tests
>Reporter: Claus Ibsen
>Priority: Minor
> Fix For: Future
>
>
> They tend to fail on CI servers with Port number in use errors
> Its in camel-spring-boot, camel-spring-cloud, and camel-spring-cloud-netflix 
> etc.
> Failed
> org.apache.camel.spring.boot.cloud.CamelCloudServiceCallTest.testServiceCall
> Failing for the past 3 builds (Since Unstable#1564 )
> Took 6 ms.
> Error Message
> Failed to load ApplicationContext
> Stacktrace
> java.lang.IllegalStateException: Failed to load ApplicationContext
> Caused by: org.apache.camel.RuntimeCamelException: java.net.BindException: 
> Address already in use
> Caused by: java.net.BindException: Address already in use



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (CAMEL-11643) Extensions: registerExtension method has to avoid final in his declaration to work in CDI

[Luca Burgazzoli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Luca Burgazzoli resolved CAMEL-11643.
-
Resolution: Fixed

> Extensions: registerExtension method has to avoid final in his declaration to 
> work in CDI
> -
>
> Key: CAMEL-11643
> URL: https://issues.apache.org/jira/browse/CAMEL-11643
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core, examples
>Reporter: Andrea Cosentino
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.20.0
>
>
> For example in the examples camel-example-cdi-properties we are currently 
> getting an error:
> {code}
> [INFO] ---
> [INFO]  T E S T S
> [INFO] ---
> [INFO] Running org.apache.camel.example.cdi.properties.CdiPropertiesTest
> 2017-08-07 10:40:08,567 [main   ] INFO  Version   
>  - WELD-000900: 2.4.4 (Final)
> 2017-08-07 10:40:08,726 [main   ] INFO  Bootstrap 
>  - WELD-000101: Transactional services not available. Injection of @Inject 
> UserTransaction not available. Transactional observers will be invoked 
> synchronously.
> 2017-08-07 10:40:08,824 [main   ] INFO  Event 
>  - WELD-000411: Observer method [BackedAnnotatedMethod] private 
> org.apache.camel.cdi.CdiCamelExtension.processAnnotatedType(@Observes 
> ProcessAnnotatedType) receives events for all annotated types. Consider 
> restricting events using @WithAnnotations or a generic type with bounds.
> 2017-08-07 10:40:08,828 [main   ] INFO  Event 
>  - WELD-000411: Observer method [BackedAnnotatedMethod] private 
> org.apache.camel.cdi.CdiCamelExtension.processAnnotatedType(@Observes 
> ProcessAnnotatedType) receives events for all annotated types. Consider 
> restricting events using @WithAnnotations or a generic type with bounds.
> 2017-08-07 10:40:08,831 [main   ] INFO  Event 
>  - WELD-000411: Observer method [BackedAnnotatedMethod] protected 
> org.apache.deltaspike.core.impl.interceptor.GlobalInterceptorExtension.promoteInterceptors(@Observes
>  ProcessAnnotatedType, BeanManager) receives events for all annotated types. 
> Consider restricting events using @WithAnnotations or a generic type with 
> bounds.
> 2017-08-07 10:40:08,839 [main   ] INFO  Event 
>  - WELD-000411: Observer method [BackedAnnotatedMethod] public 
> org.apache.deltaspike.core.impl.config.ConfigurationExtension.findDynamicConfigurationBeans(@Observes
>  ProcessAnnotatedType) receives events for all annotated types. Consider 
> restricting events using @WithAnnotations or a generic type with bounds.
> 2017-08-07 10:40:08,841 [main   ] INFO  Event 
>  - WELD-000411: Observer method [BackedAnnotatedMethod] protected 
> org.apache.deltaspike.core.impl.message.MessageBundleExtension.detectInterfaces(@Observes
>  ProcessAnnotatedType) receives events for all annotated types. Consider 
> restricting events using @WithAnnotations or a generic type with bounds.
> 2017-08-07 10:40:08,846 [main   ] INFO  Event 
>  - WELD-000411: Observer method [BackedAnnotatedMethod] protected 
> org.apache.deltaspike.core.impl.exclude.extension.ExcludeExtension.vetoBeans(@Observes
>  ProcessAnnotatedType, BeanManager) receives events for all annotated types. 
> Consider restricting events using @WithAnnotations or a generic type with 
> bounds.
> 2017-08-07 10:40:09,090 [main   ] WARN  Validator 
>  - WELD-001478: Interceptor class 
> org.apache.deltaspike.core.impl.throttling.ThrottledInterceptor is enabled 
> for the application and for the bean archive 
> /home/oscerd/.m2/repository/org/apache/deltaspike/core/deltaspike-core-impl/1.8.0/deltaspike-core-impl-1.8.0.jar.
>  It will only be invoked in the @Priority part of the chain.
> 2017-08-07 10:40:09,091 [main   ] WARN  Validator 
>  - WELD-001478: Interceptor class 
> org.apache.deltaspike.core.impl.lock.LockedInterceptor is enabled for the 
> application and for the bean archive 
> /home/oscerd/.m2/repository/org/apache/deltaspike/core/deltaspike-core-impl/1.8.0/deltaspike-core-impl-1.8.0.jar.
>  It will only be invoked in the @Priority part of the chain.
> 2017-08-07 10:40:09,091 [main   ] WARN  Validator 
>  - WELD-001478: Interceptor class 
> org.apache.deltaspike.core.impl.future.FutureableInterceptor is enabled for 
> the application and for the bean archive 
> 

[jira] [Updated] (CAMEL-11587) SupervisingRouteController : add option for initial delay

[Luca Burgazzoli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Luca Burgazzoli updated CAMEL-11587:

Summary: SupervisingRouteController : add option for initial delay  (was: 
Backoff - Add option for initial delay)

> SupervisingRouteController : add option for initial delay
> -
>
> Key: CAMEL-11587
> URL: https://issues.apache.org/jira/browse/CAMEL-11587
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Luca Burgazzoli
>  Labels: route-controller
> Fix For: 2.20.0
>
>
> So you can set an initial delay, so the routes are not started asap.
> For example
> {code}
> camel.supervising.controller.routes.undertow.back-off.initial-delay = 10s
> camel.supervising.controller.routes.undertow.back-off.delay = 20s
> camel.supervising.controller.routes.undertow.back-off.max-attempts = 3
> {code}
> Then the first start is initially started after 10 seconds.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11640) SupervisingRouteController : Add a SPI to filter routes to supervise

[Luca Burgazzoli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Luca Burgazzoli updated CAMEL-11640:

Summary: SupervisingRouteController : Add a SPI to filter routes to 
supervise  (was: SupervisingRouteController : Add a SPI to filter routes not to 
be supervised)

> SupervisingRouteController : Add a SPI to filter routes to supervise
> 
>
> Key: CAMEL-11640
> URL: https://issues.apache.org/jira/browse/CAMEL-11640
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core, camel-spring-boot
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
>  Labels: route-controller
> Fix For: 2.20.0
>
>
> Add a SPI to filter routes not to be supervised



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Work started] (CAMEL-11587) Backoff - Add option for initial delay

[Luca Burgazzoli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on CAMEL-11587 started by Luca Burgazzoli.
---
> Backoff - Add option for initial delay
> --
>
> Key: CAMEL-11587
> URL: https://issues.apache.org/jira/browse/CAMEL-11587
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Luca Burgazzoli
>  Labels: route-controller
> Fix For: 2.20.0
>
>
> So you can set an initial delay, so the routes are not started asap.
> For example
> {code}
> camel.supervising.controller.routes.undertow.back-off.initial-delay = 10s
> camel.supervising.controller.routes.undertow.back-off.delay = 20s
> camel.supervising.controller.routes.undertow.back-off.max-attempts = 3
> {code}
> Then the first start is initially started after 10 seconds.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11635) wrong groupId in camel examples readme.md and features.xml

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16116295#comment-16116295
 ] 

ASF GitHub Bot commented on CAMEL-11635:


Github user valdar closed the pull request at:

https://github.com/apache/camel/pull/1874


> wrong groupId in camel examples readme.md and features.xml
> --
>
> Key: CAMEL-11635
> URL: https://issues.apache.org/jira/browse/CAMEL-11635
> Project: Camel
>  Issue Type: Task
>  Components: examples
>Reporter: Andrea Tarocchi
>Assignee: Andrea Cosentino
> Fix For: 2.20.0
>
>
> There are a number of wrong groupId (probably because examples have been 
> moved form {{org.apache.camel}} to {{org.apache.camel.example}} ? ) in 
> {{examples/}} both in {{features.xml}} and in {{readme.md}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11643) Extensions: registerExtension method has to avoid final in his declaration to work in CDI

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino updated CAMEL-11643:
-
Summary: Extensions: registerExtension method has to avoid final in his 
declaration to work in CDI  (was: Extensions: registerExtensions method has to 
avoid final in his declaration to work in CDI)

> Extensions: registerExtension method has to avoid final in his declaration to 
> work in CDI
> -
>
> Key: CAMEL-11643
> URL: https://issues.apache.org/jira/browse/CAMEL-11643
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core, examples
>Reporter: Andrea Cosentino
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.20.0
>
>
> For example in the examples camel-example-cdi-properties we are currently 
> getting an error:
> {code}
> [INFO] ---
> [INFO]  T E S T S
> [INFO] ---
> [INFO] Running org.apache.camel.example.cdi.properties.CdiPropertiesTest
> 2017-08-07 10:40:08,567 [main   ] INFO  Version   
>  - WELD-000900: 2.4.4 (Final)
> 2017-08-07 10:40:08,726 [main   ] INFO  Bootstrap 
>  - WELD-000101: Transactional services not available. Injection of @Inject 
> UserTransaction not available. Transactional observers will be invoked 
> synchronously.
> 2017-08-07 10:40:08,824 [main   ] INFO  Event 
>  - WELD-000411: Observer method [BackedAnnotatedMethod] private 
> org.apache.camel.cdi.CdiCamelExtension.processAnnotatedType(@Observes 
> ProcessAnnotatedType) receives events for all annotated types. Consider 
> restricting events using @WithAnnotations or a generic type with bounds.
> 2017-08-07 10:40:08,828 [main   ] INFO  Event 
>  - WELD-000411: Observer method [BackedAnnotatedMethod] private 
> org.apache.camel.cdi.CdiCamelExtension.processAnnotatedType(@Observes 
> ProcessAnnotatedType) receives events for all annotated types. Consider 
> restricting events using @WithAnnotations or a generic type with bounds.
> 2017-08-07 10:40:08,831 [main   ] INFO  Event 
>  - WELD-000411: Observer method [BackedAnnotatedMethod] protected 
> org.apache.deltaspike.core.impl.interceptor.GlobalInterceptorExtension.promoteInterceptors(@Observes
>  ProcessAnnotatedType, BeanManager) receives events for all annotated types. 
> Consider restricting events using @WithAnnotations or a generic type with 
> bounds.
> 2017-08-07 10:40:08,839 [main   ] INFO  Event 
>  - WELD-000411: Observer method [BackedAnnotatedMethod] public 
> org.apache.deltaspike.core.impl.config.ConfigurationExtension.findDynamicConfigurationBeans(@Observes
>  ProcessAnnotatedType) receives events for all annotated types. Consider 
> restricting events using @WithAnnotations or a generic type with bounds.
> 2017-08-07 10:40:08,841 [main   ] INFO  Event 
>  - WELD-000411: Observer method [BackedAnnotatedMethod] protected 
> org.apache.deltaspike.core.impl.message.MessageBundleExtension.detectInterfaces(@Observes
>  ProcessAnnotatedType) receives events for all annotated types. Consider 
> restricting events using @WithAnnotations or a generic type with bounds.
> 2017-08-07 10:40:08,846 [main   ] INFO  Event 
>  - WELD-000411: Observer method [BackedAnnotatedMethod] protected 
> org.apache.deltaspike.core.impl.exclude.extension.ExcludeExtension.vetoBeans(@Observes
>  ProcessAnnotatedType, BeanManager) receives events for all annotated types. 
> Consider restricting events using @WithAnnotations or a generic type with 
> bounds.
> 2017-08-07 10:40:09,090 [main   ] WARN  Validator 
>  - WELD-001478: Interceptor class 
> org.apache.deltaspike.core.impl.throttling.ThrottledInterceptor is enabled 
> for the application and for the bean archive 
> /home/oscerd/.m2/repository/org/apache/deltaspike/core/deltaspike-core-impl/1.8.0/deltaspike-core-impl-1.8.0.jar.
>  It will only be invoked in the @Priority part of the chain.
> 2017-08-07 10:40:09,091 [main   ] WARN  Validator 
>  - WELD-001478: Interceptor class 
> org.apache.deltaspike.core.impl.lock.LockedInterceptor is enabled for the 
> application and for the bean archive 
> /home/oscerd/.m2/repository/org/apache/deltaspike/core/deltaspike-core-impl/1.8.0/deltaspike-core-impl-1.8.0.jar.
>  It will only be invoked in the @Priority part of the chain.
> 2017-08-07 10:40:09,091 [main   ] WARN  Validator 
>  - WELD-001478: Interceptor class 
> 

[jira] [Created] (CAMEL-11643) Extensions: registerExtensions method has to avoid final in his declaration to work in CDI

[Andrea Cosentino (JIRA)]

Andrea Cosentino created CAMEL-11643:


 Summary: Extensions: registerExtensions method has to avoid final 
in his declaration to work in CDI
 Key: CAMEL-11643
 URL: https://issues.apache.org/jira/browse/CAMEL-11643
 Project: Camel
  Issue Type: Bug
  Components: camel-core, examples
Reporter: Andrea Cosentino
Assignee: Luca Burgazzoli
Priority: Minor
 Fix For: 2.20.0


For example in the examples camel-example-cdi-properties we are currently 
getting an error:

{code}
[INFO] ---
[INFO]  T E S T S
[INFO] ---
[INFO] Running org.apache.camel.example.cdi.properties.CdiPropertiesTest
2017-08-07 10:40:08,567 [main   ] INFO  Version
- WELD-000900: 2.4.4 (Final)
2017-08-07 10:40:08,726 [main   ] INFO  Bootstrap  
- WELD-000101: Transactional services not available. Injection of @Inject 
UserTransaction not available. Transactional observers will be invoked 
synchronously.
2017-08-07 10:40:08,824 [main   ] INFO  Event  
- WELD-000411: Observer method [BackedAnnotatedMethod] private 
org.apache.camel.cdi.CdiCamelExtension.processAnnotatedType(@Observes 
ProcessAnnotatedType) receives events for all annotated types. Consider 
restricting events using @WithAnnotations or a generic type with bounds.
2017-08-07 10:40:08,828 [main   ] INFO  Event  
- WELD-000411: Observer method [BackedAnnotatedMethod] private 
org.apache.camel.cdi.CdiCamelExtension.processAnnotatedType(@Observes 
ProcessAnnotatedType) receives events for all annotated types. Consider 
restricting events using @WithAnnotations or a generic type with bounds.
2017-08-07 10:40:08,831 [main   ] INFO  Event  
- WELD-000411: Observer method [BackedAnnotatedMethod] protected 
org.apache.deltaspike.core.impl.interceptor.GlobalInterceptorExtension.promoteInterceptors(@Observes
 ProcessAnnotatedType, BeanManager) receives events for all annotated types. 
Consider restricting events using @WithAnnotations or a generic type with 
bounds.
2017-08-07 10:40:08,839 [main   ] INFO  Event  
- WELD-000411: Observer method [BackedAnnotatedMethod] public 
org.apache.deltaspike.core.impl.config.ConfigurationExtension.findDynamicConfigurationBeans(@Observes
 ProcessAnnotatedType) receives events for all annotated types. Consider 
restricting events using @WithAnnotations or a generic type with bounds.
2017-08-07 10:40:08,841 [main   ] INFO  Event  
- WELD-000411: Observer method [BackedAnnotatedMethod] protected 
org.apache.deltaspike.core.impl.message.MessageBundleExtension.detectInterfaces(@Observes
 ProcessAnnotatedType) receives events for all annotated types. Consider 
restricting events using @WithAnnotations or a generic type with bounds.
2017-08-07 10:40:08,846 [main   ] INFO  Event  
- WELD-000411: Observer method [BackedAnnotatedMethod] protected 
org.apache.deltaspike.core.impl.exclude.extension.ExcludeExtension.vetoBeans(@Observes
 ProcessAnnotatedType, BeanManager) receives events for all annotated types. 
Consider restricting events using @WithAnnotations or a generic type with 
bounds.
2017-08-07 10:40:09,090 [main   ] WARN  Validator  
- WELD-001478: Interceptor class 
org.apache.deltaspike.core.impl.throttling.ThrottledInterceptor is enabled for 
the application and for the bean archive 
/home/oscerd/.m2/repository/org/apache/deltaspike/core/deltaspike-core-impl/1.8.0/deltaspike-core-impl-1.8.0.jar.
 It will only be invoked in the @Priority part of the chain.
2017-08-07 10:40:09,091 [main   ] WARN  Validator  
- WELD-001478: Interceptor class 
org.apache.deltaspike.core.impl.lock.LockedInterceptor is enabled for the 
application and for the bean archive 
/home/oscerd/.m2/repository/org/apache/deltaspike/core/deltaspike-core-impl/1.8.0/deltaspike-core-impl-1.8.0.jar.
 It will only be invoked in the @Priority part of the chain.
2017-08-07 10:40:09,091 [main   ] WARN  Validator  
- WELD-001478: Interceptor class 
org.apache.deltaspike.core.impl.future.FutureableInterceptor is enabled for the 
application and for the bean archive 
/home/oscerd/.m2/repository/org/apache/deltaspike/core/deltaspike-core-impl/1.8.0/deltaspike-core-impl-1.8.0.jar.
 It will only be invoked in the @Priority part of the chain.
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.14 s 
<<< FAILURE! - in org.apache.camel.example.cdi.properties.CdiPropertiesTest
[ERROR] org.apache.camel.example.cdi.properties.CdiPropertiesTest  Time 
elapsed: 1.14 s  <<< ERROR!

[jira] [Resolved] (CAMEL-11635) wrong groupId in camel examples readme.md and features.xml

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino resolved CAMEL-11635.
--
Resolution: Fixed

> wrong groupId in camel examples readme.md and features.xml
> --
>
> Key: CAMEL-11635
> URL: https://issues.apache.org/jira/browse/CAMEL-11635
> Project: Camel
>  Issue Type: Task
>  Components: examples
>Reporter: Andrea Tarocchi
> Fix For: 2.20.0
>
>
> There are a number of wrong groupId (probably because examples have been 
> moved form {{org.apache.camel}} to {{org.apache.camel.example}} ? ) in 
> {{examples/}} both in {{features.xml}} and in {{readme.md}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (CAMEL-11635) wrong groupId in camel examples readme.md and features.xml

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino reassigned CAMEL-11635:


Assignee: Andrea Cosentino

> wrong groupId in camel examples readme.md and features.xml
> --
>
> Key: CAMEL-11635
> URL: https://issues.apache.org/jira/browse/CAMEL-11635
> Project: Camel
>  Issue Type: Task
>  Components: examples
>Reporter: Andrea Tarocchi
>Assignee: Andrea Cosentino
> Fix For: 2.20.0
>
>
> There are a number of wrong groupId (probably because examples have been 
> moved form {{org.apache.camel}} to {{org.apache.camel.example}} ? ) in 
> {{examples/}} both in {{features.xml}} and in {{readme.md}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11642) Broker Credentials should be set from endpoint

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16116278#comment-16116278
 ] 

ASF GitHub Bot commented on CAMEL-11642:


Github user Fabryprog closed the pull request at:

https://github.com/apache/camel/pull/1875


> Broker Credentials should be set from endpoint
> --
>
> Key: CAMEL-11642
> URL: https://issues.apache.org/jira/browse/CAMEL-11642
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-paho
>Affects Versions: 2.19.2
>Reporter: Fabrizio Spataro
>Assignee: Fabrizio Spataro
> Fix For: 2.20.0
>
>
> current camel-paho component uses a MqttConnectOptions to set broker 
> credentials.
> It is a very limit into a dynamically application. The credential should be 
> configured from endpoint too (like qos and retain flag)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11642) Broker Credentials should be set from endpoint

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino updated CAMEL-11642:
-
Fix Version/s: 2.20.0

> Broker Credentials should be set from endpoint
> --
>
> Key: CAMEL-11642
> URL: https://issues.apache.org/jira/browse/CAMEL-11642
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-paho
>Affects Versions: 2.19.2
>Reporter: Fabrizio Spataro
>Assignee: Fabrizio Spataro
> Fix For: 2.20.0
>
>
> current camel-paho component uses a MqttConnectOptions to set broker 
> credentials.
> It is a very limit into a dynamically application. The credential should be 
> configured from endpoint too (like qos and retain flag)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (CAMEL-11642) Broker Credentials should be set from endpoint

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino resolved CAMEL-11642.
--
Resolution: Fixed

> Broker Credentials should be set from endpoint
> --
>
> Key: CAMEL-11642
> URL: https://issues.apache.org/jira/browse/CAMEL-11642
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-paho
>Affects Versions: 2.19.2
>Reporter: Fabrizio Spataro
>Assignee: Fabrizio Spataro
> Fix For: 2.20.0
>
>
> current camel-paho component uses a MqttConnectOptions to set broker 
> credentials.
> It is a very limit into a dynamically application. The credential should be 
> configured from endpoint too (like qos and retain flag)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (CAMEL-11637) Unable to assign null value to a Salesforce object field

[Zoran Regvart (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zoran Regvart reassigned CAMEL-11637:
-

Assignee: Zoran Regvart

> Unable to assign null value to a Salesforce object field
> 
>
> Key: CAMEL-11637
> URL: https://issues.apache.org/jira/browse/CAMEL-11637
> Project: Camel
>  Issue Type: Bug
>  Components: camel-salesforce
>Affects Versions: 2.19.1
>Reporter: Roman Kalashnikov
>Assignee: Zoran Regvart
>
> When in Salesforce I have an object with a nullable field, and want to set 
> its value to null, there's no way to do it.
> Actually it's enough to pass empty string ("") or null as field value to SF 
> REST API to set field to null.
> Both
> {code}
> {
>   "PoBox__c": null
> }
> {code}
> and
> {code}
> {
>   "PoBox__c": ""
> }
> {code}
> are valid.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (CAMEL-11636) property placeholder is not replaced in REST DSL in blueprint context

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-11636.
-
Resolution: Fixed

Thanks for reporting

> property placeholder is not replaced in REST DSL in blueprint context
> -
>
> Key: CAMEL-11636
> URL: https://issues.apache.org/jira/browse/CAMEL-11636
> Project: Camel
>  Issue Type: Bug
>  Components: camel-blueprint, rest
>Affects Versions: 2.19.1
> Environment: Apache Karaf 4.0.9 running on OSX 10.12.5
>Reporter: Claudia S
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.20.0, 2.19.3
>
>
> I'm trying to update from Camel 2.16.3 to 2.19.1 and experience issues using 
> properties in the REST DSL in blueprint context.
> I have the following config:
> {code}
>  path="patient/{patient_id}/events?cutoff_timestamp={cutoff_timestamp}limit={limit}"
>  produces="application/json" consumes="application/json">
> 
>  required="true" />
>  required="false" />
>  required="false" defaultValue="{{vel.rest.default.rowlimit}}" />
> {code}   
> For the param "limit" the property vel.rest.default.rowlimit used in 
> attribute defaultValue seems not to get replaced as I receive the following 
> exception:
> {code}
> java.lang.NumberFormatException: For input string: 
> "{{vel.rest.default.rowlimit}}"
> {code}
> 
> Originally asked on the mailing list: 
> http://camel.465427.n5.nabble.com/issue-with-property-in-REST-DSL-in-blueprint-context-Camel-2-19-1-td5809573.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11642) Broker Credentials should be set from endpoint

[Fabrizio Spataro (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Fabrizio Spataro updated CAMEL-11642:
-
Summary: Broker Credentials should be set from endpoint  (was: Broken 
Credentials should be set from endpoint)

> Broker Credentials should be set from endpoint
> --
>
> Key: CAMEL-11642
> URL: https://issues.apache.org/jira/browse/CAMEL-11642
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-paho
>Affects Versions: 2.19.2
>Reporter: Fabrizio Spataro
>Assignee: Fabrizio Spataro
>
> current camel-paho component uses a MqttConnectOptions to set broker 
> credentials.
> It is a very limit into a dynamically application. The credential should be 
> configured from endpoint too (like qos and retain flag)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11642) Broken Credentials should be set from endpoint

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16116219#comment-16116219
 ] 

ASF GitHub Bot commented on CAMEL-11642:


GitHub user Fabryprog opened a pull request:

https://github.com/apache/camel/pull/1875

CAMEL-11642: Broken Credentials should be set from endpoint

https://issues.apache.org/jira/browse/CAMEL-11642

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Fabryprog/camel CAMEL-11642

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/1875.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 #1875


commit 12923a9873cd2da5e7ef112a8cda140016cc0878
Author: Fabrizio Spataro 
Date:   2017-08-07T08:07:27Z

Broken Credentials should be set from endpoint




> Broken Credentials should be set from endpoint
> --
>
> Key: CAMEL-11642
> URL: https://issues.apache.org/jira/browse/CAMEL-11642
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-paho
>Affects Versions: 2.19.2
>Reporter: Fabrizio Spataro
>Assignee: Fabrizio Spataro
>
> current camel-paho component uses a MqttConnectOptions to set broker 
> credentials.
> It is a very limit into a dynamically application. The credential should be 
> configured from endpoint too (like qos and retain flag)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (CAMEL-11642) Broken Credentials should be set from endpoint

[Fabrizio Spataro (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Fabrizio Spataro reassigned CAMEL-11642:


Assignee: Fabrizio Spataro

> Broken Credentials should be set from endpoint
> --
>
> Key: CAMEL-11642
> URL: https://issues.apache.org/jira/browse/CAMEL-11642
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-paho
>Affects Versions: 2.19.2
>Reporter: Fabrizio Spataro
>Assignee: Fabrizio Spataro
>
> current camel-paho component uses a MqttConnectOptions to set broker 
> credentials.
> It is a very limit into a dynamically application. The credential should be 
> configured from endpoint too (like qos and retain flag)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (CAMEL-11642) Broken Credentials should be set from endpoint

[Fabrizio Spataro (JIRA)]

Fabrizio Spataro created CAMEL-11642:


 Summary: Broken Credentials should be set from endpoint
 Key: CAMEL-11642
 URL: https://issues.apache.org/jira/browse/CAMEL-11642
 Project: Camel
  Issue Type: Improvement
  Components: camel-paho
Affects Versions: 2.19.2
Reporter: Fabrizio Spataro


current camel-paho component uses a MqttConnectOptions to set broker 
credentials.

It is a very limit into a dynamically application. The credential should be 
configured from endpoint too (like qos and retain flag)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (CAMEL-11634) clean up dbcp 1 dependencies and move it (where possible) to dbcp 2

[Andrea Tarocchi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Tarocchi resolved CAMEL-11634.
-
Resolution: Fixed

> clean up dbcp 1 dependencies and move it (where possible) to dbcp 2
> ---
>
> Key: CAMEL-11634
> URL: https://issues.apache.org/jira/browse/CAMEL-11634
> Project: Camel
>  Issue Type: Improvement
>Reporter: Andrea Tarocchi
>Assignee: Andrea Cosentino
> Fix For: 2.20.0
>
>
> dbcp 1 is quite old and I've noticed a couple of places where that dependency 
> is declared but actually never used. Would be good to have them cleaned up 
> and bumped to version 2 when possible. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Work started] (CAMEL-11641) SupervisingRouteController : backOff should be renamed deaultBackoff

[Luca Burgazzoli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on CAMEL-11641 started by Luca Burgazzoli.
---
> SupervisingRouteController : backOff should be renamed deaultBackoff
> 
>
> Key: CAMEL-11641
> URL: https://issues.apache.org/jira/browse/CAMEL-11641
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-spring-boot
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
>  Labels: route-controller
> Fix For: 2.20.0
>
>
> SupervisingRouteController has default-back-off property whereas the starter 
> has back-off



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (CAMEL-11641) SupervisingRouteController : backOff should be renamed deaultBackoff

[Luca Burgazzoli (JIRA)]

Luca Burgazzoli created CAMEL-11641:
---

 Summary: SupervisingRouteController : backOff should be renamed 
deaultBackoff
 Key: CAMEL-11641
 URL: https://issues.apache.org/jira/browse/CAMEL-11641
 Project: Camel
  Issue Type: Improvement
  Components: camel-spring-boot
Reporter: Luca Burgazzoli
Assignee: Luca Burgazzoli
Priority: Minor
 Fix For: 2.20.0


SupervisingRouteController has default-back-off property whereas the starter 
has back-off



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11587) Backoff - Add option for initial delay

[Claus Ibsen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16116179#comment-16116179
 ] 

Claus Ibsen commented on CAMEL-11587:
-

Yes I think the scheduled thread pool has this functionality.

> Backoff - Add option for initial delay
> --
>
> Key: CAMEL-11587
> URL: https://issues.apache.org/jira/browse/CAMEL-11587
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Luca Burgazzoli
>  Labels: route-controller
> Fix For: 2.20.0
>
>
> So you can set an initial delay, so the routes are not started asap.
> For example
> {code}
> camel.supervising.controller.routes.undertow.back-off.initial-delay = 10s
> camel.supervising.controller.routes.undertow.back-off.delay = 20s
> camel.supervising.controller.routes.undertow.back-off.max-attempts = 3
> {code}
> Then the first start is initially started after 10 seconds.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11587) Backoff - Add option for initial delay

[Luca Burgazzoli (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16116174#comment-16116174
 ] 

Luca Burgazzoli commented on CAMEL-11587:
-

Do you mean to have a delay to start routes some time after the context has 
been started ?

> Backoff - Add option for initial delay
> --
>
> Key: CAMEL-11587
> URL: https://issues.apache.org/jira/browse/CAMEL-11587
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Luca Burgazzoli
>  Labels: route-controller
> Fix For: 2.20.0
>
>
> So you can set an initial delay, so the routes are not started asap.
> For example
> {code}
> camel.supervising.controller.routes.undertow.back-off.initial-delay = 10s
> camel.supervising.controller.routes.undertow.back-off.delay = 20s
> camel.supervising.controller.routes.undertow.back-off.max-attempts = 3
> {code}
> Then the first start is initially started after 10 seconds.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11636) property placeholder is not replaced in REST DSL in blueprint context

[Claus Ibsen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16116168#comment-16116168
 ] 

Claus Ibsen commented on CAMEL-11636:
-

This requires to be pre resolved as the swagger javadoc need to include the 
resolved value as well.

> property placeholder is not replaced in REST DSL in blueprint context
> -
>
> Key: CAMEL-11636
> URL: https://issues.apache.org/jira/browse/CAMEL-11636
> Project: Camel
>  Issue Type: Bug
>  Components: camel-blueprint, rest
>Affects Versions: 2.19.1
> Environment: Apache Karaf 4.0.9 running on OSX 10.12.5
>Reporter: Claudia S
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.20.0, 2.19.3
>
>
> I'm trying to update from Camel 2.16.3 to 2.19.1 and experience issues using 
> properties in the REST DSL in blueprint context.
> I have the following config:
> {code}
>  path="patient/{patient_id}/events?cutoff_timestamp={cutoff_timestamp}limit={limit}"
>  produces="application/json" consumes="application/json">
> 
>  required="true" />
>  required="false" />
>  required="false" defaultValue="{{vel.rest.default.rowlimit}}" />
> {code}   
> For the param "limit" the property vel.rest.default.rowlimit used in 
> attribute defaultValue seems not to get replaced as I receive the following 
> exception:
> {code}
> java.lang.NumberFormatException: For input string: 
> "{{vel.rest.default.rowlimit}}"
> {code}
> 
> Originally asked on the mailing list: 
> http://camel.465427.n5.nabble.com/issue-with-property-in-REST-DSL-in-blueprint-context-Camel-2-19-1-td5809573.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11585) camel-spring-boot - Allow to reset route statistics via actuator

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16116159#comment-16116159
 ] 

ASF GitHub Bot commented on CAMEL-11585:


Github user vrlgohel closed the pull request at:

https://github.com/apache/camel/pull/1864


> camel-spring-boot - Allow to reset route statistics via actuator
> 
>
> Key: CAMEL-11585
> URL: https://issues.apache.org/jira/browse/CAMEL-11585
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-spring-boot
>Reporter: Claus Ibsen
>Assignee: Viral Gohel
>Priority: Minor
> Fix For: 2.20.0
>
>
> You can start/stop/suspend/resume routes etc. But it would also be nice to be 
> able to reset the JMX statistics.
> for example if you stop and start a route, then it continues with the 
> existing JMX stats (but sometimes you want to be able to reset).
> {code}
> 8080/camel/routes/bar/info
> {"id":"bar","uptimeMillis":0,"status":"Stopped","details":{"deltaProcessingTime":0,"exchangesInflight":0,"exchangesTotal":103,"externalRedeliveries":0,"failuresHandled":0,"firstExchangeCompletedExchangeId":"ID-davsclaus-pro-local-1500797880917-0-1","firstExchangeCompletedTimestamp":1500797883793,"lastExchangeCompletedExchangeId":"ID-davsclaus-pro-local-1500797880917-0-205","lastExchangeCompletedTimestamp":1500798394054,"lastProcessingTime":0,"maxProcessingTime":4,"meanProcessingTime":0,"minProcessingTime":0,"redeliveries":0,"totalProcessingTime":30,"hasRouteController":false}}davsclaus:/Users/davsclaus/$
>  curl -XGET -s http://localhost:8080/camel/routes/bar/info^C
> davsclaus:/Users/davsclaus/$ ^C
> davsclaus:/Users/davsclaus/$ ^C
> davsclaus:/Users/davsclaus/$ curl -XGET -s 
> http://localhost:8080/camel/routes/bar^C
> davsclaus:/Users/davsclaus/$ curl -XPOST -s 
> http://localhost:8080/camel/routes/bar/start
> davsclaus:/Users/davsclaus/$ curl -XGET -s 
> http://localhost:8080/camel/routes/bar/info
> {"id":"bar","uptime":"1.701 
> seconds","uptimeMillis":1701,"status":"Started","details":{"deltaProcessingTime":0,"exchangesInflight":0,"exchangesTotal":104,"externalRedeliveries":0,"failuresHandled":0,"firstExchangeCompletedExchangeId":"ID-davsclaus-pro-local-1500797880917-0-1","firstExchangeCompletedTimestamp":1500797883793,"lastExchangeCompletedExchangeId":"ID-davsclaus-pro-local-1500797880917-0-218","lastExchangeCompletedTimestamp":1500798449710,"lastProcessingTime":0,"maxProcessingTime":4,"meanProcessingTime":0,"minProcessingTime":0,"redeliveries":0,"totalProcessingTime":30,"hasRouteController":true}}davsclaus:/Users/davsclaus/$
>  curl -XGET -s http://localhost:8080/camel/routes/bar/info
> {code}
> So we need a reset command
> curl -XPOST -s http://localhost:8080/camel/routes/bar/reset
> That just calls the JMX reset operation on the route mbean. It should also 
> reset the processors, eg call this with true
> @ManagedOperation(description = "Reset counters")
> void reset(boolean includeProcessors) throws Exception;



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Work started] (CAMEL-11582) SupervisingRouteController should have better INFO logging on startup

[Luca Burgazzoli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on CAMEL-11582 started by Luca Burgazzoli.
---
> SupervisingRouteController should have better INFO logging on startup
> -
>
> Key: CAMEL-11582
> URL: https://issues.apache.org/jira/browse/CAMEL-11582
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Luca Burgazzoli
>  Labels: route-controller
> Fix For: 2.20.0
>
>
> Try this example: 
> https://github.com/apache/camel/tree/master/examples/camel-example-spring-boot-routecontroller
> And configure it at INFO logging. We need to better tell the end user that 
> Camel is using the supervising route controller and therefore routes are 
> deferred being started.
> And when all the routes has been successfully started then we should log 
> something at INFO that all routes are now started.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (CAMEL-11636) property placeholder is not replaced in REST DSL in blueprint context

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen reassigned CAMEL-11636:
---

Assignee: Claus Ibsen

> property placeholder is not replaced in REST DSL in blueprint context
> -
>
> Key: CAMEL-11636
> URL: https://issues.apache.org/jira/browse/CAMEL-11636
> Project: Camel
>  Issue Type: Bug
>  Components: camel-blueprint, rest
>Affects Versions: 2.19.1
> Environment: Apache Karaf 4.0.9 running on OSX 10.12.5
>Reporter: Claudia S
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.20.0, 2.19.3
>
>
> I'm trying to update from Camel 2.16.3 to 2.19.1 and experience issues using 
> properties in the REST DSL in blueprint context.
> I have the following config:
> {code}
>  path="patient/{patient_id}/events?cutoff_timestamp={cutoff_timestamp}limit={limit}"
>  produces="application/json" consumes="application/json">
> 
>  required="true" />
>  required="false" />
>  required="false" defaultValue="{{vel.rest.default.rowlimit}}" />
> {code}   
> For the param "limit" the property vel.rest.default.rowlimit used in 
> attribute defaultValue seems not to get replaced as I receive the following 
> exception:
> {code}
> java.lang.NumberFormatException: For input string: 
> "{{vel.rest.default.rowlimit}}"
> {code}
> 
> Originally asked on the mailing list: 
> http://camel.465427.n5.nabble.com/issue-with-property-in-REST-DSL-in-blueprint-context-Camel-2-19-1-td5809573.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Work started] (CAMEL-11578) Add javadoc to util.backoff

[Luca Burgazzoli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on CAMEL-11578 started by Luca Burgazzoli.
---
> Add javadoc to util.backoff
> ---
>
> Key: CAMEL-11578
> URL: https://issues.apache.org/jira/browse/CAMEL-11578
> Project: Camel
>  Issue Type: Task
>  Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Luca Burgazzoli
>Priority: Minor
>  Labels: route-controller
> Fix For: 2.20.0
>
>
> We should have javadoc for all our classes in camel-core



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11636) property placeholder is not replaced in REST DSL in blueprint context

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-11636:

Fix Version/s: 2.19.3
   2.20.0

> property placeholder is not replaced in REST DSL in blueprint context
> -
>
> Key: CAMEL-11636
> URL: https://issues.apache.org/jira/browse/CAMEL-11636
> Project: Camel
>  Issue Type: Bug
>  Components: camel-blueprint, rest
>Affects Versions: 2.19.1
> Environment: Apache Karaf 4.0.9 running on OSX 10.12.5
>Reporter: Claudia S
>Priority: Minor
> Fix For: 2.20.0, 2.19.3
>
>
> I'm trying to update from Camel 2.16.3 to 2.19.1 and experience issues using 
> properties in the REST DSL in blueprint context.
> I have the following config:
> {code}
>  path="patient/{patient_id}/events?cutoff_timestamp={cutoff_timestamp}limit={limit}"
>  produces="application/json" consumes="application/json">
> 
>  required="true" />
>  required="false" />
>  required="false" defaultValue="{{vel.rest.default.rowlimit}}" />
> {code}   
> For the param "limit" the property vel.rest.default.rowlimit used in 
> attribute defaultValue seems not to get replaced as I receive the following 
> exception:
> {code}
> java.lang.NumberFormatException: For input string: 
> "{{vel.rest.default.rowlimit}}"
> {code}
> 
> Originally asked on the mailing list: 
> http://camel.465427.n5.nabble.com/issue-with-property-in-REST-DSL-in-blueprint-context-Camel-2-19-1-td5809573.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (CAMEL-11636) property placeholder is not replaced in REST DSL in blueprint context

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen reassigned CAMEL-11636:
---

Assignee: (was: Grzegorz Grzybek)

> property placeholder is not replaced in REST DSL in blueprint context
> -
>
> Key: CAMEL-11636
> URL: https://issues.apache.org/jira/browse/CAMEL-11636
> Project: Camel
>  Issue Type: Bug
>  Components: camel-blueprint, rest
>Affects Versions: 2.19.1
> Environment: Apache Karaf 4.0.9 running on OSX 10.12.5
>Reporter: Claudia S
>Priority: Minor
> Fix For: 2.20.0, 2.19.3
>
>
> I'm trying to update from Camel 2.16.3 to 2.19.1 and experience issues using 
> properties in the REST DSL in blueprint context.
> I have the following config:
> {code}
>  path="patient/{patient_id}/events?cutoff_timestamp={cutoff_timestamp}limit={limit}"
>  produces="application/json" consumes="application/json">
> 
>  required="true" />
>  required="false" />
>  required="false" defaultValue="{{vel.rest.default.rowlimit}}" />
> {code}   
> For the param "limit" the property vel.rest.default.rowlimit used in 
> attribute defaultValue seems not to get replaced as I receive the following 
> exception:
> {code}
> java.lang.NumberFormatException: For input string: 
> "{{vel.rest.default.rowlimit}}"
> {code}
> 
> Originally asked on the mailing list: 
> http://camel.465427.n5.nabble.com/issue-with-property-in-REST-DSL-in-blueprint-context-Camel-2-19-1-td5809573.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11635) wrong groupId in camel examples readme.md and features.xml

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-11635:

Issue Type: Task  (was: Bug)

> wrong groupId in camel examples readme.md and features.xml
> --
>
> Key: CAMEL-11635
> URL: https://issues.apache.org/jira/browse/CAMEL-11635
> Project: Camel
>  Issue Type: Task
>  Components: examples
>Reporter: Andrea Tarocchi
> Fix For: 2.20.0
>
>
> There are a number of wrong groupId (probably because examples have been 
> moved form {{org.apache.camel}} to {{org.apache.camel.example}} ? ) in 
> {{examples/}} both in {{features.xml}} and in {{readme.md}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11635) wrong groupId in camel examples readme.md and features.xml

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-11635:

Component/s: examples

> wrong groupId in camel examples readme.md and features.xml
> --
>
> Key: CAMEL-11635
> URL: https://issues.apache.org/jira/browse/CAMEL-11635
> Project: Camel
>  Issue Type: Bug
>  Components: examples
>Reporter: Andrea Tarocchi
> Fix For: 2.20.0
>
>
> There are a number of wrong groupId (probably because examples have been 
> moved form {{org.apache.camel}} to {{org.apache.camel.example}} ? ) in 
> {{examples/}} both in {{features.xml}} and in {{readme.md}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11635) wrong groupId in camel examples readme.md and features.xml

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-11635:

Fix Version/s: 2.20.0

> wrong groupId in camel examples readme.md and features.xml
> --
>
> Key: CAMEL-11635
> URL: https://issues.apache.org/jira/browse/CAMEL-11635
> Project: Camel
>  Issue Type: Bug
>  Components: examples
>Reporter: Andrea Tarocchi
> Fix For: 2.20.0
>
>
> There are a number of wrong groupId (probably because examples have been 
> moved form {{org.apache.camel}} to {{org.apache.camel.example}} ? ) in 
> {{examples/}} both in {{features.xml}} and in {{readme.md}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11632) QuartzScheduledPollConsumerScheduler causes trigger misfires on each application start

[Claus Ibsen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16116115#comment-16116115
 ] 

Claus Ibsen commented on CAMEL-11632:
-

You are welcome to work on a contribution

> QuartzScheduledPollConsumerScheduler causes trigger misfires on each 
> application start
> --
>
> Key: CAMEL-11632
> URL: https://issues.apache.org/jira/browse/CAMEL-11632
> Project: Camel
>  Issue Type: Bug
>  Components: camel-quartz2
>Affects Versions: 2.19.0
> Environment: *strong text*
>Reporter: Viktor Khoroshko
>
> Recently I noticed that on application start Quartz founds and triggers 
> misfired triggers:
> {code:java}
> INFO o.s.s.q.LocalDataSourceJobStore - Handling 1 trigger(s) that missed 
> their scheduled fire-time.
> {code}
> That wasn't not the realistic case in my scenario - since I could see in a 
> database that NEXT_FIRE_TIME is much ahead of the current time.
> After digging a little I found the issue in the 
> *QuartzScheduledPollConsumerScheduler*:
> {code:java}
>  // Ensure the cron schedule is updated
> CronTrigger newTrigger = 
> existingTrigger.getTriggerBuilder().withSchedule(CronScheduleBuilder.cronSchedule(getCron()).inTimeZone(getTimeZone())).build();
> quartzScheduler.rescheduleJob(triggerKey, newTrigger);
> {code}
> There 2 issues here:
> 1. Job is rescheduled even if nothing has been changed (i.e. cron expression, 
> cron timezone)
> 2.  *existingTrigger.getTriggerBuilder()* returns trigger builder with 
> START_TIME of existing trigger which, surely, is the past. This is causing 
> the described bug - NEXT_FIRE_TIME is calculated based on the old START_TIME 
> and is in the past also. So rescheduled trigger becomes misfired trigger 
> immediately.
> Proposal:
> 1. Do not reschedule job if nothing has been changed.
> 2. If job needs to be rescheduled - make sure to set START_TIME to a current 
> date.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11630) JPAMessageIdRepository Not Releasing Connections

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-11630:

Fix Version/s: 2.20.0

> JPAMessageIdRepository Not Releasing Connections
> 
>
> Key: CAMEL-11630
> URL: https://issues.apache.org/jira/browse/CAMEL-11630
> Project: Camel
>  Issue Type: Bug
>  Components: camel-jpa
>Affects Versions: 2.19.1
>Reporter: Mary Cochran
> Fix For: 2.20.0
>
>
> When using the JpaMessageIdRepository for an idempotent repo for file 
> processing it holds onto connections and does not release them unless you 
> manually flush the connection pool.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11624) REST DSL/component method Uppercase

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-11624:

Fix Version/s: 2.19.3
   2.20.0

> REST DSL/component method Uppercase
> ---
>
> Key: CAMEL-11624
> URL: https://issues.apache.org/jira/browse/CAMEL-11624
> Project: Camel
>  Issue Type: Bug
>  Components: rest
>Affects Versions: 2.19.1
>Reporter: Paolo Lizarazu
> Fix For: 2.20.0, 2.19.3
>
>
> when we are using rest component we need to set the method in uppercase 
> otherwise this will return error 405
> bad example : String requestResponse = 
> testProducer.requestBody("rest:get:health?host=$activityHost:$activityPort", 
> null, String.class)
> working example
> String requestResponse = 
> testProducer.requestBody("rest:GET:health?host=$activityHost:$activityPort", 
> null, String.class)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (CAMEL-11624) REST DSL/component method Uppercase

[Claus Ibsen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16116107#comment-16116107
 ] 

Claus Ibsen edited comment on CAMEL-11624 at 8/7/17 6:12 AM:
-

What rest component are you using? As it may depend on which component that 
does the actual rest call about the upper case thing. 

But yeah we should make it work with regardless how you type it


was (Author: davsclaus):
What rest component are you using?

> REST DSL/component method Uppercase
> ---
>
> Key: CAMEL-11624
> URL: https://issues.apache.org/jira/browse/CAMEL-11624
> Project: Camel
>  Issue Type: Bug
>  Components: rest
>Affects Versions: 2.19.1
>Reporter: Paolo Lizarazu
> Fix For: 2.20.0, 2.19.3
>
>
> when we are using rest component we need to set the method in uppercase 
> otherwise this will return error 405
> bad example : String requestResponse = 
> testProducer.requestBody("rest:get:health?host=$activityHost:$activityPort", 
> null, String.class)
> working example
> String requestResponse = 
> testProducer.requestBody("rest:GET:health?host=$activityHost:$activityPort", 
> null, String.class)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (CAMEL-11585) camel-spring-boot - Allow to reset route statistics via actuator

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-11585.
-
Resolution: Fixed

> camel-spring-boot - Allow to reset route statistics via actuator
> 
>
> Key: CAMEL-11585
> URL: https://issues.apache.org/jira/browse/CAMEL-11585
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-spring-boot
>Reporter: Claus Ibsen
>Assignee: Viral Gohel
>Priority: Minor
> Fix For: 2.20.0
>
>
> You can start/stop/suspend/resume routes etc. But it would also be nice to be 
> able to reset the JMX statistics.
> for example if you stop and start a route, then it continues with the 
> existing JMX stats (but sometimes you want to be able to reset).
> {code}
> 8080/camel/routes/bar/info
> {"id":"bar","uptimeMillis":0,"status":"Stopped","details":{"deltaProcessingTime":0,"exchangesInflight":0,"exchangesTotal":103,"externalRedeliveries":0,"failuresHandled":0,"firstExchangeCompletedExchangeId":"ID-davsclaus-pro-local-1500797880917-0-1","firstExchangeCompletedTimestamp":1500797883793,"lastExchangeCompletedExchangeId":"ID-davsclaus-pro-local-1500797880917-0-205","lastExchangeCompletedTimestamp":1500798394054,"lastProcessingTime":0,"maxProcessingTime":4,"meanProcessingTime":0,"minProcessingTime":0,"redeliveries":0,"totalProcessingTime":30,"hasRouteController":false}}davsclaus:/Users/davsclaus/$
>  curl -XGET -s http://localhost:8080/camel/routes/bar/info^C
> davsclaus:/Users/davsclaus/$ ^C
> davsclaus:/Users/davsclaus/$ ^C
> davsclaus:/Users/davsclaus/$ curl -XGET -s 
> http://localhost:8080/camel/routes/bar^C
> davsclaus:/Users/davsclaus/$ curl -XPOST -s 
> http://localhost:8080/camel/routes/bar/start
> davsclaus:/Users/davsclaus/$ curl -XGET -s 
> http://localhost:8080/camel/routes/bar/info
> {"id":"bar","uptime":"1.701 
> seconds","uptimeMillis":1701,"status":"Started","details":{"deltaProcessingTime":0,"exchangesInflight":0,"exchangesTotal":104,"externalRedeliveries":0,"failuresHandled":0,"firstExchangeCompletedExchangeId":"ID-davsclaus-pro-local-1500797880917-0-1","firstExchangeCompletedTimestamp":1500797883793,"lastExchangeCompletedExchangeId":"ID-davsclaus-pro-local-1500797880917-0-218","lastExchangeCompletedTimestamp":1500798449710,"lastProcessingTime":0,"maxProcessingTime":4,"meanProcessingTime":0,"minProcessingTime":0,"redeliveries":0,"totalProcessingTime":30,"hasRouteController":true}}davsclaus:/Users/davsclaus/$
>  curl -XGET -s http://localhost:8080/camel/routes/bar/info
> {code}
> So we need a reset command
> curl -XPOST -s http://localhost:8080/camel/routes/bar/reset
> That just calls the JMX reset operation on the route mbean. It should also 
> reset the processors, eg call this with true
> @ManagedOperation(description = "Reset counters")
> void reset(boolean includeProcessors) throws Exception;



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11624) REST DSL/component method Uppercase

[Claus Ibsen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16116107#comment-16116107
 ] 

Claus Ibsen commented on CAMEL-11624:
-

What rest component are you using?

> REST DSL/component method Uppercase
> ---
>
> Key: CAMEL-11624
> URL: https://issues.apache.org/jira/browse/CAMEL-11624
> Project: Camel
>  Issue Type: Bug
>  Components: rest
>Affects Versions: 2.19.1
>Reporter: Paolo Lizarazu
>
> when we are using rest component we need to set the method in uppercase 
> otherwise this will return error 405
> bad example : String requestResponse = 
> testProducer.requestBody("rest:get:health?host=$activityHost:$activityPort", 
> null, String.class)
> working example
> String requestResponse = 
> testProducer.requestBody("rest:GET:health?host=$activityHost:$activityPort", 
> null, String.class)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (CAMEL-11585) camel-spring-boot - Allow to reset route statistics via actuator

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-11585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen reassigned CAMEL-11585:
---

Assignee: Viral Gohel

> camel-spring-boot - Allow to reset route statistics via actuator
> 
>
> Key: CAMEL-11585
> URL: https://issues.apache.org/jira/browse/CAMEL-11585
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-spring-boot
>Reporter: Claus Ibsen
>Assignee: Viral Gohel
>Priority: Minor
> Fix For: 2.20.0
>
>
> You can start/stop/suspend/resume routes etc. But it would also be nice to be 
> able to reset the JMX statistics.
> for example if you stop and start a route, then it continues with the 
> existing JMX stats (but sometimes you want to be able to reset).
> {code}
> 8080/camel/routes/bar/info
> {"id":"bar","uptimeMillis":0,"status":"Stopped","details":{"deltaProcessingTime":0,"exchangesInflight":0,"exchangesTotal":103,"externalRedeliveries":0,"failuresHandled":0,"firstExchangeCompletedExchangeId":"ID-davsclaus-pro-local-1500797880917-0-1","firstExchangeCompletedTimestamp":1500797883793,"lastExchangeCompletedExchangeId":"ID-davsclaus-pro-local-1500797880917-0-205","lastExchangeCompletedTimestamp":1500798394054,"lastProcessingTime":0,"maxProcessingTime":4,"meanProcessingTime":0,"minProcessingTime":0,"redeliveries":0,"totalProcessingTime":30,"hasRouteController":false}}davsclaus:/Users/davsclaus/$
>  curl -XGET -s http://localhost:8080/camel/routes/bar/info^C
> davsclaus:/Users/davsclaus/$ ^C
> davsclaus:/Users/davsclaus/$ ^C
> davsclaus:/Users/davsclaus/$ curl -XGET -s 
> http://localhost:8080/camel/routes/bar^C
> davsclaus:/Users/davsclaus/$ curl -XPOST -s 
> http://localhost:8080/camel/routes/bar/start
> davsclaus:/Users/davsclaus/$ curl -XGET -s 
> http://localhost:8080/camel/routes/bar/info
> {"id":"bar","uptime":"1.701 
> seconds","uptimeMillis":1701,"status":"Started","details":{"deltaProcessingTime":0,"exchangesInflight":0,"exchangesTotal":104,"externalRedeliveries":0,"failuresHandled":0,"firstExchangeCompletedExchangeId":"ID-davsclaus-pro-local-1500797880917-0-1","firstExchangeCompletedTimestamp":1500797883793,"lastExchangeCompletedExchangeId":"ID-davsclaus-pro-local-1500797880917-0-218","lastExchangeCompletedTimestamp":1500798449710,"lastProcessingTime":0,"maxProcessingTime":4,"meanProcessingTime":0,"minProcessingTime":0,"redeliveries":0,"totalProcessingTime":30,"hasRouteController":true}}davsclaus:/Users/davsclaus/$
>  curl -XGET -s http://localhost:8080/camel/routes/bar/info
> {code}
> So we need a reset command
> curl -XPOST -s http://localhost:8080/camel/routes/bar/reset
> That just calls the JMX reset operation on the route mbean. It should also 
> reset the processors, eg call this with true
> @ManagedOperation(description = "Reset counters")
> void reset(boolean includeProcessors) throws Exception;



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)