[jira] [Commented] (CAMEL-10458) Upgrade to Spring Boot 1.4.2

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-10458:
-

Also upgrade Spring Framework and Spring Integration as there is new version of 
those

> Upgrade to Spring Boot 1.4.2
> 
>
> Key: CAMEL-10458
> URL: https://issues.apache.org/jira/browse/CAMEL-10458
> Project: Camel
>  Issue Type: Task
>  Components: camel-spring-boot
>Affects Versions: 2.18.0
>Reporter: Claus Ibsen
> Fix For: 2.18.1, 2.19.0
>
>
> A new version is out
> https://spring.io/blog/2016/11/08/spring-boot-1-4-2-available-now



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-10458) Upgrade to Spring Boot 1.4.2

[Claus Ibsen (JIRA)]

Claus Ibsen created CAMEL-10458:
---

 Summary: Upgrade to Spring Boot 1.4.2
 Key: CAMEL-10458
 URL: https://issues.apache.org/jira/browse/CAMEL-10458
 Project: Camel
  Issue Type: Task
  Components: camel-spring-boot
Affects Versions: 2.18.0
Reporter: Claus Ibsen
 Fix For: 2.18.1, 2.19.0


A new version is out
https://spring.io/blog/2016/11/08/spring-boot-1-4-2-available-now



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-10457) Cannot generate javadoc for camel-jms-starter

[Claus Ibsen (JIRA)]

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

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

> Cannot generate javadoc for camel-jms-starter
> -
>
> Key: CAMEL-10457
> URL: https://issues.apache.org/jira/browse/CAMEL-10457
> Project: Camel
>  Issue Type: Task
>  Components: build system
>Affects Versions: 2.18.1
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
> Fix For: 2.18.1, 2.19.0
>
>
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 01:10 h
> [INFO] Finished at: 2016-11-08T18:29:26+00:00
> [INFO] Final Memory: 1469M/2777M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.3:jar (attach-javadocs) on 
> project camel-jms-starter: MavenReportException: Error while generating 
> Javadoc:
> [ERROR] Exit code: 1 - 
> /home/jenkins/jenkins-slave/workspace/Camel.2.18.x.notest/components-starter/camel-jms-starter/src/main/java/org/apache/camel/component/jms/springboot/JmsComponentConfiguration.java:1479:
>  error: unmappable character for encoding UTF-8
> [ERROR] * a route on the other queue will send it?s response directly back to
> [ERROR] ^
> [ERROR] 
> [ERROR] Command line was: 
> /usr/local/asfpackages/java/jdk1.8.0_102/jre/../bin/javadoc @options @packages
> [ERROR] 
> [ERROR] Refer to the generated Javadoc files in 
> '/home/jenkins/jenkins-slave/workspace/Camel.2.18.x.notest/components-starter/camel-jms-starter/target/apidocs'
>  dir.
> [ERROR] -> [Help 1]
> [ERROR] 
> From CI build #3
> https://builds.apache.org/job/Camel.2.18.x.notest/3/console



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-10457) Cannot generate javadoc for camel-jms-starter

[Claus Ibsen (JIRA)]

Claus Ibsen created CAMEL-10457:
---

 Summary: Cannot generate javadoc for camel-jms-starter
 Key: CAMEL-10457
 URL: https://issues.apache.org/jira/browse/CAMEL-10457
 Project: Camel
  Issue Type: Task
  Components: build system
Affects Versions: 2.18.1
Reporter: Claus Ibsen
 Fix For: 2.18.1, 2.19.0


[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 01:10 h
[INFO] Finished at: 2016-11-08T18:29:26+00:00
[INFO] Final Memory: 1469M/2777M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:2.10.3:jar (attach-javadocs) on 
project camel-jms-starter: MavenReportException: Error while generating Javadoc:
[ERROR] Exit code: 1 - 
/home/jenkins/jenkins-slave/workspace/Camel.2.18.x.notest/components-starter/camel-jms-starter/src/main/java/org/apache/camel/component/jms/springboot/JmsComponentConfiguration.java:1479:
 error: unmappable character for encoding UTF-8
[ERROR] * a route on the other queue will send it?s response directly back to
[ERROR] ^
[ERROR] 
[ERROR] Command line was: 
/usr/local/asfpackages/java/jdk1.8.0_102/jre/../bin/javadoc @options @packages
[ERROR] 
[ERROR] Refer to the generated Javadoc files in 
'/home/jenkins/jenkins-slave/workspace/Camel.2.18.x.notest/components-starter/camel-jms-starter/target/apidocs'
 dir.
[ERROR] -> [Help 1]
[ERROR] 

>From CI build #3
https://builds.apache.org/job/Camel.2.18.x.notest/3/console



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-10456) Camel leaks TCCL

[JIRA]

Christoph Läubrich created CAMEL-10456:
--

 Summary: Camel leaks TCCL
 Key: CAMEL-10456
 URL: https://issues.apache.org/jira/browse/CAMEL-10456
 Project: Camel
  Issue Type: Bug
  Components: camel-core
Reporter: Christoph Läubrich


Camel leaks ThreadContextClassLoader instances at least in the following place:

camel-core: 
https://github.com/apache/camel/blob/4f9448d83cc21a348f92cca961907b0f72d9db79/camel-core/src/main/java/org/apache/camel/util/ObjectHelper.java#L1913

As mentioned in the JavaDoc of Thread.getContextClassLoader() returning "null 
indicating the system class loader (or, failing that, the bootstrap class 
loader)", se same applies to Thread.setContextClassLoader(...)

The code only reset the TCCL if the returned value from 
Thread.currentThread().getContextClassLoader() was != null. So if in a thread 
without a TCCL set (and thus returning null) these methods set a new CCL but 
later do not reset these to the original null value.

This leads to Threads (e.g. when taking reused from a pool) having a 
classloader that will never gets reset and thus can't be garbage collected or 
even lead to strange behaviour because if other code that uses the 
TCCL-mechanism can try to load classes or resources from this loader later on.

I found that 
https://github.com/apache/camel/blob/master/components/camel-jms/src/main/java/org/apache/camel/component/jms/JmsProducer.java#L85
 uses a similar pattern, only resetting the TCCL if the *new* TCCL != null so 
maybe the code in ObjectHelper was meant to check for classloader != null 
instead of tccl !=null

The fix should also include making sure this pattern is not used in other 
camel-components or even to use the ObjectHelper Method consistently, currently 
it seems may components implement their owh TCCL-handling.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10451) camel-undertow - Add multipart request support

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-10451:


GitHub user igarashitm opened a pull request:

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

CAMEL-10451 camel-undertow - Add multipart request support



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

$ git pull https://github.com/igarashitm/camel CAMEL-10451

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

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


commit e77fcc244e7a28f0155ec459c6c70825cd904a77
Author: Tomohisa Igarashi 
Date:   2016-11-08T16:29:53Z

CAMEL-10451 camel-undertow - Add multipart request support




> camel-undertow - Add multipart request support
> --
>
> Key: CAMEL-10451
> URL: https://issues.apache.org/jira/browse/CAMEL-10451
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-undertow
>Reporter: Tomohisa Igarashi
>Assignee: Tomohisa Igarashi
>
> undertow consumer should handle multipart request, the file parts should be 
> mapped into attachment like camel-jetty is doing. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-10455) camel-chronicle - has SNAPSHOT dependency

[Claus Ibsen (JIRA)]

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

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

> camel-chronicle - has SNAPSHOT dependency
> -
>
> Key: CAMEL-10455
> URL: https://issues.apache.org/jira/browse/CAMEL-10455
> Project: Camel
>  Issue Type: Bug
>  Components: camel-chronicle
>Affects Versions: 2.18.1
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
> Fix For: 2.18.1, 2.19.0
>
>
> Cannot build 2.18.x branch due
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 17:28 min
> [INFO] Finished at: 2016-11-08T15:36:48+00:00
> [INFO] Final Memory: 1188M/2645M
> [INFO] 
> 
> [ERROR] Failed to execute goal on project camel-chronicle: Could not resolve 
> dependencies for project 
> org.apache.camel:camel-chronicle:jar:2.18.1-SNAPSHOT: Failed to collect 
> dependencies at net.openhft:chronicle-engine:jar:1.13.10 -> 
> net.openhft:chronicle-network:jar:1.7.2 -> 
> net.openhft:chronicle-wire:jar:1.7.15 -> 
> net.openhft:chronicle-bytes:jar:1.7.18: Failed to read artifact descriptor 
> for net.openhft:chronicle-bytes:jar:1.7.18: Failure to find 
> net.openhft:chronicle-bom:pom:1.13.30-SNAPSHOT in 
> http://repository.apache.org/snapshots was cached in the local repository, 
> resolution will not be reattempted until the update interval of Nexus has 
> elapsed or updates are forced -> [Help 1]
> Sadly there is indeed SNAPSHOT in that pom.xml file. So we need to revert 
> back to older working version.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-10438) Java8 DSL for Content Enricher and Aggregator

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli updated CAMEL-10438:

Fix Version/s: 2.18.1

> Java8 DSL for Content Enricher and Aggregator
> -
>
> Key: CAMEL-10438
> URL: https://issues.apache.org/jira/browse/CAMEL-10438
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.18.1, 2.19.0
>
>
> See mailing list discussion:
> https://lists.apache.org/thread.html/e3375b07c8aa06ccae33b1e74bab2328a0cf4b5ac95621fc9fa0c848@%3Cdev.camel.apache.org%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10455) camel-chronicle - has SNAPSHOT dependency

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino commented on CAMEL-10455:
--

It's true:

http://search.maven.org/#artifactdetails%7Cnet.openhft%7Cchronicle-bytes%7C1.7.18%7Cbundle

What is weird is that 1.13.32 has been released..

> camel-chronicle - has SNAPSHOT dependency
> -
>
> Key: CAMEL-10455
> URL: https://issues.apache.org/jira/browse/CAMEL-10455
> Project: Camel
>  Issue Type: Bug
>  Components: camel-chronicle
>Affects Versions: 2.18.1
>Reporter: Claus Ibsen
> Fix For: 2.18.1, 2.19.0
>
>
> Cannot build 2.18.x branch due
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 17:28 min
> [INFO] Finished at: 2016-11-08T15:36:48+00:00
> [INFO] Final Memory: 1188M/2645M
> [INFO] 
> 
> [ERROR] Failed to execute goal on project camel-chronicle: Could not resolve 
> dependencies for project 
> org.apache.camel:camel-chronicle:jar:2.18.1-SNAPSHOT: Failed to collect 
> dependencies at net.openhft:chronicle-engine:jar:1.13.10 -> 
> net.openhft:chronicle-network:jar:1.7.2 -> 
> net.openhft:chronicle-wire:jar:1.7.15 -> 
> net.openhft:chronicle-bytes:jar:1.7.18: Failed to read artifact descriptor 
> for net.openhft:chronicle-bytes:jar:1.7.18: Failure to find 
> net.openhft:chronicle-bom:pom:1.13.30-SNAPSHOT in 
> http://repository.apache.org/snapshots was cached in the local repository, 
> resolution will not be reattempted until the update interval of Nexus has 
> elapsed or updates are forced -> [Help 1]
> Sadly there is indeed SNAPSHOT in that pom.xml file. So we need to revert 
> back to older working version.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10455) camel-chronicle - has SNAPSHOT dependency

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-10455:
-

A CI job builds 2.18.x branch which will fail if there is still problem
https://builds.apache.org/view/A-D/view/Camel/job/Camel.2.18.x.notest/3/

> camel-chronicle - has SNAPSHOT dependency
> -
>
> Key: CAMEL-10455
> URL: https://issues.apache.org/jira/browse/CAMEL-10455
> Project: Camel
>  Issue Type: Bug
>  Components: camel-chronicle
>Affects Versions: 2.18.1
>Reporter: Claus Ibsen
> Fix For: 2.18.1, 2.19.0
>
>
> Cannot build 2.18.x branch due
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 17:28 min
> [INFO] Finished at: 2016-11-08T15:36:48+00:00
> [INFO] Final Memory: 1188M/2645M
> [INFO] 
> 
> [ERROR] Failed to execute goal on project camel-chronicle: Could not resolve 
> dependencies for project 
> org.apache.camel:camel-chronicle:jar:2.18.1-SNAPSHOT: Failed to collect 
> dependencies at net.openhft:chronicle-engine:jar:1.13.10 -> 
> net.openhft:chronicle-network:jar:1.7.2 -> 
> net.openhft:chronicle-wire:jar:1.7.15 -> 
> net.openhft:chronicle-bytes:jar:1.7.18: Failed to read artifact descriptor 
> for net.openhft:chronicle-bytes:jar:1.7.18: Failure to find 
> net.openhft:chronicle-bom:pom:1.13.30-SNAPSHOT in 
> http://repository.apache.org/snapshots was cached in the local repository, 
> resolution will not be reattempted until the update interval of Nexus has 
> elapsed or updates are forced -> [Help 1]
> Sadly there is indeed SNAPSHOT in that pom.xml file. So we need to revert 
> back to older working version.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10455) camel-chronicle - has SNAPSHOT dependency

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli commented on CAMEL-10455:
-

Would you like me to have a look ?

> camel-chronicle - has SNAPSHOT dependency
> -
>
> Key: CAMEL-10455
> URL: https://issues.apache.org/jira/browse/CAMEL-10455
> Project: Camel
>  Issue Type: Bug
>  Components: camel-chronicle
>Affects Versions: 2.18.1
>Reporter: Claus Ibsen
> Fix For: 2.18.1, 2.19.0
>
>
> Cannot build 2.18.x branch due
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 17:28 min
> [INFO] Finished at: 2016-11-08T15:36:48+00:00
> [INFO] Final Memory: 1188M/2645M
> [INFO] 
> 
> [ERROR] Failed to execute goal on project camel-chronicle: Could not resolve 
> dependencies for project 
> org.apache.camel:camel-chronicle:jar:2.18.1-SNAPSHOT: Failed to collect 
> dependencies at net.openhft:chronicle-engine:jar:1.13.10 -> 
> net.openhft:chronicle-network:jar:1.7.2 -> 
> net.openhft:chronicle-wire:jar:1.7.15 -> 
> net.openhft:chronicle-bytes:jar:1.7.18: Failed to read artifact descriptor 
> for net.openhft:chronicle-bytes:jar:1.7.18: Failure to find 
> net.openhft:chronicle-bom:pom:1.13.30-SNAPSHOT in 
> http://repository.apache.org/snapshots was cached in the local repository, 
> resolution will not be reattempted until the update interval of Nexus has 
> elapsed or updates are forced -> [Help 1]
> Sadly there is indeed SNAPSHOT in that pom.xml file. So we need to revert 
> back to older working version.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10455) camel-chronicle - has SNAPSHOT dependency

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-10455:
-

Ah darn this library breaks its api in patch releases - we should consider 
removing it until it works!

> camel-chronicle - has SNAPSHOT dependency
> -
>
> Key: CAMEL-10455
> URL: https://issues.apache.org/jira/browse/CAMEL-10455
> Project: Camel
>  Issue Type: Bug
>  Components: camel-chronicle
>Affects Versions: 2.18.1
>Reporter: Claus Ibsen
> Fix For: 2.18.1, 2.19.0
>
>
> Cannot build 2.18.x branch due
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 17:28 min
> [INFO] Finished at: 2016-11-08T15:36:48+00:00
> [INFO] Final Memory: 1188M/2645M
> [INFO] 
> 
> [ERROR] Failed to execute goal on project camel-chronicle: Could not resolve 
> dependencies for project 
> org.apache.camel:camel-chronicle:jar:2.18.1-SNAPSHOT: Failed to collect 
> dependencies at net.openhft:chronicle-engine:jar:1.13.10 -> 
> net.openhft:chronicle-network:jar:1.7.2 -> 
> net.openhft:chronicle-wire:jar:1.7.15 -> 
> net.openhft:chronicle-bytes:jar:1.7.18: Failed to read artifact descriptor 
> for net.openhft:chronicle-bytes:jar:1.7.18: Failure to find 
> net.openhft:chronicle-bom:pom:1.13.30-SNAPSHOT in 
> http://repository.apache.org/snapshots was cached in the local repository, 
> resolution will not be reattempted until the update interval of Nexus has 
> elapsed or updates are forced -> [Help 1]
> Sadly there is indeed SNAPSHOT in that pom.xml file. So we need to revert 
> back to older working version.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-10455) camel-chronicle - has SNAPSHOT dependency

[Claus Ibsen (JIRA)]

Claus Ibsen created CAMEL-10455:
---

 Summary: camel-chronicle - has SNAPSHOT dependency
 Key: CAMEL-10455
 URL: https://issues.apache.org/jira/browse/CAMEL-10455
 Project: Camel
  Issue Type: Bug
  Components: camel-chronicle
Affects Versions: 2.18.1
Reporter: Claus Ibsen
 Fix For: 2.18.1, 2.19.0


Cannot build 2.18.x branch due

[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 17:28 min
[INFO] Finished at: 2016-11-08T15:36:48+00:00
[INFO] Final Memory: 1188M/2645M
[INFO] 
[ERROR] Failed to execute goal on project camel-chronicle: Could not resolve 
dependencies for project org.apache.camel:camel-chronicle:jar:2.18.1-SNAPSHOT: 
Failed to collect dependencies at net.openhft:chronicle-engine:jar:1.13.10 -> 
net.openhft:chronicle-network:jar:1.7.2 -> 
net.openhft:chronicle-wire:jar:1.7.15 -> 
net.openhft:chronicle-bytes:jar:1.7.18: Failed to read artifact descriptor for 
net.openhft:chronicle-bytes:jar:1.7.18: Failure to find 
net.openhft:chronicle-bom:pom:1.13.30-SNAPSHOT in 
http://repository.apache.org/snapshots was cached in the local repository, 
resolution will not be reattempted until the update interval of Nexus has 
elapsed or updates are forced -> [Help 1]

Sadly there is indeed SNAPSHOT in that pom.xml file. So we need to revert back 
to older working version.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10438) Java8 DSL for Content Enricher and Aggregator

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli commented on CAMEL-10438:
-

Yep that is my goal too so as today the Java DSL only adds some syntax sugar 
you can easily implement in XML via i.e. bean refs in a very similar way. I 
think we should try to consolidate a little bit the APIs once the Java8 DSL get 
stable enough so we may remove some redundant stuffs.

 


> Java8 DSL for Content Enricher and Aggregator
> -
>
> Key: CAMEL-10438
> URL: https://issues.apache.org/jira/browse/CAMEL-10438
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.19.0
>
>
> See mailing list discussion:
> https://lists.apache.org/thread.html/e3375b07c8aa06ccae33b1e74bab2328a0cf4b5ac95621fc9fa0c848@%3Cdev.camel.apache.org%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-10453) camel-elsql does not set CamelSqlUpdateCount header on update operation

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-10453:

Fix Version/s: 2.19.0
   2.18.1

> camel-elsql does not set CamelSqlUpdateCount header on update operation
> ---
>
> Key: CAMEL-10453
> URL: https://issues.apache.org/jira/browse/CAMEL-10453
> Project: Camel
>  Issue Type: Bug
>  Components: camel-elsql
>Affects Versions: 2.18.0
>Reporter: Tomas Turek
> Fix For: 2.18.1, 2.19.0
>
>
> Camel ElSql should store number of rows updated for update operation into 
> CamelSqlUpdateCount header.
> Route:
> {code}
> 
>   
>   
>   
> 
> {code}
> ElSQL
> {code}
> @NAME(updateLicense)
> UPDATE projects
> SET license = :lic
> WHERE id = :id
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10453) camel-elsql does not set CamelSqlUpdateCount header on update operation

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-10453:
-

Thanks are you working on a PR

> camel-elsql does not set CamelSqlUpdateCount header on update operation
> ---
>
> Key: CAMEL-10453
> URL: https://issues.apache.org/jira/browse/CAMEL-10453
> Project: Camel
>  Issue Type: Bug
>  Components: camel-elsql
>Affects Versions: 2.18.0
>Reporter: Tomas Turek
> Fix For: 2.18.1, 2.19.0
>
>
> Camel ElSql should store number of rows updated for update operation into 
> CamelSqlUpdateCount header.
> Route:
> {code}
> 
>   
>   
>   
> 
> {code}
> ElSQL
> {code}
> @NAME(updateLicense)
> UPDATE projects
> SET license = :lic
> WHERE id = :id
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10453) camel-elsql does not set CamelSqlUpdateCount header on update operation

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-10453:
-

Also mind camel-elsql reuses camel-sql so maybe there is something wrong there 
too?

> camel-elsql does not set CamelSqlUpdateCount header on update operation
> ---
>
> Key: CAMEL-10453
> URL: https://issues.apache.org/jira/browse/CAMEL-10453
> Project: Camel
>  Issue Type: Bug
>  Components: camel-elsql
>Affects Versions: 2.18.0
>Reporter: Tomas Turek
> Fix For: 2.18.1, 2.19.0
>
>
> Camel ElSql should store number of rows updated for update operation into 
> CamelSqlUpdateCount header.
> Route:
> {code}
> 
>   
>   
>   
> 
> {code}
> ElSQL
> {code}
> @NAME(updateLicense)
> UPDATE projects
> SET license = :lic
> WHERE id = :id
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10438) Java8 DSL for Content Enricher and Aggregator

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-10438:
-

Yeah I think if we backport it we can get more community feedback.
Just mind that we have to state in the javadoc of these new methods its 
experimental.

One issue we have to find out is to ensure the Java 8 DSL dont come too far 
from what you can do with XML DSL. The power of Camel is that the Java and XML 
DSL are similar and you can do all in both of them.

And we should also ensure backwards compatibility - we cannot just throw out 
the old Java DSL for Java 8. At least not on 2.x. Even for 3.x I would like to 
see existing apps that can easily be migrated to Camel 3.x.

But its best to get as much feedback from the community.

Good job on this new Java 8 DSL.

> Java8 DSL for Content Enricher and Aggregator
> -
>
> Key: CAMEL-10438
> URL: https://issues.apache.org/jira/browse/CAMEL-10438
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.19.0
>
>
> See mailing list discussion:
> https://lists.apache.org/thread.html/e3375b07c8aa06ccae33b1e74bab2328a0cf4b5ac95621fc9fa0c848@%3Cdev.camel.apache.org%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10438) Java8 DSL for Content Enricher and Aggregator

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-10438:
-

Yeah I think if we backport it we can get more community feedback.
Just mind that we have to state in the javadoc of these new methods its 
experimental.

One issue we have to find out is to ensure the Java 8 DSL dont come too far 
from what you can do with XML DSL. The power of Camel is that the Java and XML 
DSL are similar and you can do all in both of them.

And we should also ensure backwards compatibility - we cannot just throw out 
the old Java DSL for Java 8. At least not on 2.x. Even for 3.x I would like to 
see existing apps that can easily be migrated to Camel 3.x.

But its best to get as much feedback from the community.

Good job on this new Java 8 DSL.

> Java8 DSL for Content Enricher and Aggregator
> -
>
> Key: CAMEL-10438
> URL: https://issues.apache.org/jira/browse/CAMEL-10438
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.19.0
>
>
> See mailing list discussion:
> https://lists.apache.org/thread.html/e3375b07c8aa06ccae33b1e74bab2328a0cf4b5ac95621fc9fa0c848@%3Cdev.camel.apache.org%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Issue Comment Deleted] (CAMEL-10438) Java8 DSL for Content Enricher and Aggregator

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-10438:

Comment: was deleted

(was: Yeah I think if we backport it we can get more community feedback.
Just mind that we have to state in the javadoc of these new methods its 
experimental.

One issue we have to find out is to ensure the Java 8 DSL dont come too far 
from what you can do with XML DSL. The power of Camel is that the Java and XML 
DSL are similar and you can do all in both of them.

And we should also ensure backwards compatibility - we cannot just throw out 
the old Java DSL for Java 8. At least not on 2.x. Even for 3.x I would like to 
see existing apps that can easily be migrated to Camel 3.x.

But its best to get as much feedback from the community.

Good job on this new Java 8 DSL.)

> Java8 DSL for Content Enricher and Aggregator
> -
>
> Key: CAMEL-10438
> URL: https://issues.apache.org/jira/browse/CAMEL-10438
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.19.0
>
>
> See mailing list discussion:
> https://lists.apache.org/thread.html/e3375b07c8aa06ccae33b1e74bab2328a0cf4b5ac95621fc9fa0c848@%3Cdev.camel.apache.org%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-10454) Unclear piece in IdempotentConsumer.java

[Boris Treukhov (JIRA)]

Boris Treukhov created CAMEL-10454:
--

 Summary: Unclear piece in IdempotentConsumer.java
 Key: CAMEL-10454
 URL: https://issues.apache.org/jira/browse/CAMEL-10454
 Project: Camel
  Issue Type: Improvement
  Components: camel-core
Reporter: Boris Treukhov
Priority: Minor


Current implementation of IdempotentConsumer.java has very strange check on 
whether IdempotentRepository contains the key - if it's 
ExchangeIdempotentRepository then the result of "contains()" check is not 
inverted(i.e. there is no NOT operator), while for other types of 
IdempotentRepository it IS inverted with "!".

 // check if we already have the key
if (idempotentRepository instanceof 
ExchangeIdempotentRepository) {
newKey = ((ExchangeIdempotentRepository) 
idempotentRepository).contains(exchange, messageId);
} else {
newKey = !idempotentRepository.contains(messageId);
}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-10453) camel-elsql does not set CamelSqlUpdateCount header on update operation

[Tomas Turek (JIRA)]

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

Tomas Turek updated CAMEL-10453:

Description: 
Camel ElSql should store number of rows updated for update operation into 
CamelSqlUpdateCount header.

Route:
{code}

  
  
  

{code}

ElSQL
{code}
@NAME(updateLicense)
UPDATE projects
SET license = :lic
WHERE id = :id
{code}

> camel-elsql does not set CamelSqlUpdateCount header on update operation
> ---
>
> Key: CAMEL-10453
> URL: https://issues.apache.org/jira/browse/CAMEL-10453
> Project: Camel
>  Issue Type: Bug
>  Components: camel-elsql
>Affects Versions: 2.18.0
>Reporter: Tomas Turek
>
> Camel ElSql should store number of rows updated for update operation into 
> CamelSqlUpdateCount header.
> Route:
> {code}
> 
>   
>   
>   
> 
> {code}
> ElSQL
> {code}
> @NAME(updateLicense)
> UPDATE projects
> SET license = :lic
> WHERE id = :id
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-10453) camel-elsql does not set CamelSqlUpdateCount header on update operation

[Tomas Turek (JIRA)]

Tomas Turek created CAMEL-10453:
---

 Summary: camel-elsql does not set CamelSqlUpdateCount header on 
update operation
 Key: CAMEL-10453
 URL: https://issues.apache.org/jira/browse/CAMEL-10453
 Project: Camel
  Issue Type: Bug
  Components: camel-elsql
Affects Versions: 2.18.0
Reporter: Tomas Turek






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-10452) camel-salesforce: Add an option to simulate SELECT * from

[Luca Burgazzoli (JIRA)]

Luca Burgazzoli created CAMEL-10452:
---

 Summary: camel-salesforce: Add an option to simulate SELECT * from
 Key: CAMEL-10452
 URL: https://issues.apache.org/jira/browse/CAMEL-10452
 Project: Camel
  Issue Type: Improvement
  Components: camel-salesforce
Reporter: Luca Burgazzoli
Priority: Minor
 Fix For: 2.19.0


As today it is not possible to run a query like SELECT * from but one is forced 
to list all the field he want.

It would be nice to auto generate a statement using SObject meta data so one 
can write:

from("salesforce:stream?SObjectName=Case=true")

to get all the fields the SObjectName supports.

[~dhirajsb] what do you think ?




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (CAMEL-10186) camel-spring-boot - Add auto-configuration to components without properties

[Nicola Ferraro (JIRA)]

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

Nicola Ferraro closed CAMEL-10186.
--
Resolution: Fixed

> camel-spring-boot - Add auto-configuration to components without properties
> ---
>
> Key: CAMEL-10186
> URL: https://issues.apache.org/jira/browse/CAMEL-10186
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-spring-boot
>Reporter: Nicola Ferraro
>Assignee: Nicola Ferraro
>Priority: Minor
> Fix For: 2.19.0
>
>
> The new tooling improvements provided by CAMEL-9419 also added spring-boot 
> auto configuration for many components.
> But components without configuration properties (all components that are 
> configurable at endpoint level only, eg. _exec_) do not have this feature.
> I think it would be useful to add auto-configuration to all modules left 
> behind.
> I can work on this feature.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-10451) camel-undertow - Add multipart request support

[Tomohisa Igarashi (JIRA)]

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

Tomohisa Igarashi updated CAMEL-10451:
--
Summary: camel-undertow - Add multipart request support  (was: 
camel-undertow - Add multipart support)

> camel-undertow - Add multipart request support
> --
>
> Key: CAMEL-10451
> URL: https://issues.apache.org/jira/browse/CAMEL-10451
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-undertow
>Reporter: Tomohisa Igarashi
>Assignee: Tomohisa Igarashi
>
> undertow consumer should handle multipart request, the file parts should be 
> mapped into attachment like camel-jetty is doing. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-10451) camel-undertow - Add multipart support

[Tomohisa Igarashi (JIRA)]

Tomohisa Igarashi created CAMEL-10451:
-

 Summary: camel-undertow - Add multipart support
 Key: CAMEL-10451
 URL: https://issues.apache.org/jira/browse/CAMEL-10451
 Project: Camel
  Issue Type: Improvement
  Components: camel-undertow
Reporter: Tomohisa Igarashi
Assignee: Tomohisa Igarashi


undertow consumer should handle multipart request, the file parts should be 
mapped into attachment like camel-jetty is doing. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-10438) Java8 DSL for Content Enricher and Aggregator

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli resolved CAMEL-10438.
-
Resolution: Fixed

[~davsclaus] should this be back-ported to 2.18.x ?

> Java8 DSL for Content Enricher and Aggregator
> -
>
> Key: CAMEL-10438
> URL: https://issues.apache.org/jira/browse/CAMEL-10438
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.19.0
>
>
> See mailing list discussion:
> https://lists.apache.org/thread.html/e3375b07c8aa06ccae33b1e74bab2328a0cf4b5ac95621fc9fa0c848@%3Cdev.camel.apache.org%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9597) camel-nagios - Mockito for testing

[Kevin Earls (JIRA)]

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

Kevin Earls commented on CAMEL-9597:


I've started working on a fix for this.


> camel-nagios - Mockito for testing
> --
>
> Key: CAMEL-9597
> URL: https://issues.apache.org/jira/browse/CAMEL-9597
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-nagios
>Reporter: Claus Ibsen
>Priority: Minor
> Fix For: Future
>
>
> the test jar it uses for jsendnca is downloaded from jboss nexus maven. We 
> should consider mocking the unit tests so we can drop the test jar, and then 
> just the jar from maven central so we can drop the 3rd party repo.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-10344) RouteIdFactory - That can assign route ids using derived values from uris

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-10344:

Fix Version/s: (was: Future)
   2.19.0

> RouteIdFactory - That can assign route ids using derived values from uris
> -
>
> Key: CAMEL-10344
> URL: https://issues.apache.org/jira/browse/CAMEL-10344
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-core
>Reporter: Claus Ibsen
>Priority: Minor
> Fix For: 2.19.0
>
>
> When using routes that uses direct/seda etc as route inputs, then you may 
> want to use their name as the route id, eg
> direct:foo   -> foo
> seda:bar-> bar
> jms:orders -> orders
> Instead of having route1, route2 as auto assigned names. 
> There could be a NodeIdFactory that assign such names for route's. For 
> example it can use the context-path of the route url as the name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10344) RouteIdFactory - That can assign route ids using derived values from uris

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-10344:
-

We also would need an unit test where some of the routes have explicit assigned 
id with .routeId("myRoute"), which this factory should not override.

> RouteIdFactory - That can assign route ids using derived values from uris
> -
>
> Key: CAMEL-10344
> URL: https://issues.apache.org/jira/browse/CAMEL-10344
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-core
>Reporter: Claus Ibsen
>Priority: Minor
> Fix For: Future
>
>
> When using routes that uses direct/seda etc as route inputs, then you may 
> want to use their name as the route id, eg
> direct:foo   -> foo
> seda:bar-> bar
> jms:orders -> orders
> Instead of having route1, route2 as auto assigned names. 
> There could be a NodeIdFactory that assign such names for route's. For 
> example it can use the context-path of the route url as the name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10344) RouteIdFactory - That can assign route ids using derived values from uris

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-10344:
-

For the rest routes we may want to replace / with - in the name, so it 
preserves the full path and the verb.

rest foo
get 
post

then its 2 routes with id

get-foo
post-foo
Also if there is nested paths we preserve the full name

rest foo
get bar 
post bar

then its

get-foo-bar
post-foo-bar
And we would need some unit tests for rest-dsl routes.

> RouteIdFactory - That can assign route ids using derived values from uris
> -
>
> Key: CAMEL-10344
> URL: https://issues.apache.org/jira/browse/CAMEL-10344
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-core
>Reporter: Claus Ibsen
>Priority: Minor
> Fix For: Future
>
>
> When using routes that uses direct/seda etc as route inputs, then you may 
> want to use their name as the route id, eg
> direct:foo   -> foo
> seda:bar-> bar
> jms:orders -> orders
> Instead of having route1, route2 as auto assigned names. 
> There could be a NodeIdFactory that assign such names for route's. For 
> example it can use the context-path of the route url as the name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10344) RouteIdFactory - That can assign route ids using derived values from uris

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-10344:


Github user asfgit closed the pull request at:

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


> RouteIdFactory - That can assign route ids using derived values from uris
> -
>
> Key: CAMEL-10344
> URL: https://issues.apache.org/jira/browse/CAMEL-10344
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-core
>Reporter: Claus Ibsen
>Priority: Minor
> Fix For: Future
>
>
> When using routes that uses direct/seda etc as route inputs, then you may 
> want to use their name as the route id, eg
> direct:foo   -> foo
> seda:bar-> bar
> jms:orders -> orders
> Instead of having route1, route2 as auto assigned names. 
> There could be a NodeIdFactory that assign such names for route's. For 
> example it can use the context-path of the route url as the name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)