[jira] [Commented] (CAMEL-11845) Migrate easymock and powermock to mockito

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-11845:


GitHub user PascalSchumacher opened a pull request:

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

CAMEL-11845: Migrate easymock and powermock to mockito

Migrate camel-mina and camel-mina2 from easymock to mockito.

Test still pass.

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

$ git pull https://github.com/PascalSchumacher/camel 
camel_11845_mockito_migration

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

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


commit c3bf1c4c61c078f62bab51bd80d147105c20b05d
Author: Pascal Schumacher 
Date:   2017-09-27T21:46:13Z

CAMEL-11845: Migrate easymock and powermock to mockito

Migrate camel-mina and camel-mina2 from easymock to mockito.




> Migrate easymock and powermock to mockito
> -
>
> Key: CAMEL-11845
> URL: https://issues.apache.org/jira/browse/CAMEL-11845
> Project: Camel
>  Issue Type: Test
>Reporter: Claus Ibsen
> Fix For: Future
>
>
> We want to only use one kind of mock testing library. They are a pain to 
> maintain and too much fuzz/magic going on. 
> The majority is using mockito, and its more popular.
> Contributions is welcome to migrate the components that uses easymock or 
> powermock



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

[jira] [Commented] (CAMEL-11845) Migrate easymock and powermock to mockito

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-11845:


GitHub user aldettinger opened a pull request:

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

CAMEL-11845: Migrated camel-bonita from powermock to mockito

Migrated camel-bonita from powermock to mockito.
Removed an unused property from camel-azure as well.

More details in 
[CAMEL-11845](https://issues.apache.org/jira/browse/CAMEL-11845).

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

$ git pull https://github.com/aldettinger/camel master

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

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


commit 1e9f3ed611a758ffd49be254f7bf38d15ec7c738
Author: aldettinger 
Date:   2017-09-27T21:43:45Z

CAMEL-11845: Migrated camel-bonita from powermock to mockito




> Migrate easymock and powermock to mockito
> -
>
> Key: CAMEL-11845
> URL: https://issues.apache.org/jira/browse/CAMEL-11845
> Project: Camel
>  Issue Type: Test
>Reporter: Claus Ibsen
> Fix For: Future
>
>
> We want to only use one kind of mock testing library. They are a pain to 
> maintain and too much fuzz/magic going on. 
> The majority is using mockito, and its more popular.
> Contributions is welcome to migrate the components that uses easymock or 
> powermock



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

[jira] [Commented] (CAMEL-11805) Upgrade to Apache Ignite 2.x

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-11805:
-

Contributions is welcome

> Upgrade to Apache Ignite 2.x
> 
>
> Key: CAMEL-11805
> URL: https://issues.apache.org/jira/browse/CAMEL-11805
> Project: Camel
>  Issue Type: Task
>  Components: camel-ignite
>Reporter: Luca Burgazzoli
> Fix For: 2.21.0
>
>
> Last version is 2.2.0, we are on 1.9.0



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

[jira] [Updated] (CAMEL-11805) Upgrade to Apache Ignite 2.x

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-11805:

Estimated Complexity: Novice  (was: Unknown)

> Upgrade to Apache Ignite 2.x
> 
>
> Key: CAMEL-11805
> URL: https://issues.apache.org/jira/browse/CAMEL-11805
> Project: Camel
>  Issue Type: Task
>  Components: camel-ignite
>Reporter: Luca Burgazzoli
> Fix For: 2.21.0
>
>
> Last version is 2.2.0, we are on 1.9.0



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

[jira] [Assigned] (CAMEL-11850) camel-hdfs2 - test fails on jdk9

[Claus Ibsen (JIRA)]

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

Claus Ibsen reassigned CAMEL-11850:
---

Assignee: John Poth

> camel-hdfs2 - test fails on jdk9
> 
>
> Key: CAMEL-11850
> URL: https://issues.apache.org/jira/browse/CAMEL-11850
> Project: Camel
>  Issue Type: Test
>  Components: camel-hdfs2
>Reporter: Claus Ibsen
>Assignee: John Poth
> Fix For: 2.20.0
>
>
> Failed
> org.apache.camel.component.hdfs2.FromFileToHdfsTest.testTwoFilesToHdfs
> Failing for the past 23 builds (Since #802 )
> Took 1.8 sec.
> Error Message
> Could not initialize class org.apache.hadoop.util.StringUtils
> Stacktrace
> java.lang.NoClassDefFoundError: Could not initialize class 
> org.apache.hadoop.util.StringUtils
>   at 
> org.apache.camel.component.hdfs2.FromFileToHdfsTest.setUp(FromFileToHdfsTest.java:44)



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

[jira] [Updated] (CAMEL-11819) camel-velocity - Upgrade to 2.x

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-11819:

Fix Version/s: (was: 2.21.0)
   2.20.0

> camel-velocity - Upgrade to 2.x
> ---
>
> Key: CAMEL-11819
> URL: https://issues.apache.org/jira/browse/CAMEL-11819
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-velocity
>Reporter: Claus Ibsen
> Fix For: 2.20.0
>
>
> There is a 2.0 release - the old 1.7 release is very old.
> Contributions is welcome
> http://camel.apache.org/contributing



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

[jira] [Resolved] (CAMEL-11850) camel-hdfs2 - test fails on jdk9

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-11850.
-
   Resolution: Fixed
Fix Version/s: (was: 2.21.0)
   2.20.0

Thanks John

> camel-hdfs2 - test fails on jdk9
> 
>
> Key: CAMEL-11850
> URL: https://issues.apache.org/jira/browse/CAMEL-11850
> Project: Camel
>  Issue Type: Test
>  Components: camel-hdfs2
>Reporter: Claus Ibsen
>Assignee: John Poth
> Fix For: 2.20.0
>
>
> Failed
> org.apache.camel.component.hdfs2.FromFileToHdfsTest.testTwoFilesToHdfs
> Failing for the past 23 builds (Since #802 )
> Took 1.8 sec.
> Error Message
> Could not initialize class org.apache.hadoop.util.StringUtils
> Stacktrace
> java.lang.NoClassDefFoundError: Could not initialize class 
> org.apache.hadoop.util.StringUtils
>   at 
> org.apache.camel.component.hdfs2.FromFileToHdfsTest.setUp(FromFileToHdfsTest.java:44)



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

[jira] [Resolved] (CAMEL-11859) Deprecate camel-spark-rest as it does not play well in OSGi

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-11859.
-
   Resolution: Fixed
 Assignee: Claus Ibsen
Fix Version/s: (was: 2.21.0)
   2.20.0

> Deprecate camel-spark-rest as it does not play well in OSGi
> ---
>
> Key: CAMEL-11859
> URL: https://issues.apache.org/jira/browse/CAMEL-11859
> Project: Camel
>  Issue Type: Sub-task
>  Components: karaf
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.20.0
>
>
> It has some static code that does not play very well in OSGi



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

[jira] [Commented] (CAMEL-11859) Deprecate camel-spark-rest as it does not play well in OSGi

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-11859:
-

It would be great if karaf had a deprecate=true|false on the feature so it 
could stand out a bit more.

> Deprecate camel-spark-rest as it does not play well in OSGi
> ---
>
> Key: CAMEL-11859
> URL: https://issues.apache.org/jira/browse/CAMEL-11859
> Project: Camel
>  Issue Type: Sub-task
>  Components: karaf
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.20.0
>
>
> It has some static code that does not play very well in OSGi



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

[jira] [Commented] (CAMEL-11859) Deprecate camel-spark-rest as it does not play well in OSGi

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-11859:
-

I added a note to its karaf feature its deprecated. This is how we represent 
this currently.

> Deprecate camel-spark-rest as it does not play well in OSGi
> ---
>
> Key: CAMEL-11859
> URL: https://issues.apache.org/jira/browse/CAMEL-11859
> Project: Camel
>  Issue Type: Sub-task
>  Components: karaf
>Reporter: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.20.0
>
>
> It has some static code that does not play very well in OSGi



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

[jira] [Commented] (CAMEL-11850) camel-hdfs2 - test fails on jdk9

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-11850:


Github user johnpoth closed the pull request at:

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


> camel-hdfs2 - test fails on jdk9
> 
>
> Key: CAMEL-11850
> URL: https://issues.apache.org/jira/browse/CAMEL-11850
> Project: Camel
>  Issue Type: Test
>  Components: camel-hdfs2
>Reporter: Claus Ibsen
> Fix For: 2.21.0
>
>
> Failed
> org.apache.camel.component.hdfs2.FromFileToHdfsTest.testTwoFilesToHdfs
> Failing for the past 23 builds (Since #802 )
> Took 1.8 sec.
> Error Message
> Could not initialize class org.apache.hadoop.util.StringUtils
> Stacktrace
> java.lang.NoClassDefFoundError: Could not initialize class 
> org.apache.hadoop.util.StringUtils
>   at 
> org.apache.camel.component.hdfs2.FromFileToHdfsTest.setUp(FromFileToHdfsTest.java:44)



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

[jira] [Commented] (CAMEL-11853) camel-reactor : create karaf feature

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli commented on CAMEL-11853:
-

This may require a little bit of work also on camel-reactive-streams side, 
postponed to 2.21

> camel-reactor : create karaf feature
> 
>
> Key: CAMEL-11853
> URL: https://issues.apache.org/jira/browse/CAMEL-11853
> Project: Camel
>  Issue Type: Task
>  Components: camel-reactor, karaf
>Reporter: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.21.0
>
>




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

[jira] [Updated] (CAMEL-11853) camel-reactor : create karaf feature

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli updated CAMEL-11853:

Fix Version/s: (was: 2.20.0)
   2.21.0

> camel-reactor : create karaf feature
> 
>
> Key: CAMEL-11853
> URL: https://issues.apache.org/jira/browse/CAMEL-11853
> Project: Camel
>  Issue Type: Task
>  Components: camel-reactor, karaf
>Reporter: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.21.0
>
>




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

[jira] [Commented] (CAMEL-11850) camel-hdfs2 - test fails on jdk9

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-11850:


GitHub user johnpoth opened a pull request:

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

Camel 11850

Fix for [CAMEL-11850](https://issues.apache.org/jira/browse/CAMEL-11850)

Also includes other fixes to build the entire project (without tests) using 
JDK9 GA. I'll work on fixing remaining test failures in a separate PR.

Thanks!

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

$ git pull https://github.com/johnpoth/camel CAMEL-11850

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

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


commit 148664081f4948c947da8ba964d44871092077b8
Author: jpoth 
Date:   2017-09-27T11:25:42Z

CAMEL-11850 fix camel-asn1 on JDK9

commit 451341868f785964cd664f069b88f096e0b7e2c8
Author: jpoth 
Date:   2017-09-27T13:46:25Z

CAMEL-11850 upgrade maven-javadoc-plugin to 3.0.0-M1 containing fix for 
MJAVADOC-485 to pass Java 9 builds

commit d7995da5bff965a6f81d85b3a8be6e80d834baab
Author: jpoth 
Date:   2017-09-27T14:15:06Z

CAMEL-11850 fix camel-kubernetes on Java 9

commit baa659f396da791ae7f3c8d128ce8aa411f4039e
Author: jpoth 
Date:   2017-09-27T15:45:49Z

CAMEL-11850 upgrade hadoop to 2.7.4 to include fix for HADOOP-14586 to 
build on Java 9

commit 8d0e897953d4450d73415a20ca6d3db4600e33af
Author: jpoth 
Date:   2017-09-27T15:46:34Z

CAMEL-11850 build camel-olingo2-api on Java 9




> camel-hdfs2 - test fails on jdk9
> 
>
> Key: CAMEL-11850
> URL: https://issues.apache.org/jira/browse/CAMEL-11850
> Project: Camel
>  Issue Type: Test
>  Components: camel-hdfs2
>Reporter: Claus Ibsen
> Fix For: 2.21.0
>
>
> Failed
> org.apache.camel.component.hdfs2.FromFileToHdfsTest.testTwoFilesToHdfs
> Failing for the past 23 builds (Since #802 )
> Took 1.8 sec.
> Error Message
> Could not initialize class org.apache.hadoop.util.StringUtils
> Stacktrace
> java.lang.NoClassDefFoundError: Could not initialize class 
> org.apache.hadoop.util.StringUtils
>   at 
> org.apache.camel.component.hdfs2.FromFileToHdfsTest.setUp(FromFileToHdfsTest.java:44)



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

[jira] [Resolved] (CAMEL-11829) [example] spring-boot-health-checks - 'application' keep emitting ERRORs

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli resolved CAMEL-11829.
-
Resolution: Fixed

> [example] spring-boot-health-checks - 'application' keep emitting ERRORs
> 
>
> Key: CAMEL-11829
> URL: https://issues.apache.org/jira/browse/CAMEL-11829
> Project: Camel
>  Issue Type: Sub-task
>  Components: examples
>Reporter: Tomohisa Igarashi
>Assignee: Luca Burgazzoli
>Priority: Minor
>  Labels: health-check
> Fix For: 2.20.0
>
>
> {code}
> 2017-09-24 08:46:03.929 ERROR 25801 --- [2 - timer://bar] 
> o.a.camel.processor.DefaultErrorHandler  : Failed delivery for (MessageId: 
> ID-tomo-p50-1506257079785-0-395 on ExchangeId: 
> ID-tomo-p50-1506257079785-0-393). Exhausted after delivery attempt: 1 caught: 
> org.apache.camel.RuntimeCamelException: fail (bar)
> Message History
> ---
> RouteId  ProcessorId  Processor   
>  Elapsed (ms)
> [bar   ] [bar   ] [timer://bar?period=1s  
>] [ 2]
> [bar   ] [process2  ] [Processor@0x2cd311fc   
>] [ 0]
> Stacktrace
> ---
> org.apache.camel.RuntimeCamelException: fail (bar)
>   at 
> sample.camel.ApplicationConfiguration$1.lambda$configure$1(ApplicationConfiguration.java:38)
>  ~[classes/:na]
>   at 
> org.apache.camel.processor.DelegateSyncProcessor.process(DelegateSyncProcessor.java:63)
>  ~[camel-core-2.20.0-SNAPSHOT.jar:2.20.0-SNAPSHOT]
>   at 
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
>  ~[camel-core-2.20.0-SNAPSHOT.jar:2.20.0-SNAPSHOT]
>   at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
>  [camel-core-2.20.0-SNAPSHOT.jar:2.20.0-SNAPSHOT]
>   at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
>  [camel-core-2.20.0-SNAPSHOT.jar:2.20.0-SNAPSHOT]
>   at 
> org.apache.camel.component.timer.TimerConsumer.sendTimerExchange(TimerConsumer.java:197)
>  [camel-core-2.20.0-SNAPSHOT.jar:2.20.0-SNAPSHOT]
>   at 
> org.apache.camel.component.timer.TimerConsumer$1.run(TimerConsumer.java:79) 
> [camel-core-2.20.0-SNAPSHOT.jar:2.20.0-SNAPSHOT]
>   at java.util.TimerThread.mainLoop(Timer.java:555) [na:1.8.0_144]
>   at java.util.TimerThread.run(Timer.java:505) [na:1.8.0_144]
> {code}



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

[jira] [Created] (CAMEL-11859) Deprecate camel-spark-rest as it does not play well in OSGi

[Luca Burgazzoli (JIRA)]

Luca Burgazzoli created CAMEL-11859:
---

 Summary: Deprecate camel-spark-rest as it does not play well in 
OSGi
 Key: CAMEL-11859
 URL: https://issues.apache.org/jira/browse/CAMEL-11859
 Project: Camel
  Issue Type: Sub-task
Reporter: Luca Burgazzoli
Priority: Minor
 Fix For: 2.21.0


It has some static code that does not play very well in OSGi



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

[jira] [Created] (CAMEL-11858) Deprecate non working karaf features

[Luca Burgazzoli (JIRA)]

Luca Burgazzoli created CAMEL-11858:
---

 Summary: Deprecate non working karaf features
 Key: CAMEL-11858
 URL: https://issues.apache.org/jira/browse/CAMEL-11858
 Project: Camel
  Issue Type: Task
  Components: karaf
Reporter: Luca Burgazzoli
Priority: Minor
 Fix For: 2.21.0






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

[jira] [Resolved] (CAMEL-11852) camel-milo : create karaf feature

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli resolved CAMEL-11852.
-
Resolution: Fixed

> camel-milo : create karaf feature
> -
>
> Key: CAMEL-11852
> URL: https://issues.apache.org/jira/browse/CAMEL-11852
> Project: Camel
>  Issue Type: Task
>  Components: camel-milo, karaf
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.20.0
>
>




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

[jira] [Assigned] (CAMEL-11852) camel-milo : create karaf feature

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli reassigned CAMEL-11852:
---

Assignee: Luca Burgazzoli

> camel-milo : create karaf feature
> -
>
> Key: CAMEL-11852
> URL: https://issues.apache.org/jira/browse/CAMEL-11852
> Project: Camel
>  Issue Type: Task
>  Components: camel-milo, karaf
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.20.0
>
>




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

[jira] [Resolved] (CAMEL-11847) cluster-service : support multiple cluster services

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli resolved CAMEL-11847.
-
Resolution: Fixed

> cluster-service : support multiple cluster services
> ---
>
> Key: CAMEL-11847
> URL: https://issues.apache.org/jira/browse/CAMEL-11847
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Affects Versions: 2.20.0
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>  Labels: clustering
> Fix For: 2.20.0
>
>




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

[jira] [Resolved] (CAMEL-10320) Provide a LeaderPolicy to ease the implementation of master/slave route/context

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli resolved CAMEL-10320.
-
Resolution: Fixed

> Provide a LeaderPolicy to ease the implementation of master/slave 
> route/context
> ---
>
> Key: CAMEL-10320
> URL: https://issues.apache.org/jira/browse/CAMEL-10320
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-core
>Reporter: Luca Burgazzoli
>Assignee: Dhiraj Bokde
>  Labels: clustering
> Fix For: 2.20.0
>
>
> I've been working on some master/slave RoutePolicy and I'm wondering
> if we can have a proper LeaderPolicy with a standardized
> implementation in Camel 3.0 so one has only to notify when a
> leadership is taken
> In addition it may be nice to have:
> - a support for Leader election from the CmelContext so the routes are
> started when the context become leader.
> - an option to warm-up routes or to keep them stopped while not leader
> Then we can also make it exposed in JMX so tooling are able to detect
> which are current master and slaves, and whatnot.
> Some possible DSL/EIP extensions:
> {code:java}
> from("...")
> .routeId("myRoute")
> .master() 
> .group("my-group")
> .consulConfiguration("http://consul-node:8500;)
> .end()
> . to(...)
> {code}
> {code:java}
> camelContext.setDefaultClusteredRouteConfiguration(
> ClusteredRouteConfiguration.builder()
> .withAction(ClusteredRouteAction.SUSPEND)
> .withHealtCheck(...)
> .consulConfiguration("http://consul-node:8500;)
> .build()
> );
>   
> // lookup the cluster configuration from the registry   
> from("clustered:file:/data")
> .routeId("data-files")
> .to(...)
> // lookup the cluster configuration from the registry  
> from("master:file:/share")
> .routeId("shared-files")
> .master()
> .configuration("...")
> .end()
> .to(...)
> {code}
> {code:xml}
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
>
> 
> 
> 
> 
> 
> {code}



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

[jira] [Updated] (CAMEL-11857) camel-zendesk : create karaf feature

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli updated CAMEL-11857:

Component/s: (was: camel-olingo4)
 camel-zendesk

> camel-zendesk : create karaf feature
> 
>
> Key: CAMEL-11857
> URL: https://issues.apache.org/jira/browse/CAMEL-11857
> Project: Camel
>  Issue Type: Task
>  Components: camel-zendesk, karaf
>Reporter: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.20.0
>
>




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

[jira] [Created] (CAMEL-11857) camel-zendesk : create karaf feature

[Luca Burgazzoli (JIRA)]

Luca Burgazzoli created CAMEL-11857:
---

 Summary: camel-zendesk : create karaf feature
 Key: CAMEL-11857
 URL: https://issues.apache.org/jira/browse/CAMEL-11857
 Project: Camel
  Issue Type: Task
  Components: camel-olingo4, karaf
Reporter: Luca Burgazzoli
Priority: Minor
 Fix For: 2.20.0






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

[jira] [Created] (CAMEL-11856) camel-olingo4 : create karaf feature

[Luca Burgazzoli (JIRA)]

Luca Burgazzoli created CAMEL-11856:
---

 Summary: camel-olingo4 : create karaf feature
 Key: CAMEL-11856
 URL: https://issues.apache.org/jira/browse/CAMEL-11856
 Project: Camel
  Issue Type: Task
  Components: camel-opentracing, karaf
Reporter: Luca Burgazzoli
Priority: Minor
 Fix For: 2.20.0






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

[jira] [Updated] (CAMEL-11856) camel-olingo4 : create karaf feature

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli updated CAMEL-11856:

Component/s: (was: camel-opentracing)
 camel-olingo4

> camel-olingo4 : create karaf feature
> 
>
> Key: CAMEL-11856
> URL: https://issues.apache.org/jira/browse/CAMEL-11856
> Project: Camel
>  Issue Type: Task
>  Components: camel-olingo4, karaf
>Reporter: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.20.0
>
>




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

[jira] [Created] (CAMEL-11855) camel-opentracing : create karaf feature

[Luca Burgazzoli (JIRA)]

Luca Burgazzoli created CAMEL-11855:
---

 Summary: camel-opentracing : create karaf feature
 Key: CAMEL-11855
 URL: https://issues.apache.org/jira/browse/CAMEL-11855
 Project: Camel
  Issue Type: Task
  Components: camel-opentracing, karaf
Reporter: Luca Burgazzoli
Priority: Minor
 Fix For: 2.20.0






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

[jira] [Updated] (CAMEL-11854) camel-pubnub : create karaf feature

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli updated CAMEL-11854:

Component/s: (was: camel-reactor)
 camel-pubnub

> camel-pubnub : create karaf feature
> ---
>
> Key: CAMEL-11854
> URL: https://issues.apache.org/jira/browse/CAMEL-11854
> Project: Camel
>  Issue Type: Task
>  Components: camel-pubnub, karaf
>Reporter: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.20.0
>
>




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

[jira] [Created] (CAMEL-11854) camel-pubnub : create karaf feature

[Luca Burgazzoli (JIRA)]

Luca Burgazzoli created CAMEL-11854:
---

 Summary: camel-pubnub : create karaf feature
 Key: CAMEL-11854
 URL: https://issues.apache.org/jira/browse/CAMEL-11854
 Project: Camel
  Issue Type: Task
  Components: camel-reactor, karaf
Reporter: Luca Burgazzoli
Priority: Minor
 Fix For: 2.20.0






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

[jira] [Created] (CAMEL-11853) camel-reactor : create karaf feature

[Luca Burgazzoli (JIRA)]

Luca Burgazzoli created CAMEL-11853:
---

 Summary: camel-reactor : create karaf feature
 Key: CAMEL-11853
 URL: https://issues.apache.org/jira/browse/CAMEL-11853
 Project: Camel
  Issue Type: Task
  Components: camel-reactor, karaf
Reporter: Luca Burgazzoli
Priority: Minor
 Fix For: 2.20.0






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

[jira] [Resolved] (CAMEL-11848) Using MongoDB Tailable Cursor Consumer on non-capped collection results in NullPointerException (instead of proper error message)

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-11848.
-
Resolution: Fixed
  Assignee: Claus Ibsen

Thanks for the PR and testing

> Using MongoDB Tailable Cursor Consumer on non-capped collection results in 
> NullPointerException (instead of proper error message)
> -
>
> Key: CAMEL-11848
> URL: https://issues.apache.org/jira/browse/CAMEL-11848
> Project: Camel
>  Issue Type: Bug
>  Components: camel-mongodb, camel-mongodb3
>Affects Versions: 2.19.3
>Reporter: Frank Wein
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.19.4, 2.20.0
>
>
> When using the Camel MongoDB component with a tailable cursor consumer on a 
> non-capped collection, you get a NullPointerException (also see 
> http://camel.apache.org/mongodb.html#MongoDB-TailableCursorConsumer on this). 
> While using this feature on a non-capped collection is not supported, the 
> error message should be better (at the moment it only throws a 
> NullPointerException because the code tries to unbox a null in a Boolean 
> object). The code actually already has a better error message, but there is a 
> small logic flaw that prevents the error message from showing up. See 
> https://github.com/apache/camel/blob/camel-2.19.3/components/camel-mongodb/src/main/java/org/apache/camel/component/mongodb/MongoDbTailingProcess.java#L78
>  for the code.



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

[jira] [Commented] (CAMEL-11848) Using MongoDB Tailable Cursor Consumer on non-capped collection results in NullPointerException (instead of proper error message)

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-11848:


Github user asfgit closed the pull request at:

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


> Using MongoDB Tailable Cursor Consumer on non-capped collection results in 
> NullPointerException (instead of proper error message)
> -
>
> Key: CAMEL-11848
> URL: https://issues.apache.org/jira/browse/CAMEL-11848
> Project: Camel
>  Issue Type: Bug
>  Components: camel-mongodb, camel-mongodb3
>Affects Versions: 2.19.3
>Reporter: Frank Wein
>Priority: Minor
> Fix For: 2.19.4, 2.20.0
>
>
> When using the Camel MongoDB component with a tailable cursor consumer on a 
> non-capped collection, you get a NullPointerException (also see 
> http://camel.apache.org/mongodb.html#MongoDB-TailableCursorConsumer on this). 
> While using this feature on a non-capped collection is not supported, the 
> error message should be better (at the moment it only throws a 
> NullPointerException because the code tries to unbox a null in a Boolean 
> object). The code actually already has a better error message, but there is a 
> small logic flaw that prevents the error message from showing up. See 
> https://github.com/apache/camel/blob/camel-2.19.3/components/camel-mongodb/src/main/java/org/apache/camel/component/mongodb/MongoDbTailingProcess.java#L78
>  for the code.



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

[jira] [Resolved] (CAMEL-11851) camel-kura : create karaf feature

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-11851.
-
Resolution: Fixed

> camel-kura : create karaf feature
> -
>
> Key: CAMEL-11851
> URL: https://issues.apache.org/jira/browse/CAMEL-11851
> Project: Camel
>  Issue Type: Task
>  Components: camel-kura, karaf
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.20.0
>
>




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

[jira] [Commented] (CAMEL-11848) Using MongoDB Tailable Cursor Consumer on non-capped collection results in NullPointerException (instead of proper error message)

[Frank Wein (JIRA)]

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

Frank Wein commented on CAMEL-11848:


BTW: I checked with mongodb 3.2 and 3.4, there it's fine.

> Using MongoDB Tailable Cursor Consumer on non-capped collection results in 
> NullPointerException (instead of proper error message)
> -
>
> Key: CAMEL-11848
> URL: https://issues.apache.org/jira/browse/CAMEL-11848
> Project: Camel
>  Issue Type: Bug
>  Components: camel-mongodb, camel-mongodb3
>Affects Versions: 2.19.3
>Reporter: Frank Wein
>Priority: Minor
> Fix For: 2.19.4, 2.20.0
>
>
> When using the Camel MongoDB component with a tailable cursor consumer on a 
> non-capped collection, you get a NullPointerException (also see 
> http://camel.apache.org/mongodb.html#MongoDB-TailableCursorConsumer on this). 
> While using this feature on a non-capped collection is not supported, the 
> error message should be better (at the moment it only throws a 
> NullPointerException because the code tries to unbox a null in a Boolean 
> object). The code actually already has a better error message, but there is a 
> small logic flaw that prevents the error message from showing up. See 
> https://github.com/apache/camel/blob/camel-2.19.3/components/camel-mongodb/src/main/java/org/apache/camel/component/mongodb/MongoDbTailingProcess.java#L78
>  for the code.



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

[jira] [Assigned] (CAMEL-11851) camel-kura : create karaf feature

[Claus Ibsen (JIRA)]

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

Claus Ibsen reassigned CAMEL-11851:
---

Assignee: Claus Ibsen

> camel-kura : create karaf feature
> -
>
> Key: CAMEL-11851
> URL: https://issues.apache.org/jira/browse/CAMEL-11851
> Project: Camel
>  Issue Type: Task
>  Components: camel-kura, karaf
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.20.0
>
>




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

[jira] [Commented] (CAMEL-11848) Using MongoDB Tailable Cursor Consumer on non-capped collection results in NullPointerException (instead of proper error message)

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-11848:


GitHub user Frankst2 opened a pull request:

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

CAMEL-11848: Check for null value when getting key "capped" of collec…

…tion stats (key/value might not exist in MongoDB 2.6 when it is a 
non-capped collection)

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

$ git pull https://github.com/Frankst2/camel master

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

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


commit 62a8ce1d953cda0c1594ef556726d7d9f6aa3658
Author: Frank Wein 
Date:   2017-09-27T13:17:09Z

CAMEL-11848: Check for null value when getting key "capped" of collection 
stats (key/value might not exist in MongoDB 2.6)




> Using MongoDB Tailable Cursor Consumer on non-capped collection results in 
> NullPointerException (instead of proper error message)
> -
>
> Key: CAMEL-11848
> URL: https://issues.apache.org/jira/browse/CAMEL-11848
> Project: Camel
>  Issue Type: Bug
>  Components: camel-mongodb, camel-mongodb3
>Affects Versions: 2.19.3
>Reporter: Frank Wein
>Priority: Minor
> Fix For: 2.19.4, 2.20.0
>
>
> When using the Camel MongoDB component with a tailable cursor consumer on a 
> non-capped collection, you get a NullPointerException (also see 
> http://camel.apache.org/mongodb.html#MongoDB-TailableCursorConsumer on this). 
> While using this feature on a non-capped collection is not supported, the 
> error message should be better (at the moment it only throws a 
> NullPointerException because the code tries to unbox a null in a Boolean 
> object). The code actually already has a better error message, but there is a 
> small logic flaw that prevents the error message from showing up. See 
> https://github.com/apache/camel/blob/camel-2.19.3/components/camel-mongodb/src/main/java/org/apache/camel/component/mongodb/MongoDbTailingProcess.java#L78
>  for the code.



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

[jira] [Created] (CAMEL-11852) camel-milo : create karaf feature

[Luca Burgazzoli (JIRA)]

Luca Burgazzoli created CAMEL-11852:
---

 Summary: camel-milo : create karaf feature
 Key: CAMEL-11852
 URL: https://issues.apache.org/jira/browse/CAMEL-11852
 Project: Camel
  Issue Type: Task
  Components: camel-milo, karaf
Reporter: Luca Burgazzoli
Priority: Minor
 Fix For: 2.20.0






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

[jira] [Commented] (CAMEL-11848) Using MongoDB Tailable Cursor Consumer on non-capped collection results in NullPointerException (instead of proper error message)

[Frank Wein (JIRA)]

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

Frank Wein commented on CAMEL-11848:


Actually I forgot one part in my explanation: I think this might only affect 
old MongoDB versions, I tested it with 2.6. But a fix for this problem in Camel 
should be easy anyway.

> Using MongoDB Tailable Cursor Consumer on non-capped collection results in 
> NullPointerException (instead of proper error message)
> -
>
> Key: CAMEL-11848
> URL: https://issues.apache.org/jira/browse/CAMEL-11848
> Project: Camel
>  Issue Type: Bug
>  Components: camel-mongodb, camel-mongodb3
>Affects Versions: 2.19.3
>Reporter: Frank Wein
>Priority: Minor
> Fix For: 2.19.4, 2.20.0
>
>
> When using the Camel MongoDB component with a tailable cursor consumer on a 
> non-capped collection, you get a NullPointerException (also see 
> http://camel.apache.org/mongodb.html#MongoDB-TailableCursorConsumer on this). 
> While using this feature on a non-capped collection is not supported, the 
> error message should be better (at the moment it only throws a 
> NullPointerException because the code tries to unbox a null in a Boolean 
> object). The code actually already has a better error message, but there is a 
> small logic flaw that prevents the error message from showing up. See 
> https://github.com/apache/camel/blob/camel-2.19.3/components/camel-mongodb/src/main/java/org/apache/camel/component/mongodb/MongoDbTailingProcess.java#L78
>  for the code.



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

[jira] [Resolved] (CAMEL-11821) camel-xstream - tests should initialize xstream

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-11821.
-
   Resolution: Fixed
 Assignee: Claus Ibsen
Fix Version/s: (was: 2.21.0)
   2.20.0

> camel-xstream - tests should initialize xstream
> ---
>
> Key: CAMEL-11821
> URL: https://issues.apache.org/jira/browse/CAMEL-11821
> Project: Camel
>  Issue Type: Task
>  Components: camel-xstream
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
> Fix For: 2.20.0
>
>
> When testing camel-xstream we see these kind printed
> {code}
> [INFO] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.08 s 
> - in 
> org.apache.camel.dataformat.xstream.XStreamDataFormatPermissionsSystemPropertyTest
> [INFO] Running 
> org.apache.camel.dataformat.xstream.XStreamDataFormatPermissionsTest
> Security framework of XStream not initialized, XStream is probably vulnerable.
> Security framework of XStream not initialized, XStream is probably vulnerable.
> Security framework of XStream not initialized, XStream is probably vulnerable.
> Security framework of XStream not initialized, XStream is probably vulnerable.
> Security framework of XStream not initialized, XStream is probably vulnerable.
> Security framework of XStream not initialized, XStream is probably vulnerable.
> Security framework of XStream not initialized, XStream is probably vulnerable.
> Security framework of XStream not initialized, XStream is probably vulnerable.
> Security framework of XStream not initialized, XStream is probably vulnerable.
> {code}
> It would be good to investigate and see if its the unit test, or something 
> extra we need to do in camel-xstream



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

[jira] [Resolved] (CAMEL-11849) camel-crypto-cms : create karaf feature

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-11849.
-
Resolution: Fixed

> camel-crypto-cms : create karaf feature
> ---
>
> Key: CAMEL-11849
> URL: https://issues.apache.org/jira/browse/CAMEL-11849
> Project: Camel
>  Issue Type: Task
>  Components: camel-crypto-cms
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.20.0
>
>




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

[jira] [Assigned] (CAMEL-11849) camel-crypto-cms : create karaf feature

[Claus Ibsen (JIRA)]

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

Claus Ibsen reassigned CAMEL-11849:
---

Assignee: Claus Ibsen

> camel-crypto-cms : create karaf feature
> ---
>
> Key: CAMEL-11849
> URL: https://issues.apache.org/jira/browse/CAMEL-11849
> Project: Camel
>  Issue Type: Task
>  Components: camel-crypto-cms
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.20.0
>
>




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

[jira] [Commented] (CAMEL-11845) Migrate easymock and powermock to mockito

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-11845:


Github user asfgit closed the pull request at:

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


> Migrate easymock and powermock to mockito
> -
>
> Key: CAMEL-11845
> URL: https://issues.apache.org/jira/browse/CAMEL-11845
> Project: Camel
>  Issue Type: Test
>Reporter: Claus Ibsen
> Fix For: Future
>
>
> We want to only use one kind of mock testing library. They are a pain to 
> maintain and too much fuzz/magic going on. 
> The majority is using mockito, and its more popular.
> Contributions is welcome to migrate the components that uses easymock or 
> powermock



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

[jira] [Commented] (CAMEL-11845) Migrate easymock and powermock to mockito

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-11845:


GitHub user jamesnetherton opened a pull request:

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

CAMEL-11845: Remove powermock from camel-docker

Since I was already working in this area. This is a start towards 
https://issues.apache.org/jira/browse/CAMEL-11845.

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

$ git pull https://github.com/jamesnetherton/camel CAMEL-11845

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

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


commit f0376e360ee02f86525bf4a673566ab4cf976180
Author: James Netherton 
Date:   2017-09-27T10:26:39Z

CAMEL-11845: Remove powermock from camel-docker




> Migrate easymock and powermock to mockito
> -
>
> Key: CAMEL-11845
> URL: https://issues.apache.org/jira/browse/CAMEL-11845
> Project: Camel
>  Issue Type: Test
>Reporter: Claus Ibsen
> Fix For: Future
>
>
> We want to only use one kind of mock testing library. They are a pain to 
> maintain and too much fuzz/magic going on. 
> The majority is using mockito, and its more popular.
> Contributions is welcome to migrate the components that uses easymock or 
> powermock



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

[jira] [Resolved] (CAMEL-11843) Unable to configure some URI options on DockerEndpoint

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-11843.
-
Resolution: Fixed

> Unable to configure some URI options on DockerEndpoint 
> ---
>
> Key: CAMEL-11843
> URL: https://issues.apache.org/jira/browse/CAMEL-11843
> Project: Camel
>  Issue Type: Bug
>  Components: camel-docker
>Affects Versions: 2.19.3
>Reporter: James Netherton
>Assignee: James Netherton
>Priority: Minor
> Fix For: 2.19.4, 2.20.0
>
>
> The docker component triggers some [custom 
> logic|https://github.com/apache/camel/blob/master/components/camel-docker/src/main/java/org/apache/camel/component/docker/DockerComponent.java#L65]
>  to validate URI options. 
> It does not handle all of the valid set of URI options. E.g setting 
> exchangePattern, maxTotalConnections and others, results in:
> {code}
> Caused by: com.github.dockerjava.api.exception.DockerClientException: 
> bridgeErrorHandler is not a valid URI parameter
>   at 
> org.apache.camel.component.docker.DockerHelper.validateParameters(DockerHelper.java:56)
>   at 
> org.apache.camel.component.docker.DockerComponent.createEndpoint(DockerComponent.java:65)
>   at 
> org.apache.camel.impl.DefaultComponent.createEndpoint(DefaultComponent.java:126)
>   at 
> org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:703)
>   ... 51 more
> {code}



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

[jira] [Commented] (CAMEL-11843) Unable to configure some URI options on DockerEndpoint

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-11843:


Github user jamesnetherton closed the pull request at:

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


> Unable to configure some URI options on DockerEndpoint 
> ---
>
> Key: CAMEL-11843
> URL: https://issues.apache.org/jira/browse/CAMEL-11843
> Project: Camel
>  Issue Type: Bug
>  Components: camel-docker
>Affects Versions: 2.19.3
>Reporter: James Netherton
>Assignee: James Netherton
>Priority: Minor
> Fix For: 2.19.4, 2.20.0
>
>
> The docker component triggers some [custom 
> logic|https://github.com/apache/camel/blob/master/components/camel-docker/src/main/java/org/apache/camel/component/docker/DockerComponent.java#L65]
>  to validate URI options. 
> It does not handle all of the valid set of URI options. E.g setting 
> exchangePattern, maxTotalConnections and others, results in:
> {code}
> Caused by: com.github.dockerjava.api.exception.DockerClientException: 
> bridgeErrorHandler is not a valid URI parameter
>   at 
> org.apache.camel.component.docker.DockerHelper.validateParameters(DockerHelper.java:56)
>   at 
> org.apache.camel.component.docker.DockerComponent.createEndpoint(DockerComponent.java:65)
>   at 
> org.apache.camel.impl.DefaultComponent.createEndpoint(DefaultComponent.java:126)
>   at 
> org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:703)
>   ... 51 more
> {code}



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

[jira] [Commented] (CAMEL-11850) camel-hdfs2 - test fails on jdk9

[John Poth (JIRA)]

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

John Poth commented on CAMEL-11850:
---

[~davsclaus] Sure I can test out the whole build with JDK9 GA

> camel-hdfs2 - test fails on jdk9
> 
>
> Key: CAMEL-11850
> URL: https://issues.apache.org/jira/browse/CAMEL-11850
> Project: Camel
>  Issue Type: Test
>  Components: camel-hdfs2
>Reporter: Claus Ibsen
> Fix For: 2.21.0
>
>
> Failed
> org.apache.camel.component.hdfs2.FromFileToHdfsTest.testTwoFilesToHdfs
> Failing for the past 23 builds (Since #802 )
> Took 1.8 sec.
> Error Message
> Could not initialize class org.apache.hadoop.util.StringUtils
> Stacktrace
> java.lang.NoClassDefFoundError: Could not initialize class 
> org.apache.hadoop.util.StringUtils
>   at 
> org.apache.camel.component.hdfs2.FromFileToHdfsTest.setUp(FromFileToHdfsTest.java:44)



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

[jira] [Commented] (CAMEL-9856) RestSwaggerProcessor fails with "Provider org.apache.xalan.processor.TransformerFactoryImpl not found"

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-9856:


You are welcome to provide a doc update at
https://github.com/apache/camel/blob/master/components/camel-swagger-java/src/main/docs/swagger-java.adoc

> RestSwaggerProcessor fails with "Provider 
> org.apache.xalan.processor.TransformerFactoryImpl not found"
> --
>
> Key: CAMEL-9856
> URL: https://issues.apache.org/jira/browse/CAMEL-9856
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core, karaf
>Affects Versions: 2.16.3
> Environment: Karaf 4.0.3, Java 8
>Reporter: Ralf Steppacher
>Assignee: Claus Ibsen
> Fix For: 2.18.0
>
>
> When I try to query the Swagger API output for my REST routes, which are 
> defined in a Blueprint context with the XML DSL, any request to a path that I 
> think should return API information yields an empty response body (status 
> 200) on the client and this error on the server. The error is raised by 
> {{RestSwaggerSupport::getRestDefinitions(String)}} (line 147).
> {noformat}
> 2016-04-11 16:45:29,136 | WARN  | qtp215489304-167 | RestSwaggerProcessor 
> | 78 - org.apache.camel.camel-swagger-java - 2.16.3 |   | Error 
> rendering Swagger API due RuntimeException thrown in RequiredModelMBean while 
> trying to invoke operation dumpRestsAsXml
> javax.management.MBeanException: RuntimeException thrown in 
> RequiredModelMBean while trying to invoke operation dumpRestsAsXml
>   at 
> javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1285)[:1.8.0_77]
>   at 
> javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:1085)[:1.8.0_77]
>   at 
> org.apache.camel.management.MixinRequiredModelMBean.invoke(MixinRequiredModelMBean.java:70)[71:org.apache.camel.camel-core:2.16.3]
>   at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)[:1.8.0_77]
>   at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)[:1.8.0_77]
>   at 
> org.apache.camel.swagger.RestSwaggerSupport.getRestDefinitions(RestSwaggerSupport.java:147)[78:org.apache.camel.camel-swagger-java:2.16.3]
>   at 
> org.apache.camel.swagger.RestSwaggerSupport.renderResourceListing(RestSwaggerSupport.java:198)[78:org.apache.camel.camel-swagger-java:2.16.3]
>   at 
> org.apache.camel.swagger.RestSwaggerProcessor.process(RestSwaggerProcessor.java:95)[78:org.apache.camel.camel-swagger-java:2.16.3]
>   at 
> org.apache.camel.component.rest.RestApiProducer.process(RestApiProducer.java:36)[71:org.apache.camel.camel-core:2.16.3]
>   at 
> org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)[71:org.apache.camel.camel-core:2.16.3]
>   at 
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:145)[71:org.apache.camel.camel-core:2.16.3]
>   at 
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)[71:org.apache.camel.camel-core:2.16.3]
>   at 
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:460)[71:org.apache.camel.camel-core:2.16.3]
>   at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:190)[71:org.apache.camel.camel-core:2.16.3]
>   at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:190)[71:org.apache.camel.camel-core:2.16.3]
>   at 
> org.apache.camel.component.jetty.CamelContinuationServlet.service(CamelContinuationServlet.java:191)[74:org.apache.camel.camel-jetty-common:2.16.3]
>   at 
> javax.servlet.http.HttpServlet.service(HttpServlet.java:790)[63:javax.servlet-api:3.1.0]
>   at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:808)[122:org.eclipse.jetty.servlet:9.2.10.v20150310]
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669)[122:org.eclipse.jetty.servlet:9.2.10.v20150310]
>   at 
> org.eclipse.jetty.servlets.MultiPartFilter.doFilter(MultiPartFilter.java:146)[123:org.eclipse.jetty.servlets:9.2.10.v20150310]
>   at 
> org.apache.camel.component.jetty.CamelFilterWrapper.doFilter(CamelFilterWrapper.java:43)[74:org.apache.camel.camel-jetty-common:2.16.3]
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)[122:org.eclipse.jetty.servlet:9.2.10.v20150310]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)[122:org.eclipse.jetty.servlet:9.2.10.v20150310]
>   at 
> 

[jira] [Commented] (CAMEL-9856) RestSwaggerProcessor fails with "Provider org.apache.xalan.processor.TransformerFactoryImpl not found"

[Martin Lichtin (JIRA)]

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

Martin Lichtin commented on CAMEL-9856:
---

2.18.5 exhibits the same issue.
However what solves it, is to (re-) add the following system properties to 
Karaf:

{noformat}
javax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
javax.xml.transform.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl
{noformat}

Earlier releases of Karaf had these settings, but for some reason they were 
removed.

> RestSwaggerProcessor fails with "Provider 
> org.apache.xalan.processor.TransformerFactoryImpl not found"
> --
>
> Key: CAMEL-9856
> URL: https://issues.apache.org/jira/browse/CAMEL-9856
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core, karaf
>Affects Versions: 2.16.3
> Environment: Karaf 4.0.3, Java 8
>Reporter: Ralf Steppacher
>Assignee: Claus Ibsen
> Fix For: 2.18.0
>
>
> When I try to query the Swagger API output for my REST routes, which are 
> defined in a Blueprint context with the XML DSL, any request to a path that I 
> think should return API information yields an empty response body (status 
> 200) on the client and this error on the server. The error is raised by 
> {{RestSwaggerSupport::getRestDefinitions(String)}} (line 147).
> {noformat}
> 2016-04-11 16:45:29,136 | WARN  | qtp215489304-167 | RestSwaggerProcessor 
> | 78 - org.apache.camel.camel-swagger-java - 2.16.3 |   | Error 
> rendering Swagger API due RuntimeException thrown in RequiredModelMBean while 
> trying to invoke operation dumpRestsAsXml
> javax.management.MBeanException: RuntimeException thrown in 
> RequiredModelMBean while trying to invoke operation dumpRestsAsXml
>   at 
> javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1285)[:1.8.0_77]
>   at 
> javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:1085)[:1.8.0_77]
>   at 
> org.apache.camel.management.MixinRequiredModelMBean.invoke(MixinRequiredModelMBean.java:70)[71:org.apache.camel.camel-core:2.16.3]
>   at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)[:1.8.0_77]
>   at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)[:1.8.0_77]
>   at 
> org.apache.camel.swagger.RestSwaggerSupport.getRestDefinitions(RestSwaggerSupport.java:147)[78:org.apache.camel.camel-swagger-java:2.16.3]
>   at 
> org.apache.camel.swagger.RestSwaggerSupport.renderResourceListing(RestSwaggerSupport.java:198)[78:org.apache.camel.camel-swagger-java:2.16.3]
>   at 
> org.apache.camel.swagger.RestSwaggerProcessor.process(RestSwaggerProcessor.java:95)[78:org.apache.camel.camel-swagger-java:2.16.3]
>   at 
> org.apache.camel.component.rest.RestApiProducer.process(RestApiProducer.java:36)[71:org.apache.camel.camel-core:2.16.3]
>   at 
> org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)[71:org.apache.camel.camel-core:2.16.3]
>   at 
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:145)[71:org.apache.camel.camel-core:2.16.3]
>   at 
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)[71:org.apache.camel.camel-core:2.16.3]
>   at 
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:460)[71:org.apache.camel.camel-core:2.16.3]
>   at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:190)[71:org.apache.camel.camel-core:2.16.3]
>   at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:190)[71:org.apache.camel.camel-core:2.16.3]
>   at 
> org.apache.camel.component.jetty.CamelContinuationServlet.service(CamelContinuationServlet.java:191)[74:org.apache.camel.camel-jetty-common:2.16.3]
>   at 
> javax.servlet.http.HttpServlet.service(HttpServlet.java:790)[63:javax.servlet-api:3.1.0]
>   at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:808)[122:org.eclipse.jetty.servlet:9.2.10.v20150310]
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669)[122:org.eclipse.jetty.servlet:9.2.10.v20150310]
>   at 
> org.eclipse.jetty.servlets.MultiPartFilter.doFilter(MultiPartFilter.java:146)[123:org.eclipse.jetty.servlets:9.2.10.v20150310]
>   at 
> org.apache.camel.component.jetty.CamelFilterWrapper.doFilter(CamelFilterWrapper.java:43)[74:org.apache.camel.camel-jetty-common:2.16.3]
>   at 
> 

[jira] [Commented] (CAMEL-11843) Unable to configure some URI options on DockerEndpoint

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-11843:


GitHub user jamesnetherton opened a pull request:

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

CAMEL-11843: Fix issues configuring some URI options on DockerEndpoint

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

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

$ git pull https://github.com/jamesnetherton/camel CAMEL-11843

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

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


commit 35c6e0a27cd8adfca6c0aab42b4a36f0f3cfc46f
Author: James Netherton 
Date:   2017-09-27T09:36:04Z

CAMEL-11843: Fix issues configuring some URI options on DockerEndpoint




> Unable to configure some URI options on DockerEndpoint 
> ---
>
> Key: CAMEL-11843
> URL: https://issues.apache.org/jira/browse/CAMEL-11843
> Project: Camel
>  Issue Type: Bug
>  Components: camel-docker
>Affects Versions: 2.19.3
>Reporter: James Netherton
>Assignee: James Netherton
>Priority: Minor
> Fix For: 2.19.4, 2.20.0
>
>
> The docker component triggers some [custom 
> logic|https://github.com/apache/camel/blob/master/components/camel-docker/src/main/java/org/apache/camel/component/docker/DockerComponent.java#L65]
>  to validate URI options. 
> It does not handle all of the valid set of URI options. E.g setting 
> exchangePattern, maxTotalConnections and others, results in:
> {code}
> Caused by: com.github.dockerjava.api.exception.DockerClientException: 
> bridgeErrorHandler is not a valid URI parameter
>   at 
> org.apache.camel.component.docker.DockerHelper.validateParameters(DockerHelper.java:56)
>   at 
> org.apache.camel.component.docker.DockerComponent.createEndpoint(DockerComponent.java:65)
>   at 
> org.apache.camel.impl.DefaultComponent.createEndpoint(DefaultComponent.java:126)
>   at 
> org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:703)
>   ... 51 more
> {code}



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

[jira] [Commented] (CAMEL-11850) camel-hdfs2 - test fails on jdk9

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-11850:
-

There is a similar problem with camel-hdfs. 

It may be that they are not JDK9 compatible

> camel-hdfs2 - test fails on jdk9
> 
>
> Key: CAMEL-11850
> URL: https://issues.apache.org/jira/browse/CAMEL-11850
> Project: Camel
>  Issue Type: Test
>  Components: camel-hdfs2
>Reporter: Claus Ibsen
> Fix For: 2.21.0
>
>
> Failed
> org.apache.camel.component.hdfs2.FromFileToHdfsTest.testTwoFilesToHdfs
> Failing for the past 23 builds (Since #802 )
> Took 1.8 sec.
> Error Message
> Could not initialize class org.apache.hadoop.util.StringUtils
> Stacktrace
> java.lang.NoClassDefFoundError: Could not initialize class 
> org.apache.hadoop.util.StringUtils
>   at 
> org.apache.camel.component.hdfs2.FromFileToHdfsTest.setUp(FromFileToHdfsTest.java:44)



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

[jira] [Commented] (CAMEL-11850) camel-hdfs2 - test fails on jdk9

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-11850:
-

[~jpoth] if you want to help again with jdk9 issues, then camel-hdfs2 fails all 
tests on JDK9

> camel-hdfs2 - test fails on jdk9
> 
>
> Key: CAMEL-11850
> URL: https://issues.apache.org/jira/browse/CAMEL-11850
> Project: Camel
>  Issue Type: Test
>  Components: camel-hdfs2
>Reporter: Claus Ibsen
> Fix For: 2.21.0
>
>
> Failed
> org.apache.camel.component.hdfs2.FromFileToHdfsTest.testTwoFilesToHdfs
> Failing for the past 23 builds (Since #802 )
> Took 1.8 sec.
> Error Message
> Could not initialize class org.apache.hadoop.util.StringUtils
> Stacktrace
> java.lang.NoClassDefFoundError: Could not initialize class 
> org.apache.hadoop.util.StringUtils
>   at 
> org.apache.camel.component.hdfs2.FromFileToHdfsTest.setUp(FromFileToHdfsTest.java:44)



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

[jira] [Created] (CAMEL-11850) camel-hdfs2 - test fails on jdk9

[Claus Ibsen (JIRA)]

Claus Ibsen created CAMEL-11850:
---

 Summary: camel-hdfs2 - test fails on jdk9
 Key: CAMEL-11850
 URL: https://issues.apache.org/jira/browse/CAMEL-11850
 Project: Camel
  Issue Type: Test
  Components: camel-hdfs2
Reporter: Claus Ibsen
 Fix For: 2.21.0


Failed

org.apache.camel.component.hdfs2.FromFileToHdfsTest.testTwoFilesToHdfs

Failing for the past 23 builds (Since #802 )
Took 1.8 sec.
Error Message

Could not initialize class org.apache.hadoop.util.StringUtils
Stacktrace

java.lang.NoClassDefFoundError: Could not initialize class 
org.apache.hadoop.util.StringUtils
at 
org.apache.camel.component.hdfs2.FromFileToHdfsTest.setUp(FromFileToHdfsTest.java:44)



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

[jira] [Updated] (CAMEL-11818) cluster-service : review spring boot configuration order

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli updated CAMEL-11818:

Summary: cluster-service : review spring boot configuration order  (was: 
cluster-service : review spring boot configuration torder)

> cluster-service : review spring boot configuration order
> 
>
> Key: CAMEL-11818
> URL: https://issues.apache.org/jira/browse/CAMEL-11818
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-spring-boot, camel-spring-boot-starters
>Affects Versions: 2.20.0
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
>  Labels: clustering
> Fix For: 2.21.0
>
>
> As today cluster services are configured before the camel context starts but 
> some implementation may require the camel context to be there already so we 
> should investigate if we can use afterPropertiesSet or something similar to 
> bind the service to the context.



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

[jira] [Work started] (CAMEL-11847) cluster-service : support multiple cluster services

[Luca Burgazzoli (JIRA)]

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

Work on CAMEL-11847 started by Luca Burgazzoli.
---
> cluster-service : support multiple cluster services
> ---
>
> Key: CAMEL-11847
> URL: https://issues.apache.org/jira/browse/CAMEL-11847
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Affects Versions: 2.20.0
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>  Labels: clustering
> Fix For: 2.20.0
>
>




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

[jira] [Commented] (CAMEL-11843) Unable to configure some URI options on DockerEndpoint

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-11843:
-

Then its probably better to go the other way of not doing this magic 
validation, so its similar to other lenient properties components. Its a bit of 
hazzle to configure via headers. So I would remove that special validation 
check, and then Camel users should configure it properly

> Unable to configure some URI options on DockerEndpoint 
> ---
>
> Key: CAMEL-11843
> URL: https://issues.apache.org/jira/browse/CAMEL-11843
> Project: Camel
>  Issue Type: Bug
>  Components: camel-docker
>Affects Versions: 2.19.3
>Reporter: James Netherton
>Assignee: James Netherton
>Priority: Minor
> Fix For: 2.19.4, 2.20.0
>
>
> The docker component triggers some [custom 
> logic|https://github.com/apache/camel/blob/master/components/camel-docker/src/main/java/org/apache/camel/component/docker/DockerComponent.java#L65]
>  to validate URI options. 
> It does not handle all of the valid set of URI options. E.g setting 
> exchangePattern, maxTotalConnections and others, results in:
> {code}
> Caused by: com.github.dockerjava.api.exception.DockerClientException: 
> bridgeErrorHandler is not a valid URI parameter
>   at 
> org.apache.camel.component.docker.DockerHelper.validateParameters(DockerHelper.java:56)
>   at 
> org.apache.camel.component.docker.DockerComponent.createEndpoint(DockerComponent.java:65)
>   at 
> org.apache.camel.impl.DefaultComponent.createEndpoint(DefaultComponent.java:126)
>   at 
> org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:703)
>   ... 51 more
> {code}



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

[jira] [Commented] (CAMEL-11843) Unable to configure some URI options on DockerEndpoint

[James Netherton (JIRA)]

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

James Netherton commented on CAMEL-11843:
-

Turns out this component is a little odd. The endpoint is isLenientProperties = 
true. 

It allows users to configure different URI options depending on the docker 
operation. Hence there is no fixed set of URI params.

We could change it to  isLenientProperties = false so that the generic 
validation kicks in. But this would throw an error on a URI like 
{{docker:stats?host=foo=bar=abc123}}, because containerId is 
not an @UriOption in the DockerConfiguration class.

All of the extra docker operation specific URI params can already be configured 
as headers. So is it ok to force users to configure these extra options only 
via headers instead of URI params?



> Unable to configure some URI options on DockerEndpoint 
> ---
>
> Key: CAMEL-11843
> URL: https://issues.apache.org/jira/browse/CAMEL-11843
> Project: Camel
>  Issue Type: Bug
>  Components: camel-docker
>Affects Versions: 2.19.3
>Reporter: James Netherton
>Assignee: James Netherton
>Priority: Minor
> Fix For: 2.19.4, 2.20.0
>
>
> The docker component triggers some [custom 
> logic|https://github.com/apache/camel/blob/master/components/camel-docker/src/main/java/org/apache/camel/component/docker/DockerComponent.java#L65]
>  to validate URI options. 
> It does not handle all of the valid set of URI options. E.g setting 
> exchangePattern, maxTotalConnections and others, results in:
> {code}
> Caused by: com.github.dockerjava.api.exception.DockerClientException: 
> bridgeErrorHandler is not a valid URI parameter
>   at 
> org.apache.camel.component.docker.DockerHelper.validateParameters(DockerHelper.java:56)
>   at 
> org.apache.camel.component.docker.DockerComponent.createEndpoint(DockerComponent.java:65)
>   at 
> org.apache.camel.impl.DefaultComponent.createEndpoint(DefaultComponent.java:126)
>   at 
> org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:703)
>   ... 51 more
> {code}



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

[jira] [Commented] (CAMEL-9275) camel-jackson - Allow to use a custom ObjectMapper instance

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-9275:


Look at the commits

> camel-jackson - Allow to use a custom ObjectMapper instance
> ---
>
> Key: CAMEL-9275
> URL: https://issues.apache.org/jira/browse/CAMEL-9275
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-jackson
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.17.0
>
>
> People may configure a ObjectMapper instance themselves and want to use that 
> with the data format.
> See SO
> http://stackoverflow.com/questions/33397359/how-to-configure-jackson-objectmapper-for-camel-in-spring-boot



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

[jira] [Commented] (CAMEL-9275) camel-jackson - Allow to use a custom ObjectMapper instance

[Jacek Obarymski (JIRA)]

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

Jacek Obarymski commented on CAMEL-9275:


how do we make use of the fix?

> camel-jackson - Allow to use a custom ObjectMapper instance
> ---
>
> Key: CAMEL-9275
> URL: https://issues.apache.org/jira/browse/CAMEL-9275
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-jackson
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.17.0
>
>
> People may configure a ObjectMapper instance themselves and want to use that 
> with the data format.
> See SO
> http://stackoverflow.com/questions/33397359/how-to-configure-jackson-objectmapper-for-camel-in-spring-boot



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

[jira] [Created] (CAMEL-11849) camel-crypto-cms : create karaf feature

[Luca Burgazzoli (JIRA)]

Luca Burgazzoli created CAMEL-11849:
---

 Summary: camel-crypto-cms : create karaf feature
 Key: CAMEL-11849
 URL: https://issues.apache.org/jira/browse/CAMEL-11849
 Project: Camel
  Issue Type: Task
  Components: camel-crypto-cms
Reporter: Luca Burgazzoli
Priority: Minor
 Fix For: 2.20.0






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

[jira] [Work started] (CAMEL-9008) Contributing GRPC / Thrift support to Camel

[Dmitry Volodin (JIRA)]

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

Work on CAMEL-9008 started by Dmitry Volodin.
-
> Contributing GRPC / Thrift support to Camel
> ---
>
> Key: CAMEL-9008
> URL: https://issues.apache.org/jira/browse/CAMEL-9008
> Project: Camel
>  Issue Type: New Feature
>Reporter: Andrew Harmel-Law
>Assignee: Dmitry Volodin
> Fix For: 2.20.0
>
>
> Hi,
> We're building Microservices with Camel, predominantly producing from REST 
> DSL components and have got to the point where having an easy way to swap in 
> GRPC [1] / Thrift [2] endpoints and clients would be of great help.
> We wondered if this was already on the cards for a future release, and if we 
> might be able to work on it, and if not, if it would be something we could 
> work on and contribute (with guidance to smooth the design and 
> implementation)?
> Kind regards, the Capgemini UK and Indian Camel teams
> [1] http://www.grpc.io/
> [2] https://thrift.apache.org/



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

[jira] [Updated] (CAMEL-11847) cluster-service : support multiple cluster services

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli updated CAMEL-11847:

Fix Version/s: (was: 2.21.0)
   2.20.0

> cluster-service : support multiple cluster services
> ---
>
> Key: CAMEL-11847
> URL: https://issues.apache.org/jira/browse/CAMEL-11847
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Affects Versions: 2.20.0
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>  Labels: clustering
> Fix For: 2.20.0
>
>




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

[jira] [Resolved] (CAMEL-11790) camel-headersmap : create karaf feature

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-11790.
-
Resolution: Fixed

> camel-headersmap : create karaf feature
> ---
>
> Key: CAMEL-11790
> URL: https://issues.apache.org/jira/browse/CAMEL-11790
> Project: Camel
>  Issue Type: Task
>  Components: camel-headersmap
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.20.0
>
>




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

[jira] [Commented] (CAMEL-11790) camel-headersmap : create karaf feature

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-11790:
-

Okay working on this, and I can now see on karaf that it has detected the 
custom headers map
{code}
2017-09-27 09:36:49,294 | INFO  | nt Dispatcher: 1 | HeadersMapFactoryResolver  
  | 54 - org.apache.camel.camel-core - 2.20.0.SNAPSHOT | Detected and using 
custom HeadersMapFactory: 
org.apache.camel.component.headersmap.FastHeadersMapFactory@7e050f52
{code}

> camel-headersmap : create karaf feature
> ---
>
> Key: CAMEL-11790
> URL: https://issues.apache.org/jira/browse/CAMEL-11790
> Project: Camel
>  Issue Type: Task
>  Components: camel-headersmap
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.20.0
>
>




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

[jira] [Assigned] (CAMEL-11790) camel-headersmap : create karaf feature

[Claus Ibsen (JIRA)]

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

Claus Ibsen reassigned CAMEL-11790:
---

Assignee: Claus Ibsen  (was: Luca Burgazzoli)

> camel-headersmap : create karaf feature
> ---
>
> Key: CAMEL-11790
> URL: https://issues.apache.org/jira/browse/CAMEL-11790
> Project: Camel
>  Issue Type: Task
>  Components: camel-headersmap
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.20.0
>
>




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

[jira] [Commented] (CAMEL-11843) Unable to configure some URI options on DockerEndpoint

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-11843:
-

Thanks, do you mind fixing the validation first, as its most important. We plan 
to cut 2.20.0 end of this month and would like this fix to be included.

> Unable to configure some URI options on DockerEndpoint 
> ---
>
> Key: CAMEL-11843
> URL: https://issues.apache.org/jira/browse/CAMEL-11843
> Project: Camel
>  Issue Type: Bug
>  Components: camel-docker
>Affects Versions: 2.19.3
>Reporter: James Netherton
>Assignee: James Netherton
>Priority: Minor
> Fix For: 2.19.4, 2.20.0
>
>
> The docker component triggers some [custom 
> logic|https://github.com/apache/camel/blob/master/components/camel-docker/src/main/java/org/apache/camel/component/docker/DockerComponent.java#L65]
>  to validate URI options. 
> It does not handle all of the valid set of URI options. E.g setting 
> exchangePattern, maxTotalConnections and others, results in:
> {code}
> Caused by: com.github.dockerjava.api.exception.DockerClientException: 
> bridgeErrorHandler is not a valid URI parameter
>   at 
> org.apache.camel.component.docker.DockerHelper.validateParameters(DockerHelper.java:56)
>   at 
> org.apache.camel.component.docker.DockerComponent.createEndpoint(DockerComponent.java:65)
>   at 
> org.apache.camel.impl.DefaultComponent.createEndpoint(DefaultComponent.java:126)
>   at 
> org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:703)
>   ... 51 more
> {code}



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

[jira] [Commented] (CAMEL-11843) Unable to configure some URI options on DockerEndpoint

[James Netherton (JIRA)]

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

James Netherton commented on CAMEL-11843:
-

I'll take a look. I'll try to remove the power mock stuff from this component 
too.

It's my last day before holiday so I may not get back to this for a couple of 
weeks.


> Unable to configure some URI options on DockerEndpoint 
> ---
>
> Key: CAMEL-11843
> URL: https://issues.apache.org/jira/browse/CAMEL-11843
> Project: Camel
>  Issue Type: Bug
>  Components: camel-docker
>Affects Versions: 2.19.3
>Reporter: James Netherton
>Assignee: James Netherton
>Priority: Minor
> Fix For: 2.19.4, 2.20.0
>
>
> The docker component triggers some [custom 
> logic|https://github.com/apache/camel/blob/master/components/camel-docker/src/main/java/org/apache/camel/component/docker/DockerComponent.java#L65]
>  to validate URI options. 
> It does not handle all of the valid set of URI options. E.g setting 
> exchangePattern, maxTotalConnections and others, results in:
> {code}
> Caused by: com.github.dockerjava.api.exception.DockerClientException: 
> bridgeErrorHandler is not a valid URI parameter
>   at 
> org.apache.camel.component.docker.DockerHelper.validateParameters(DockerHelper.java:56)
>   at 
> org.apache.camel.component.docker.DockerComponent.createEndpoint(DockerComponent.java:65)
>   at 
> org.apache.camel.impl.DefaultComponent.createEndpoint(DefaultComponent.java:126)
>   at 
> org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:703)
>   ... 51 more
> {code}



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

[jira] [Updated] (CAMEL-11823) [example] cdi-cassandrasql - nodetool: Failed to connect to '127.0.0.1:7199' - ConnectException: 'Connection refused'

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-11823:

Fix Version/s: (was: 2.20.0)
   2.21.0

> [example] cdi-cassandrasql - nodetool: Failed to connect to '127.0.0.1:7199' 
> - ConnectException: 'Connection refused'
> -
>
> Key: CAMEL-11823
> URL: https://issues.apache.org/jira/browse/CAMEL-11823
> Project: Camel
>  Issue Type: Sub-task
>  Components: examples
>Affects Versions: 2.20.0
>Reporter: Tomohisa Igarashi
> Fix For: 2.21.0
>
>
> something wrong with docker image
> {code}
> $ docker exec -ti master_node /opt/cassandra/bin/nodetool status
> nodetool: Failed to connect to '127.0.0.1:7199' - ConnectException: 
> 'Connection refused'.
> {code}
> {code}
> $ docker logs master_node
> *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
> *** Running /etc/rc.local...
> *** Booting runit daemon...
> *** Runit started as PID 8
> I'm starting cassandra
> tail: unrecognized file system type 0x794c7630 for ‘/var/log/syslog’. please 
> report this to bug-coreut...@gnu.org. reverting to polling
> Filling in the blanks inside cassandra.yaml
> Java HotSpot(TM) 64-Bit Server VM warning: Cannot open file 
> bin/../logs/gc.log due to No such file or directory
> ./run: line 31:28 Killed  bin/cassandra -Rf
> I'm starting cassandra
> Java HotSpot(TM) 64-Bit Server VM warning: Cannot open file 
> bin/../logs/gc.log due to No such file or directory
> ./run: line 31:93 Killed  bin/cassandra -Rf
> I'm starting cassandra
> Java HotSpot(TM) 64-Bit Server VM warning: Cannot open file 
> bin/../logs/gc.log due to No such file or directory
> ./run: line 31:   159 Killed  bin/cassandra -Rf
> {code}



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

[jira] [Assigned] (CAMEL-11823) [example] cdi-cassandrasql - nodetool: Failed to connect to '127.0.0.1:7199' - ConnectException: 'Connection refused'

[Claus Ibsen (JIRA)]

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

Claus Ibsen reassigned CAMEL-11823:
---

Assignee: Andrea Cosentino

> [example] cdi-cassandrasql - nodetool: Failed to connect to '127.0.0.1:7199' 
> - ConnectException: 'Connection refused'
> -
>
> Key: CAMEL-11823
> URL: https://issues.apache.org/jira/browse/CAMEL-11823
> Project: Camel
>  Issue Type: Sub-task
>  Components: examples
>Affects Versions: 2.20.0
>Reporter: Tomohisa Igarashi
>Assignee: Andrea Cosentino
> Fix For: 2.21.0
>
>
> something wrong with docker image
> {code}
> $ docker exec -ti master_node /opt/cassandra/bin/nodetool status
> nodetool: Failed to connect to '127.0.0.1:7199' - ConnectException: 
> 'Connection refused'.
> {code}
> {code}
> $ docker logs master_node
> *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
> *** Running /etc/rc.local...
> *** Booting runit daemon...
> *** Runit started as PID 8
> I'm starting cassandra
> tail: unrecognized file system type 0x794c7630 for ‘/var/log/syslog’. please 
> report this to bug-coreut...@gnu.org. reverting to polling
> Filling in the blanks inside cassandra.yaml
> Java HotSpot(TM) 64-Bit Server VM warning: Cannot open file 
> bin/../logs/gc.log due to No such file or directory
> ./run: line 31:28 Killed  bin/cassandra -Rf
> I'm starting cassandra
> Java HotSpot(TM) 64-Bit Server VM warning: Cannot open file 
> bin/../logs/gc.log due to No such file or directory
> ./run: line 31:93 Killed  bin/cassandra -Rf
> I'm starting cassandra
> Java HotSpot(TM) 64-Bit Server VM warning: Cannot open file 
> bin/../logs/gc.log due to No such file or directory
> ./run: line 31:   159 Killed  bin/cassandra -Rf
> {code}



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

[jira] [Assigned] (CAMEL-11843) Unable to configure some URI options on DockerEndpoint

[James Netherton (JIRA)]

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

James Netherton reassigned CAMEL-11843:
---

Assignee: James Netherton

> Unable to configure some URI options on DockerEndpoint 
> ---
>
> Key: CAMEL-11843
> URL: https://issues.apache.org/jira/browse/CAMEL-11843
> Project: Camel
>  Issue Type: Bug
>  Components: camel-docker
>Affects Versions: 2.19.3
>Reporter: James Netherton
>Assignee: James Netherton
>Priority: Minor
> Fix For: 2.19.4, 2.20.0
>
>
> The docker component triggers some [custom 
> logic|https://github.com/apache/camel/blob/master/components/camel-docker/src/main/java/org/apache/camel/component/docker/DockerComponent.java#L65]
>  to validate URI options. 
> It does not handle all of the valid set of URI options. E.g setting 
> exchangePattern, maxTotalConnections and others, results in:
> {code}
> Caused by: com.github.dockerjava.api.exception.DockerClientException: 
> bridgeErrorHandler is not a valid URI parameter
>   at 
> org.apache.camel.component.docker.DockerHelper.validateParameters(DockerHelper.java:56)
>   at 
> org.apache.camel.component.docker.DockerComponent.createEndpoint(DockerComponent.java:65)
>   at 
> org.apache.camel.impl.DefaultComponent.createEndpoint(DefaultComponent.java:126)
>   at 
> org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:703)
>   ... 51 more
> {code}



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

[jira] [Commented] (CAMEL-11832) camel-aws - Add support for Lambda

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-11832:
-

Awesome, thanks Thomas

> camel-aws - Add support for Lambda
> --
>
> Key: CAMEL-11832
> URL: https://issues.apache.org/jira/browse/CAMEL-11832
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-aws
>Reporter: Claus Ibsen
> Fix For: 2.21.0
>
>
> We should make it easier to use AWS Lambdas with Apache Camel.
> There is a little example here
> https://github.com/garciapau/LambdaRidingCamel
> If we could make that more like a native Camel component so you can just do a 
> Camel route or something with from aws-lambda:xxx to xxx etc.



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

[jira] [Updated] (CAMEL-11832) camel-aws - Add support for Lambda

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-11832:

Fix Version/s: (was: Future)
   2.21.0

> camel-aws - Add support for Lambda
> --
>
> Key: CAMEL-11832
> URL: https://issues.apache.org/jira/browse/CAMEL-11832
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-aws
>Reporter: Claus Ibsen
> Fix For: 2.21.0
>
>
> We should make it easier to use AWS Lambdas with Apache Camel.
> There is a little example here
> https://github.com/garciapau/LambdaRidingCamel
> If we could make that more like a native Camel component so you can just do a 
> Camel route or something with from aws-lambda:xxx to xxx etc.



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

[jira] [Resolved] (CAMEL-11830) [example] sql - no application log on karaf

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-11830.
-
Resolution: Fixed
  Assignee: Claus Ibsen

Its the camel-example-sql-blueprint that works in Karaf. The camel-example-sql 
has been delated as it was not working correctly.

> [example] sql - no application log on karaf
> ---
>
> Key: CAMEL-11830
> URL: https://issues.apache.org/jira/browse/CAMEL-11830
> Project: Camel
>  Issue Type: Sub-task
>  Components: examples
>Reporter: Tomohisa Igarashi
>Assignee: Claus Ibsen
> Fix For: 2.20.0
>
>
> On karaf, 4.1.1 bundle successfully starts but no application log
> {code}
> 2017-09-24 21:32:19,327 | INFO  | pool-3-thread-1  | FeaturesServiceImpl  
> | 9 - org.apache.karaf.features.core - 4.1.1 | Starting bundles:
> 2017-09-24 21:32:19,333 | INFO  | pool-3-thread-1  | FeaturesServiceImpl  
> | 9 - org.apache.karaf.features.core - 4.1.1 |   
> org.apache.servicemix.bundles.aopalliance/1.0.0.6
> 2017-09-24 21:32:19,334 | INFO  | pool-3-thread-1  | FeaturesServiceImpl  
> | 9 - org.apache.karaf.features.core - 4.1.1 |   
> org.apache.servicemix.bundles.spring-core/4.3.5.RELEASE_1
> 2017-09-24 21:32:19,335 | INFO  | pool-3-thread-1  | FeaturesServiceImpl  
> | 9 - org.apache.karaf.features.core - 4.1.1 |   
> org.apache.servicemix.bundles.spring-beans/4.3.5.RELEASE_1
> 2017-09-24 21:32:19,336 | INFO  | pool-3-thread-1  | FeaturesServiceImpl  
> | 9 - org.apache.karaf.features.core - 4.1.1 |   
> org.apache.servicemix.bundles.spring-aop/4.3.5.RELEASE_1
> 2017-09-24 21:32:19,338 | INFO  | pool-3-thread-1  | FeaturesServiceImpl  
> | 9 - org.apache.karaf.features.core - 4.1.1 |   
> org.apache.servicemix.bundles.spring-expression/4.3.5.RELEASE_1
> 2017-09-24 21:32:19,339 | INFO  | pool-3-thread-1  | FeaturesServiceImpl  
> | 9 - org.apache.karaf.features.core - 4.1.1 |   
> org.apache.servicemix.bundles.spring-context/4.3.5.RELEASE_1
> 2017-09-24 21:32:19,340 | INFO  | pool-3-thread-1  | FeaturesServiceImpl  
> | 9 - org.apache.karaf.features.core - 4.1.1 |   
> org.apache.servicemix.bundles.spring-tx/4.3.5.RELEASE_1
> 2017-09-24 21:32:19,341 | INFO  | pool-3-thread-1  | FeaturesServiceImpl  
> | 9 - org.apache.karaf.features.core - 4.1.1 |   
> org.apache.servicemix.bundles.spring-jdbc/4.3.5.RELEASE_1
> 2017-09-24 21:32:19,341 | INFO  | pool-3-thread-1  | FeaturesServiceImpl  
> | 9 - org.apache.karaf.features.core - 4.1.1 |   
> org.apache.servicemix.bundles.spring-context-support/4.3.5.RELEASE_1
> 2017-09-24 21:32:19,342 | INFO  | pool-3-thread-1  | FeaturesServiceImpl  
> | 9 - org.apache.karaf.features.core - 4.1.1 |   
> org.apache.camel.camel-core/2.20.0.SNAPSHOT
> 2017-09-24 21:32:19,344 | INFO  | pool-3-thread-1  | Activator
> | 54 - org.apache.camel.camel-core - 2.20.0.SNAPSHOT | Camel 
> activator starting
> 2017-09-24 21:32:19,350 | INFO  | pool-3-thread-1  | Activator
> | 54 - org.apache.camel.camel-core - 2.20.0.SNAPSHOT | Camel 
> activator started
> 2017-09-24 21:32:19,364 | INFO  | pool-3-thread-1  | FeaturesServiceImpl  
> | 9 - org.apache.karaf.features.core - 4.1.1 |   
> org.apache.camel.camel-spring/2.20.0.SNAPSHOT
> 2017-09-24 21:32:19,368 | INFO  | pool-3-thread-1  | FeaturesServiceImpl  
> | 9 - org.apache.karaf.features.core - 4.1.1 |   
> org.apache.camel.camel-sql/2.20.0.SNAPSHOT
> 2017-09-24 21:32:19,370 | INFO  | pool-3-thread-1  | FeaturesServiceImpl  
> | 9 - org.apache.karaf.features.core - 4.1.1 |   
> org.apache.geronimo.specs.geronimo-jta_1.1_spec/1.1.1
> 2017-09-24 21:32:19,371 | INFO  | pool-3-thread-1  | FeaturesServiceImpl  
> | 9 - org.apache.karaf.features.core - 4.1.1 |   
> org.apache.camel.camel-blueprint/2.20.0.SNAPSHOT
> 2017-09-24 21:32:19,380 | INFO  | pool-3-thread-1  | FeaturesServiceImpl  
> | 9 - org.apache.karaf.features.core - 4.1.1 |   
> org.apache.camel.camel-commands-core/2.20.0.SNAPSHOT
> 2017-09-24 21:32:19,381 | INFO  | pool-3-thread-1  | FeaturesServiceImpl  
> | 9 - org.apache.karaf.features.core - 4.1.1 |   
> org.apache.commons.pool2/2.4.2
> 2017-09-24 21:32:19,382 | INFO  | pool-3-thread-1  | FeaturesServiceImpl  
> | 9 - org.apache.karaf.features.core - 4.1.1 |   
> org.apache.camel.karaf.camel-karaf-commands/2.20.0.SNAPSHOT
> 2017-09-24 21:32:19,398 | INFO  | pool-3-thread-1  | CommandExtension 
> | 42 - org.apache.karaf.shell.core - 4.1.1 | Registering commands for 
> bundle org.apache.camel.karaf.camel-karaf-commands/2.20.0.SNAPSHOT
> 2017-09-24 21:32:19,399 | INFO  | pool-3-thread-1  | 

[jira] [Commented] (CAMEL-11832) camel-aws - Add support for Lambda

[Thomas Lehoux (JIRA)]

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

Thomas Lehoux commented on CAMEL-11832:
---

As I said in gitter's room, I'm working on such a camel-aws component.

> camel-aws - Add support for Lambda
> --
>
> Key: CAMEL-11832
> URL: https://issues.apache.org/jira/browse/CAMEL-11832
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-aws
>Reporter: Claus Ibsen
> Fix For: Future
>
>
> We should make it easier to use AWS Lambdas with Apache Camel.
> There is a little example here
> https://github.com/garciapau/LambdaRidingCamel
> If we could make that more like a native Camel component so you can just do a 
> Camel route or something with from aws-lambda:xxx to xxx etc.



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

[jira] [Updated] (CAMEL-11832) camel-aws - Add support for Lambda

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-11832:

Fix Version/s: Future

> camel-aws - Add support for Lambda
> --
>
> Key: CAMEL-11832
> URL: https://issues.apache.org/jira/browse/CAMEL-11832
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-aws
>Reporter: Claus Ibsen
> Fix For: Future
>
>
> We should make it easier to use AWS Lambdas with Apache Camel.
> There is a little example here
> https://github.com/garciapau/LambdaRidingCamel
> If we could make that more like a native Camel component so you can just do a 
> Camel route or something with from aws-lambda:xxx to xxx etc.



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

[jira] [Commented] (CAMEL-11832) camel-aws - Add support for Lambda

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-11832:
-

At first we are looking for support to allow Camel to call an existing lambda 
function, eg as a producer in camel-aws. Not so much about running a JVM + 
Camel as a lambda itself.

> camel-aws - Add support for Lambda
> --
>
> Key: CAMEL-11832
> URL: https://issues.apache.org/jira/browse/CAMEL-11832
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-aws
>Reporter: Claus Ibsen
> Fix For: Future
>
>
> We should make it easier to use AWS Lambdas with Apache Camel.
> There is a little example here
> https://github.com/garciapau/LambdaRidingCamel
> If we could make that more like a native Camel component so you can just do a 
> Camel route or something with from aws-lambda:xxx to xxx etc.



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

[jira] [Commented] (CAMEL-11843) Unable to configure some URI options on DockerEndpoint

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-11843:
-

You are welcome to work on a fix. I wonder if this validation is needed at all? 
Or if so it should only do very specific validation of a limited set of known 
docker only options.

The default component will do generic validation afterwards.

> Unable to configure some URI options on DockerEndpoint 
> ---
>
> Key: CAMEL-11843
> URL: https://issues.apache.org/jira/browse/CAMEL-11843
> Project: Camel
>  Issue Type: Bug
>  Components: camel-docker
>Affects Versions: 2.19.3
>Reporter: James Netherton
>Priority: Minor
> Fix For: 2.19.4, 2.20.0
>
>
> The docker component triggers some [custom 
> logic|https://github.com/apache/camel/blob/master/components/camel-docker/src/main/java/org/apache/camel/component/docker/DockerComponent.java#L65]
>  to validate URI options. 
> It does not handle all of the valid set of URI options. E.g setting 
> exchangePattern, maxTotalConnections and others, results in:
> {code}
> Caused by: com.github.dockerjava.api.exception.DockerClientException: 
> bridgeErrorHandler is not a valid URI parameter
>   at 
> org.apache.camel.component.docker.DockerHelper.validateParameters(DockerHelper.java:56)
>   at 
> org.apache.camel.component.docker.DockerComponent.createEndpoint(DockerComponent.java:65)
>   at 
> org.apache.camel.impl.DefaultComponent.createEndpoint(DefaultComponent.java:126)
>   at 
> org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:703)
>   ... 51 more
> {code}



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

[jira] [Updated] (CAMEL-11843) Unable to configure some URI options on DockerEndpoint

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-11843:

Estimated Complexity: Novice  (was: Unknown)

> Unable to configure some URI options on DockerEndpoint 
> ---
>
> Key: CAMEL-11843
> URL: https://issues.apache.org/jira/browse/CAMEL-11843
> Project: Camel
>  Issue Type: Bug
>  Components: camel-docker
>Affects Versions: 2.19.3
>Reporter: James Netherton
>Priority: Minor
> Fix For: 2.19.4, 2.20.0
>
>
> The docker component triggers some [custom 
> logic|https://github.com/apache/camel/blob/master/components/camel-docker/src/main/java/org/apache/camel/component/docker/DockerComponent.java#L65]
>  to validate URI options. 
> It does not handle all of the valid set of URI options. E.g setting 
> exchangePattern, maxTotalConnections and others, results in:
> {code}
> Caused by: com.github.dockerjava.api.exception.DockerClientException: 
> bridgeErrorHandler is not a valid URI parameter
>   at 
> org.apache.camel.component.docker.DockerHelper.validateParameters(DockerHelper.java:56)
>   at 
> org.apache.camel.component.docker.DockerComponent.createEndpoint(DockerComponent.java:65)
>   at 
> org.apache.camel.impl.DefaultComponent.createEndpoint(DefaultComponent.java:126)
>   at 
> org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:703)
>   ... 51 more
> {code}



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

[jira] [Updated] (CAMEL-11843) Unable to configure some URI options on DockerEndpoint

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-11843:

Affects Version/s: (was: 2.20.0)

> Unable to configure some URI options on DockerEndpoint 
> ---
>
> Key: CAMEL-11843
> URL: https://issues.apache.org/jira/browse/CAMEL-11843
> Project: Camel
>  Issue Type: Bug
>  Components: camel-docker
>Affects Versions: 2.19.3
>Reporter: James Netherton
>Priority: Minor
> Fix For: 2.19.4, 2.20.0
>
>
> The docker component triggers some [custom 
> logic|https://github.com/apache/camel/blob/master/components/camel-docker/src/main/java/org/apache/camel/component/docker/DockerComponent.java#L65]
>  to validate URI options. 
> It does not handle all of the valid set of URI options. E.g setting 
> exchangePattern, maxTotalConnections and others, results in:
> {code}
> Caused by: com.github.dockerjava.api.exception.DockerClientException: 
> bridgeErrorHandler is not a valid URI parameter
>   at 
> org.apache.camel.component.docker.DockerHelper.validateParameters(DockerHelper.java:56)
>   at 
> org.apache.camel.component.docker.DockerComponent.createEndpoint(DockerComponent.java:65)
>   at 
> org.apache.camel.impl.DefaultComponent.createEndpoint(DefaultComponent.java:126)
>   at 
> org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:703)
>   ... 51 more
> {code}



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

[jira] [Updated] (CAMEL-11843) Unable to configure some URI options on DockerEndpoint

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-11843:

Fix Version/s: 2.20.0
   2.19.4

> Unable to configure some URI options on DockerEndpoint 
> ---
>
> Key: CAMEL-11843
> URL: https://issues.apache.org/jira/browse/CAMEL-11843
> Project: Camel
>  Issue Type: Bug
>  Components: camel-docker
>Affects Versions: 2.19.3
>Reporter: James Netherton
>Priority: Minor
> Fix For: 2.19.4, 2.20.0
>
>
> The docker component triggers some [custom 
> logic|https://github.com/apache/camel/blob/master/components/camel-docker/src/main/java/org/apache/camel/component/docker/DockerComponent.java#L65]
>  to validate URI options. 
> It does not handle all of the valid set of URI options. E.g setting 
> exchangePattern, maxTotalConnections and others, results in:
> {code}
> Caused by: com.github.dockerjava.api.exception.DockerClientException: 
> bridgeErrorHandler is not a valid URI parameter
>   at 
> org.apache.camel.component.docker.DockerHelper.validateParameters(DockerHelper.java:56)
>   at 
> org.apache.camel.component.docker.DockerComponent.createEndpoint(DockerComponent.java:65)
>   at 
> org.apache.camel.impl.DefaultComponent.createEndpoint(DefaultComponent.java:126)
>   at 
> org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:703)
>   ... 51 more
> {code}



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

[jira] [Resolved] (CAMEL-11808) log4j2 2.9 upgrade causes errors in camel-salesforce and others

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-11808.
-
   Resolution: Fixed
 Assignee: Claus Ibsen
Fix Version/s: (was: 2.21.0)
   2.20.0

Okay we got it fixed now

> log4j2 2.9 upgrade causes errors in camel-salesforce and others
> ---
>
> Key: CAMEL-11808
> URL: https://issues.apache.org/jira/browse/CAMEL-11808
> Project: Camel
>  Issue Type: Task
>  Components: build system
>Affects Versions: 2.20.0
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.20.0
>
>
> [12:28:26]  davsclaus, master build fails with [ERROR] 
> Failed to execute goal 
> org.apache.maven.plugins:maven-plugin-plugin:3.4:helpmojo (help-goal) on 
> project camel-salesforce-maven-plugin: Execution help-goal of goal 
> org.apache.maven.plugins:maven-plugin-plugin:3.4:helpmojo failed. 
> IllegalArgumentException -> [Help 1]



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

[jira] [Updated] (CAMEL-11848) Using MongoDB Tailable Cursor Consumer on non-capped collection results in NullPointerException (instead of proper error message)

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-11848:

Fix Version/s: 2.20.0
   2.19.4

> Using MongoDB Tailable Cursor Consumer on non-capped collection results in 
> NullPointerException (instead of proper error message)
> -
>
> Key: CAMEL-11848
> URL: https://issues.apache.org/jira/browse/CAMEL-11848
> Project: Camel
>  Issue Type: Bug
>  Components: camel-mongodb, camel-mongodb3
>Affects Versions: 2.19.3
>Reporter: Frank Wein
>Priority: Minor
> Fix For: 2.19.4, 2.20.0
>
>
> When using the Camel MongoDB component with a tailable cursor consumer on a 
> non-capped collection, you get a NullPointerException (also see 
> http://camel.apache.org/mongodb.html#MongoDB-TailableCursorConsumer on this). 
> While using this feature on a non-capped collection is not supported, the 
> error message should be better (at the moment it only throws a 
> NullPointerException because the code tries to unbox a null in a Boolean 
> object). The code actually already has a better error message, but there is a 
> small logic flaw that prevents the error message from showing up. See 
> https://github.com/apache/camel/blob/camel-2.19.3/components/camel-mongodb/src/main/java/org/apache/camel/component/mongodb/MongoDbTailingProcess.java#L78
>  for the code.



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

[jira] [Updated] (CAMEL-11808) log4j2 2.9 upgrade causes errors in camel-salesforce and others

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-11808:

Affects Version/s: (was: 2.21.0)
   2.20.0

> log4j2 2.9 upgrade causes errors in camel-salesforce and others
> ---
>
> Key: CAMEL-11808
> URL: https://issues.apache.org/jira/browse/CAMEL-11808
> Project: Camel
>  Issue Type: Task
>  Components: build system
>Affects Versions: 2.20.0
>Reporter: Claus Ibsen
>Priority: Minor
> Fix For: 2.20.0
>
>
> [12:28:26]  davsclaus, master build fails with [ERROR] 
> Failed to execute goal 
> org.apache.maven.plugins:maven-plugin-plugin:3.4:helpmojo (help-goal) on 
> project camel-salesforce-maven-plugin: Execution help-goal of goal 
> org.apache.maven.plugins:maven-plugin-plugin:3.4:helpmojo failed. 
> IllegalArgumentException -> [Help 1]



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

[jira] [Commented] (CAMEL-11848) Using MongoDB Tailable Cursor Consumer on non-capped collection results in NullPointerException (instead of proper error message)

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-11848:
-

Mind there is 2 mongodb components with Camel so if they both has this problem 
you are welcome to fix them both.

> Using MongoDB Tailable Cursor Consumer on non-capped collection results in 
> NullPointerException (instead of proper error message)
> -
>
> Key: CAMEL-11848
> URL: https://issues.apache.org/jira/browse/CAMEL-11848
> Project: Camel
>  Issue Type: Bug
>  Components: camel-mongodb, camel-mongodb3
>Affects Versions: 2.19.3
>Reporter: Frank Wein
>Priority: Minor
>
> When using the Camel MongoDB component with a tailable cursor consumer on a 
> non-capped collection, you get a NullPointerException (also see 
> http://camel.apache.org/mongodb.html#MongoDB-TailableCursorConsumer on this). 
> While using this feature on a non-capped collection is not supported, the 
> error message should be better (at the moment it only throws a 
> NullPointerException because the code tries to unbox a null in a Boolean 
> object). The code actually already has a better error message, but there is a 
> small logic flaw that prevents the error message from showing up. See 
> https://github.com/apache/camel/blob/camel-2.19.3/components/camel-mongodb/src/main/java/org/apache/camel/component/mongodb/MongoDbTailingProcess.java#L78
>  for the code.



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

[jira] [Updated] (CAMEL-11848) Using MongoDB Tailable Cursor Consumer on non-capped collection results in NullPointerException (instead of proper error message)

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-11848:

Component/s: camel-mongodb3
 camel-mongodb

> Using MongoDB Tailable Cursor Consumer on non-capped collection results in 
> NullPointerException (instead of proper error message)
> -
>
> Key: CAMEL-11848
> URL: https://issues.apache.org/jira/browse/CAMEL-11848
> Project: Camel
>  Issue Type: Bug
>  Components: camel-mongodb, camel-mongodb3
>Affects Versions: 2.19.3
>Reporter: Frank Wein
>Priority: Minor
>
> When using the Camel MongoDB component with a tailable cursor consumer on a 
> non-capped collection, you get a NullPointerException (also see 
> http://camel.apache.org/mongodb.html#MongoDB-TailableCursorConsumer on this). 
> While using this feature on a non-capped collection is not supported, the 
> error message should be better (at the moment it only throws a 
> NullPointerException because the code tries to unbox a null in a Boolean 
> object). The code actually already has a better error message, but there is a 
> small logic flaw that prevents the error message from showing up. See 
> https://github.com/apache/camel/blob/camel-2.19.3/components/camel-mongodb/src/main/java/org/apache/camel/component/mongodb/MongoDbTailingProcess.java#L78
>  for the code.



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

[jira] [Updated] (CAMEL-11848) Using MongoDB Tailable Cursor Consumer on non-capped collection results in NullPointerException (instead of proper error message)

[Frank Wein (JIRA)]

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

Frank Wein updated CAMEL-11848:
---
Summary: Using MongoDB Tailable Cursor Consumer on non-capped collection 
results in NullPointerException (instead of proper error message)  (was: Using 
MongoDB Tailable Cursor Consumer on non-capped collection results in 
NullPointerException (except of proper error message))

> Using MongoDB Tailable Cursor Consumer on non-capped collection results in 
> NullPointerException (instead of proper error message)
> -
>
> Key: CAMEL-11848
> URL: https://issues.apache.org/jira/browse/CAMEL-11848
> Project: Camel
>  Issue Type: Bug
>Reporter: Frank Wein
>Priority: Minor
>
> When using the Camel MongoDB component with a tailable cursor consumer on a 
> non-capped collection, you get a NullPointerException (also see 
> http://camel.apache.org/mongodb.html#MongoDB-TailableCursorConsumer on this). 
> While using this feature on a non-capped collection is not supported, the 
> error message should be better (at the moment it only throws a 
> NullPointerException because the code tries to unbox a null in a Boolean 
> object). The code actually already has a better error message, but there is a 
> small logic flaw that prevents the error message from showing up. See 
> https://github.com/apache/camel/blob/camel-2.19.3/components/camel-mongodb/src/main/java/org/apache/camel/component/mongodb/MongoDbTailingProcess.java#L78
>  for the code.



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

[jira] [Created] (CAMEL-11848) Using MongoDB Tailable Cursor Consumer on non-capped collection results in NullPointerException (except of proper error message)

[Frank Wein (JIRA)]

Frank Wein created CAMEL-11848:
--

 Summary: Using MongoDB Tailable Cursor Consumer on non-capped 
collection results in NullPointerException (except of proper error message)
 Key: CAMEL-11848
 URL: https://issues.apache.org/jira/browse/CAMEL-11848
 Project: Camel
  Issue Type: Bug
Reporter: Frank Wein
Priority: Minor


When using the Camel MongoDB component with a tailable cursor consumer on a 
non-capped collection, you get a NullPointerException (also see 
http://camel.apache.org/mongodb.html#MongoDB-TailableCursorConsumer on this). 
While using this feature on a non-capped collection is not supported, the error 
message should be better (at the moment it only throws a NullPointerException 
because the code tries to unbox a null in a Boolean object). The code actually 
already has a better error message, but there is a small logic flaw that 
prevents the error message from showing up. See 
https://github.com/apache/camel/blob/camel-2.19.3/components/camel-mongodb/src/main/java/org/apache/camel/component/mongodb/MongoDbTailingProcess.java#L78
 for the code.



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