[jira] [Work started] (CAMEL-11953) maven connector plugin: connector only properties are ignored in spring boot code generation

2017-10-26 Thread Luca Burgazzoli (JIRA) 

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

Work on CAMEL-11953 started by Luca Burgazzoli.
---
> maven connector plugin: connector only properties are ignored in spring boot 
> code generation
> 
>
> Key: CAMEL-11953
> URL: https://issues.apache.org/jira/browse/CAMEL-11953
> Project: Camel
>  Issue Type: Bug
>  Components: camel-connector
>Affects Versions: 2.20.0
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.20.1, 2.21.0
>
>




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

[jira] [Created] (CAMEL-11953) maven connector plugin: connector only properties are ignored in spring boot code generation

2017-10-26 Thread Luca Burgazzoli (JIRA) 
Luca Burgazzoli created CAMEL-11953:
---

 Summary: maven connector plugin: connector only properties are 
ignored in spring boot code generation
 Key: CAMEL-11953
 URL: https://issues.apache.org/jira/browse/CAMEL-11953
 Project: Camel
  Issue Type: Bug
  Components: camel-connector
Affects Versions: 2.20.0
Reporter: Luca Burgazzoli
Assignee: Luca Burgazzoli
Priority: Minor
 Fix For: 2.20.1, 2.21.0






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

[jira] [Created] (CAMEL-11952) XSLT options not set when resource URI is http

2017-10-26 Thread Tyler Flaherty (JIRA) 
Tyler Flaherty created CAMEL-11952:
--

 Summary: XSLT options not set when resource URI is http
 Key: CAMEL-11952
 URL: https://issues.apache.org/jira/browse/CAMEL-11952
 Project: Camel
  Issue Type: Bug
  Components: camel-core
Affects Versions: 2.20.0
Reporter: Tyler Flaherty
Priority: Minor


Options included for an XSLT endpoint URI are not applied if the resource is 
referenced via HTTP. 

In XsltComponent.createEndpoint(), it checks if the resource URI is http 
(XsltComponent:179). If it is, ResourceHelper.appendParameters() is called 
(XsltComponent:180).

ResourceHelper.appendParameters() adds the parameters to the HTTP URI and then 
clears the parameters list (ResourceHelper:336). 

By the time setProperties() is called on line 207 of XsltComponent, the 
parameters map is empty and nothing gets set.



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

[jira] [Created] (CAMEL-11951) Uri matching does not match request type

2017-10-26 Thread Robert Hillier (JIRA) 
Robert Hillier created CAMEL-11951:
--

 Summary: Uri matching does not match request type
 Key: CAMEL-11951
 URL: https://issues.apache.org/jira/browse/CAMEL-11951
 Project: Camel
  Issue Type: Bug
  Components: camel-http-common
Affects Versions: 2.20.0
 Environment: camel-spring, camel-jetty
OS - RHEL
Reporter: Robert Hillier


I had previously described the problem here:
https://stackoverflow.com/questions/46936348/apache-camel-rest-dsl-405-method-not-allowed

It appears that the problem is down to a possible bug in the way URIs are 
matched (not to mention my rather obscure use-case)

I have a number of REST-DSL endpoints with the same URI but different request 
types (POST, PUT, GET, DELETE).  In my case, the URI is getting selected by
HttpServletResolveConsumerStrategy.resolve (in addition to these, I have some 
specific endpoints with wildcards in them)

This method matches the URI, but not the request type.  When I send a GET 
request, it returns the first consumer candidate it finds which, in my case, 
always seems to be PUT.  Later, when CamelContinuationServlet.doService checks 
that the request type and cadidate type match, they don't.  It then returns 405 
Method Not Allowed.

I believe that the HttpServletResolveConsumerStrategy.resolve method IN 
camel-hhtp-common should check the request type as well as the URI.



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

[jira] [Updated] (CAMEL-11950) Inconsistent jar versions with apache curator

2017-10-26 Thread Thomas Diesler (JIRA) 

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

Thomas Diesler updated CAMEL-11950:
---
Description: CrossRef: 
https://github.com/wildfly-extras/wildfly-camel/issues/2243

> Inconsistent jar versions with apache curator
> -
>
> Key: CAMEL-11950
> URL: https://issues.apache.org/jira/browse/CAMEL-11950
> Project: Camel
>  Issue Type: Bug
>  Components: camel-zookeeper
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
> Fix For: 2.20.1
>
>
> CrossRef: https://github.com/wildfly-extras/wildfly-camel/issues/2243



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

[jira] [Commented] (CAMEL-11950) Inconsistent jar versions with apache curator

2017-10-26 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CAMEL-11950:


oscerd commented on issue #2063: [CAMEL-11950] Inconsistent jar versions with 
apache curator
URL: https://github.com/apache/camel/pull/2063#issuecomment-339732540
 
 
   I'll merge tomorrow


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Inconsistent jar versions with apache curator
> -
>
> Key: CAMEL-11950
> URL: https://issues.apache.org/jira/browse/CAMEL-11950
> Project: Camel
>  Issue Type: Bug
>  Components: camel-zookeeper
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
> Fix For: 2.20.1
>
>




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

[jira] [Commented] (CAMEL-11950) Inconsistent jar versions with apache curator

2017-10-26 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CAMEL-11950:


GitHub user tdiesler opened a pull request:

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

[CAMEL-11950] Inconsistent jar versions with apache curator



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

$ git pull https://github.com/tdiesler/camel CAMEL-11950

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

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


commit e5cf6131ea79b4ee5b9c17bbaa6ec6d1830334d5
Author: Thomas Diesler 
Date:   2017-10-26T16:58:10Z

[CAMEL-11950] Inconsistent jar versions with apache curator




> Inconsistent jar versions with apache curator
> -
>
> Key: CAMEL-11950
> URL: https://issues.apache.org/jira/browse/CAMEL-11950
> Project: Camel
>  Issue Type: Bug
>  Components: camel-zookeeper
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
> Fix For: 2.20.1
>
>




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

[jira] [Commented] (CAMEL-11950) Inconsistent jar versions with apache curator

2017-10-26 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CAMEL-11950:


tdiesler opened a new pull request #2063: [CAMEL-11950] Inconsistent jar 
versions with apache curator
URL: https://github.com/apache/camel/pull/2063
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Inconsistent jar versions with apache curator
> -
>
> Key: CAMEL-11950
> URL: https://issues.apache.org/jira/browse/CAMEL-11950
> Project: Camel
>  Issue Type: Bug
>  Components: camel-zookeeper
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
> Fix For: 2.20.1
>
>




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

[jira] [Created] (CAMEL-11950) Inconsistent jar versions with apache curator

2017-10-26 Thread Thomas Diesler (JIRA) 
Thomas Diesler created CAMEL-11950:
--

 Summary: Inconsistent jar versions with apache curator
 Key: CAMEL-11950
 URL: https://issues.apache.org/jira/browse/CAMEL-11950
 Project: Camel
  Issue Type: Bug
  Components: camel-zookeeper
Reporter: Thomas Diesler
Assignee: Thomas Diesler
 Fix For: 2.20.1






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

[jira] [Commented] (CAMEL-11292) support for Scala 2.12.x

2017-10-26 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CAMEL-11292:


sinwe commented on issue #2060: CAMEL-11292: Upgrade to scala 2.12.x
URL: https://github.com/apache/camel/pull/2060#issuecomment-339687982
 
 
   And here is what I got
   
   ```
   [INFO] Results:  


   
   [INFO]   


   
   [ERROR] Errors:  


   
   [ERROR] 
org.apache.camel.model.ModelSanityCheckerTest.testSanity(org.apache.camel.model.ModelSanityCheckerTest)


 
   [ERROR]   Run 1: ModelSanityCheckerTest.testSanity:83 » NoSuchMethod 
org.apache.camel.model.dat...   

   
   [ERROR]   Run 2: ModelSanityCheckerTest.testSanity:83 » NoSuchMethod 
org.apache.camel.model.dat...   

   
   [ERROR]   Run 3: ModelSanityCheckerTest.testSanity:83 » NoSuchMethod 
org.apache.camel.model.dat...   

   
   [INFO]   


   
   [WARNING] Flakes:  
   [WARNING] 
org.apache.camel.component.dataset.CustomDataSetTest.testUsingCustomDataSet(org.apache.camel.component.dataset.CustomDataSetTest)
   [ERROR]   Run 1: 
CustomDataSetTest>TestSupport.runBare:58->testUsingCustomDataSet:54->ContextTestSupport.assertMockEndpointsSatisfied:352
 dataset://foo?initialDelay=0 Received message count. Expected: <10> but was: 
<9>
   ```
   
   I've just pulled from apache/camel:master, so I'm not sure if the master is 
green at this moment.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> support for Scala 2.12.x
> 
>
> Key: CAMEL-11292
> URL: https://issues.apache.org/jira/browse/CAMEL-11292
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-scala
>Affects Versions: 2.19.0
>Reporter: Sarunas Valaskevicius
>Priority: Minor
>
> currently camel-scala depends on Scala 2.11. could this be upgraded to 2.12.x 
> release? 
> Same with scalatest.
> All possible updates can be seen here - 
> https://mvnrepository.com/artifact/org.apache.camel/camel-scala/2.19.0
> Thanks



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

[jira] [Updated] (CAMEL-11948) NPE on DefaultMessage setBody if deprecated constructor was used

2017-10-26 Thread Claus Ibsen (JIRA) 

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

Claus Ibsen updated CAMEL-11948:

Priority: Minor  (was: Major)

> NPE on DefaultMessage setBody if deprecated constructor was used
> 
>
> Key: CAMEL-11948
> URL: https://issues.apache.org/jira/browse/CAMEL-11948
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Affects Versions: 2.20.0
>Reporter: Thomas Papke
>Priority: Minor
> Fix For: 2.21.0
>
>
> After upgrade camel 2.20.0, some operations fail with a NullPointerException:
> {code}
> Caused by: java.lang.NullPointerException
> at 
> org.apache.camel.impl.MessageSupport.setBody(MessageSupport.java:122)
> {code}
> The issue seems to be introduced with the change CAMEL-11380.
> The issue could be easily reproduced by using the deprecated constructor, 
> where no camelContext is set:
> {code}
> Message message = new DefaultMessage();
> message.setBody("something");
> {code}
> To remain better backward compatibility, i would suggest a nullcheck in the 
> setBody for cases where the CamelContext is not set.



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

[jira] [Commented] (CAMEL-11948) NPE on DefaultMessage setBody if deprecated constructor was used

2017-10-26 Thread Claus Ibsen (JIRA) 

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

Claus Ibsen commented on CAMEL-11948:
-

You are welcome to work on a github PR

> NPE on DefaultMessage setBody if deprecated constructor was used
> 
>
> Key: CAMEL-11948
> URL: https://issues.apache.org/jira/browse/CAMEL-11948
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Affects Versions: 2.20.0
>Reporter: Thomas Papke
>Priority: Minor
> Fix For: 2.21.0
>
>
> After upgrade camel 2.20.0, some operations fail with a NullPointerException:
> {code}
> Caused by: java.lang.NullPointerException
> at 
> org.apache.camel.impl.MessageSupport.setBody(MessageSupport.java:122)
> {code}
> The issue seems to be introduced with the change CAMEL-11380.
> The issue could be easily reproduced by using the deprecated constructor, 
> where no camelContext is set:
> {code}
> Message message = new DefaultMessage();
> message.setBody("something");
> {code}
> To remain better backward compatibility, i would suggest a nullcheck in the 
> setBody for cases where the CamelContext is not set.



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

[jira] [Updated] (CAMEL-11948) NPE on DefaultMessage setBody if deprecated constructor was used

2017-10-26 Thread Claus Ibsen (JIRA) 

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

Claus Ibsen updated CAMEL-11948:

Fix Version/s: 2.21.0

> NPE on DefaultMessage setBody if deprecated constructor was used
> 
>
> Key: CAMEL-11948
> URL: https://issues.apache.org/jira/browse/CAMEL-11948
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Affects Versions: 2.20.0
>Reporter: Thomas Papke
>Priority: Minor
> Fix For: 2.21.0
>
>
> After upgrade camel 2.20.0, some operations fail with a NullPointerException:
> {code}
> Caused by: java.lang.NullPointerException
> at 
> org.apache.camel.impl.MessageSupport.setBody(MessageSupport.java:122)
> {code}
> The issue seems to be introduced with the change CAMEL-11380.
> The issue could be easily reproduced by using the deprecated constructor, 
> where no camelContext is set:
> {code}
> Message message = new DefaultMessage();
> message.setBody("something");
> {code}
> To remain better backward compatibility, i would suggest a nullcheck in the 
> setBody for cases where the CamelContext is not set.



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

[jira] [Updated] (CAMEL-11948) NPE on DefaultMessage setBody if deprecated constructor was used

2017-10-26 Thread Claus Ibsen (JIRA) 

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

Claus Ibsen updated CAMEL-11948:

Issue Type: Improvement  (was: Bug)

> NPE on DefaultMessage setBody if deprecated constructor was used
> 
>
> Key: CAMEL-11948
> URL: https://issues.apache.org/jira/browse/CAMEL-11948
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Affects Versions: 2.20.0
>Reporter: Thomas Papke
> Fix For: 2.21.0
>
>
> After upgrade camel 2.20.0, some operations fail with a NullPointerException:
> {code}
> Caused by: java.lang.NullPointerException
> at 
> org.apache.camel.impl.MessageSupport.setBody(MessageSupport.java:122)
> {code}
> The issue seems to be introduced with the change CAMEL-11380.
> The issue could be easily reproduced by using the deprecated constructor, 
> where no camelContext is set:
> {code}
> Message message = new DefaultMessage();
> message.setBody("something");
> {code}
> To remain better backward compatibility, i would suggest a nullcheck in the 
> setBody for cases where the CamelContext is not set.



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

[jira] [Commented] (CAMEL-11292) support for Scala 2.12.x

2017-10-26 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CAMEL-11292:


davsclaus commented on issue #2060: CAMEL-11292: Upgrade to scala 2.12.x
URL: https://github.com/apache/camel/pull/2060#issuecomment-339684520
 
 
   mvn clean install in that directory


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> support for Scala 2.12.x
> 
>
> Key: CAMEL-11292
> URL: https://issues.apache.org/jira/browse/CAMEL-11292
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-scala
>Affects Versions: 2.19.0
>Reporter: Sarunas Valaskevicius
>Priority: Minor
>
> currently camel-scala depends on Scala 2.11. could this be upgraded to 2.12.x 
> release? 
> Same with scalatest.
> All possible updates can be seen here - 
> https://mvnrepository.com/artifact/org.apache.camel/camel-scala/2.19.0
> Thanks



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

[jira] [Closed] (CAMEL-11919) Salesforce REST API request headers not included in update,upsert,create and query operations

2017-10-26 Thread Dicken George (JIRA) 

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

Dicken George closed CAMEL-11919.
-

The issue is fixed respecting all future use cases and it also  handles all 
available headers in requests and responses. However only form version 2.21.0

> Salesforce REST API request headers not included in update,upsert,create and 
> query operations
> -
>
> Key: CAMEL-11919
> URL: https://issues.apache.org/jira/browse/CAMEL-11919
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-salesforce
>Affects Versions: 2.20.0
>Reporter: Dicken George
>Assignee: Zoran Regvart
> Fix For: 2.21.0
>
>
> There few Salesforce Rest API Http-Header parameters as decribed here.
> https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/headers.htm
> Sforce-Auto-Assign
> Sfore-Query-Options
> Sforce-Call-Options
> x-sfdc-packageversion-[namespace]
> and
> Sforce-Limit-Info : This is part of the SFDC response header.
> Out of these four, the "Sforce-Auto-Assign" header perform am implicit chain 
> reaction in salesforce which causes unwanted repercussions which in certain 
> operations needs to be controlled. For example, one of the issues,we have 
> noticed, is that during an update operation if this header is not set to 
> "FALSE", salesforce automatically updates the ownerID of the record although 
> it was not included in the request. There are other side effects which we are 
> currently not aware of. Therefore, the client would need the possibility to 
> set this header parameter within their request to True or False manually. 
> However, currently only the approval requests accept these http headers from 
> the client request, and we have found that it needs to be included in the 
> update, upsert and create queries as well. 
> Sfore-Query-Options : this header is valid for query operations, in order to 
> set the batchsize of your query response. We have implemented this as well 
> since it could come in handy which performing batch / bulk queries.
> For the time being we have implemented only these two header parameters in 
> the camel-salesforce project, however in the future the other two or all 
> three headers could also be include with camel-salesforce to customization.



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

[jira] [Commented] (CAMEL-11292) support for Scala 2.12.x

2017-10-26 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CAMEL-11292:


sinwe commented on issue #2060: CAMEL-11292: Upgrade to scala 2.12.x
URL: https://github.com/apache/camel/pull/2060#issuecomment-339669627
 
 
   @davsclaus How did you compile? I did `mvn package -pl 
components/camel-scala -am -DskipTests` and it can compile


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> support for Scala 2.12.x
> 
>
> Key: CAMEL-11292
> URL: https://issues.apache.org/jira/browse/CAMEL-11292
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-scala
>Affects Versions: 2.19.0
>Reporter: Sarunas Valaskevicius
>Priority: Minor
>
> currently camel-scala depends on Scala 2.11. could this be upgraded to 2.12.x 
> release? 
> Same with scalatest.
> All possible updates can be seen here - 
> https://mvnrepository.com/artifact/org.apache.camel/camel-scala/2.19.0
> Thanks



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

[jira] [Resolved] (CAMEL-11949) Camel-Elasticsearch5-Rest: Add a Ping Operation to Producer

2017-10-26 Thread Andrea Cosentino (JIRA) 

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

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

> Camel-Elasticsearch5-Rest: Add a Ping Operation to Producer
> ---
>
> Key: CAMEL-11949
> URL: https://issues.apache.org/jira/browse/CAMEL-11949
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-elasticsearch5-rest
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
> Fix For: 2.21.0
>
>




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

[jira] [Created] (CAMEL-11949) Camel-Elasticsearch5-Rest: Add a Ping Operation to Producer

2017-10-26 Thread Andrea Cosentino (JIRA) 
Andrea Cosentino created CAMEL-11949:


 Summary: Camel-Elasticsearch5-Rest: Add a Ping Operation to 
Producer
 Key: CAMEL-11949
 URL: https://issues.apache.org/jira/browse/CAMEL-11949
 Project: Camel
  Issue Type: New Feature
  Components: camel-elasticsearch5-rest
Reporter: Andrea Cosentino
Assignee: Andrea Cosentino
 Fix For: 2.21.0






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

[jira] [Closed] (CAMEL-11753) Camel-AWS: Create an AWS RDS component

2017-10-26 Thread Andrea Cosentino (JIRA) 

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

Andrea Cosentino closed CAMEL-11753.

Resolution: Fixed

> Camel-AWS: Create an AWS RDS component
> --
>
> Key: CAMEL-11753
> URL: https://issues.apache.org/jira/browse/CAMEL-11753
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-aws
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
> Fix For: Future
>
>
> https://aws.amazon.com/it/rds/
> Similar to EC2



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

[jira] [Commented] (CAMEL-11893) No test coverage for camel-solr

2017-10-26 Thread Andrea Cosentino (JIRA) 

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

Andrea Cosentino commented on CAMEL-11893:
--

Contributions are welcome:
https://github.com/apache/camel/blob/master/CONTRIBUTING.md

> No test coverage for camel-solr
> ---
>
> Key: CAMEL-11893
> URL: https://issues.apache.org/jira/browse/CAMEL-11893
> Project: Camel
>  Issue Type: Task
>  Components: camel-solr
>Reporter: Thomas Diesler
>Priority: Minor
> Fix For: 2.20.1, 2.21.0
>
>
> CrossRef: https://github.com/wildfly-extras/wildfly-camel/issues/2030



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

[jira] [Resolved] (CAMEL-11921) Camel-Elasticsearch5-rest: Create Karaf feature

2017-10-26 Thread Andrea Cosentino (JIRA) 

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

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

> Camel-Elasticsearch5-rest: Create Karaf feature
> ---
>
> Key: CAMEL-11921
> URL: https://issues.apache.org/jira/browse/CAMEL-11921
> Project: Camel
>  Issue Type: Task
>  Components: camel-elasticsearch5-rest
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
> Fix For: 2.21.0
>
>




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

[jira] [Commented] (CAMEL-11914) camel-fn component to call funktions on the fnplatform

2017-10-26 Thread Ramu kakarla (JIRA) 

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

 Ramu kakarla commented on CAMEL-11914:
---

I will look into it

> camel-fn component to call funktions on the fnplatform
> --
>
> Key: CAMEL-11914
> URL: https://issues.apache.org/jira/browse/CAMEL-11914
> Project: Camel
>  Issue Type: New Feature
>Reporter: Claus Ibsen
> Fix For: Future
>
>
> One of those popular servless function platforms - fnproject has a java 
> client api, which can be used to call funktions
> https://github.com/fnproject/fdk-java
> We should create a little Camel component for this.



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

[jira] [Created] (CAMEL-11948) NPE on DefaultMessage setBody if deprecated constructor was used

2017-10-26 Thread Thomas Papke (JIRA) 
Thomas Papke created CAMEL-11948:


 Summary: NPE on DefaultMessage setBody if deprecated constructor 
was used
 Key: CAMEL-11948
 URL: https://issues.apache.org/jira/browse/CAMEL-11948
 Project: Camel
  Issue Type: Bug
  Components: camel-core
Affects Versions: 2.20.0
Reporter: Thomas Papke


After upgrade camel 2.20.0, some operations fail with a NullPointerException:
{code}
Caused by: java.lang.NullPointerException
at org.apache.camel.impl.MessageSupport.setBody(MessageSupport.java:122)
{code}

The issue seems to be introduced with the change CAMEL-11380.

The issue could be easily reproduced by using the deprecated constructor, where 
no camelContext is set:
{code}
Message message = new DefaultMessage();
message.setBody("something");
{code}

To remain better backward compatibility, i would suggest a nullcheck in the 
setBody for cases where the CamelContext is not set.



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

[jira] [Created] (CAMEL-11947) Possible race condition in iec60870 producer

2017-10-26 Thread James Netherton (JIRA) 
James Netherton created CAMEL-11947:
---

 Summary: Possible race condition in iec60870 producer
 Key: CAMEL-11947
 URL: https://issues.apache.org/jira/browse/CAMEL-11947
 Project: Camel
  Issue Type: Bug
  Components: camel-iec60870
Affects Versions: 2.20.0
Reporter: James Netherton


I've been working on integrating the iec60870 component with WIldFly. I have an 
integration test 
[here|https://github.com/wildfly-extras/wildfly-camel/blob/master/itests/standalone/basic/src/test/java/org/wildfly/camel/test/iec60870/Iec60870IntegrationTest.java].
 When it's executed on its own, everything works fine. When it runs with the 
entire test suite, I encounter a NullPointerException in the Neoscada 
[Client.writeCommand()|https://github.com/eclipse/neoscada/blob/master/protocols/org.eclipse.neoscada.protocol.iec60870.client/src/org/eclipse/neoscada/protocol/iec60870/client/Client.java#L259]
 method.

It seems that the Netty channel that it's trying to write to is null and that 
initialisation of the channel happens async in 
[Client.handleOperationComplete()|https://github.com/eclipse/neoscada/blob/master/protocols/org.eclipse.neoscada.protocol.iec60870.client/src/org/eclipse/neoscada/protocol/iec60870/client/Client.java#L138].
 When I debug, I see the channel gets initialised after the call to 
writeCommand().

Not sure if there's any way to detect whether the client connection has been 
established before trying to use it in the 
[ClientProducer|https://github.com/apache/camel/blob/master/components/camel-iec60870/src/main/java/org/apache/camel/component/iec60870/client/ClientProducer.java#L49].
 Or maybe this ticket would be better placed with the neoscada project?



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