[jira] [Commented] (CAMEL-12440) Upgrade camel-dozer to 6.2

2018-04-12 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CAMEL-12440:


garethahealy opened a new pull request #2291: [CAMEL-12440] Upgraded dozer to 
6.2
URL: https://github.com/apache/camel/pull/2291
 
 
   - https://issues.apache.org/jira/browse/CAMEL-12440


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


> Upgrade camel-dozer to 6.2
> --
>
> Key: CAMEL-12440
> URL: https://issues.apache.org/jira/browse/CAMEL-12440
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-dozer
>Reporter: Gareth Healy
>Priority: Major
> Fix For: 2.22.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CAMEL-12440) Upgrade camel-dozer to 6.2

2018-04-12 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CAMEL-12440:


GitHub user garethahealy opened a pull request:

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

[CAMEL-12440] Upgraded dozer to 6.2

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

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

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

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

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


commit 1ad0ff613abf3ab3c4fadbaa5c0b3cf2ecf1
Author: Gareth Healy 
Date:   2018-04-12T22:28:38Z

[CAMEL-12440] Upgraded dozer to 6.2




> Upgrade camel-dozer to 6.2
> --
>
> Key: CAMEL-12440
> URL: https://issues.apache.org/jira/browse/CAMEL-12440
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-dozer
>Reporter: Gareth Healy
>Priority: Major
> Fix For: 2.22.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (CAMEL-12440) Upgrade camel-dozer to 6.2

2018-04-12 Thread Gareth Healy (JIRA) 
Gareth Healy created CAMEL-12440:


 Summary: Upgrade camel-dozer to 6.2
 Key: CAMEL-12440
 URL: https://issues.apache.org/jira/browse/CAMEL-12440
 Project: Camel
  Issue Type: Improvement
  Components: camel-dozer
Reporter: Gareth Healy
 Fix For: 2.22.0






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (CAMEL-12439) FailedToCreateRouteException should mask sensitive information in uris

2018-04-12 Thread Claus Ibsen (JIRA) 

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

Claus Ibsen resolved CAMEL-12439.
-
Resolution: Fixed

> FailedToCreateRouteException should mask sensitive information in uris
> --
>
> Key: CAMEL-12439
> URL: https://issues.apache.org/jira/browse/CAMEL-12439
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Affects Versions: 2.21.0
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 2.20.4, 2.21.1, 2.22.0
>
>
> If you misconfigure routes etc and they fail being created you get an 
> exception 
> FailedToCreateRouteException that output parts of the route where the problem 
> is, and in there, we should mask sensitive details such as passwords.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (CAMEL-12439) FailedToCreateRouteException should mask sensitive information in uris

2018-04-12 Thread Claus Ibsen (JIRA) 
Claus Ibsen created CAMEL-12439:
---

 Summary: FailedToCreateRouteException should mask sensitive 
information in uris
 Key: CAMEL-12439
 URL: https://issues.apache.org/jira/browse/CAMEL-12439
 Project: Camel
  Issue Type: Improvement
  Components: camel-core
Affects Versions: 2.21.0
Reporter: Claus Ibsen
Assignee: Claus Ibsen
 Fix For: 2.20.4, 2.21.1, 2.22.0


If you misconfigure routes etc and they fail being created you get an exception 

FailedToCreateRouteException that output parts of the route where the problem 
is, and in there, we should mask sensitive details such as passwords.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (CAMEL-12436) camel-undertow - should extract body message from PATCH request

2018-04-12 Thread Claus Ibsen (JIRA) 

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

Claus Ibsen resolved CAMEL-12436.
-
   Resolution: Fixed
 Assignee: Claus Ibsen
Fix Version/s: 2.22.0
   2.21.1
   2.20.4

Thanks for the PR

> camel-undertow - should extract body message from PATCH request
> ---
>
> Key: CAMEL-12436
> URL: https://issues.apache.org/jira/browse/CAMEL-12436
> Project: Camel
>  Issue Type: Bug
>  Components: camel-undertow
>Affects Versions: 2.21.0
>Reporter: Tomas Turek
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 2.20.4, 2.21.1, 2.22.0
>
>
> Undertow component should process body message of HTTP PATCH request.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CAMEL-12437) Ability to define dynamic bucket name for s3 router using standard S3Constants.BUCKET_NAME supplied in header

2018-04-12 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CAMEL-12437:


oscerd commented on issue #2290: CAMEL-12437
URL: https://github.com/apache/camel/pull/2290#issuecomment-380817305
 
 
   Merged on master. Thanks.


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


> Ability to define dynamic bucket name for s3 router using standard 
> S3Constants.BUCKET_NAME supplied in header
> -
>
> Key: CAMEL-12437
> URL: https://issues.apache.org/jira/browse/CAMEL-12437
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-aws
>Affects Versions: 2.20.2
>Reporter: Aliaksandr Laptseu
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 2.22.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (CAMEL-12437) Ability to define dynamic bucket name for s3 router using standard S3Constants.BUCKET_NAME supplied in header

2018-04-12 Thread Andrea Cosentino (JIRA) 

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

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

> Ability to define dynamic bucket name for s3 router using standard 
> S3Constants.BUCKET_NAME supplied in header
> -
>
> Key: CAMEL-12437
> URL: https://issues.apache.org/jira/browse/CAMEL-12437
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-aws
>Affects Versions: 2.20.2
>Reporter: Aliaksandr Laptseu
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 2.22.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CAMEL-12437) Ability to define dynamic bucket name for s3 router using standard S3Constants.BUCKET_NAME supplied in header

2018-04-12 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CAMEL-12437:


Github user oscerd closed the pull request at:

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


> Ability to define dynamic bucket name for s3 router using standard 
> S3Constants.BUCKET_NAME supplied in header
> -
>
> Key: CAMEL-12437
> URL: https://issues.apache.org/jira/browse/CAMEL-12437
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-aws
>Affects Versions: 2.20.2
>Reporter: Aliaksandr Laptseu
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 2.22.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CAMEL-12437) Ability to define dynamic bucket name for s3 router using standard S3Constants.BUCKET_NAME supplied in header

2018-04-12 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CAMEL-12437:


oscerd closed pull request #2290: CAMEL-12437
URL: https://github.com/apache/camel/pull/2290
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git 
a/components/camel-aws/src/main/java/org/apache/camel/component/aws/s3/S3Producer.java
 
b/components/camel-aws/src/main/java/org/apache/camel/component/aws/s3/S3Producer.java
index df6e1c36409..2efb9904aec 100644
--- 
a/components/camel-aws/src/main/java/org/apache/camel/component/aws/s3/S3Producer.java
+++ 
b/components/camel-aws/src/main/java/org/apache/camel/component/aws/s3/S3Producer.java
@@ -228,7 +228,12 @@ public void processSingleOp(final Exchange exchange) 
throws Exception {
 is = new ByteArrayInputStream(baos.toByteArray());
 }
 
-putObjectRequest = new 
PutObjectRequest(getConfiguration().getBucketName(), determineKey(exchange), 
is, objectMetadata);
+String bucketName = 
exchange.getIn().getHeader(S3Constants.BUCKET_NAME, String.class);
+if (bucketName == null){
+LOG.trace("Bucket name is not in header, using default one  
[{}]...", getConfiguration().getBucketName());
+bucketName = getConfiguration().getBucketName();
+}
+putObjectRequest = new PutObjectRequest(bucketName, 
determineKey(exchange), is, objectMetadata);
 
 String storageClass = determineStorageClass(exchange);
 if (storageClass != null) {


 


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


> Ability to define dynamic bucket name for s3 router using standard 
> S3Constants.BUCKET_NAME supplied in header
> -
>
> Key: CAMEL-12437
> URL: https://issues.apache.org/jira/browse/CAMEL-12437
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-aws
>Affects Versions: 2.20.2
>Reporter: Aliaksandr Laptseu
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 2.22.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CAMEL-12436) camel-undertow - should extract body message from PATCH request

2018-04-12 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CAMEL-12436:


davsclaus closed pull request #2289: CAMEL-12436: Fix Undertow to extract body 
message from PATCH request
URL: https://github.com/apache/camel/pull/2289
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git 
a/components/camel-undertow/src/main/java/org/apache/camel/component/undertow/DefaultUndertowHttpBinding.java
 
b/components/camel-undertow/src/main/java/org/apache/camel/component/undertow/DefaultUndertowHttpBinding.java
index 91bd8522205..ae1f6fe6e45 100644
--- 
a/components/camel-undertow/src/main/java/org/apache/camel/component/undertow/DefaultUndertowHttpBinding.java
+++ 
b/components/camel-undertow/src/main/java/org/apache/camel/component/undertow/DefaultUndertowHttpBinding.java
@@ -124,7 +124,7 @@ public Message toCamelMessage(HttpServerExchange 
httpExchange, Exchange exchange
 } else {
 //extract body by myself if undertow parser didn't handle and the 
method is allowed to have one
 //body is extracted as byte[] then auto TypeConverter kicks in
-if (Methods.POST.equals(httpExchange.getRequestMethod()) || 
Methods.PUT.equals(httpExchange.getRequestMethod())) {
+if (Methods.POST.equals(httpExchange.getRequestMethod()) || 
Methods.PUT.equals(httpExchange.getRequestMethod()) || 
Methods.PATCH.equals(httpExchange.getRequestMethod())) {
 
result.setBody(readFromChannel(httpExchange.getRequestChannel()));
 } else {
 result.setBody(null);
diff --git 
a/components/camel-undertow/src/test/java/org/apache/camel/component/undertow/rest/RestUndertowProducerPatchTest.java
 
b/components/camel-undertow/src/test/java/org/apache/camel/component/undertow/rest/RestUndertowProducerPatchTest.java
new file mode 100644
index 000..bfbd59fca2b
--- /dev/null
+++ 
b/components/camel-undertow/src/test/java/org/apache/camel/component/undertow/rest/RestUndertowProducerPatchTest.java
@@ -0,0 +1,58 @@
+/**
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *  http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.camel.component.undertow.rest;
+
+import org.apache.camel.builder.RouteBuilder;
+import org.apache.camel.component.mock.MockEndpoint;
+import org.apache.camel.component.undertow.BaseUndertowTest;
+import org.junit.Test;
+
+public class RestUndertowProducerPatchTest extends BaseUndertowTest {
+
+@Test
+public void testUndertowProducerPatch() throws Exception {
+String body = "Donald Duck";
+String id = "123";
+
+MockEndpoint mock = getMockEndpoint("mock:input");
+mock.message(0).body().isEqualTo(body);
+mock.message(0).header("id").isEqualTo(id);
+
+fluentTemplate.withBody(body).withHeader("id", 
id).to("direct:start").send();
+
+assertMockEndpointsSatisfied();
+}
+
+@Override
+protected RouteBuilder createRouteBuilder() throws Exception {
+return new RouteBuilder() {
+@Override
+public void configure() throws Exception {
+// configure to use localhost with the given port
+
restConfiguration().component("undertow").host("localhost").port(getPort());
+
+from("direct:start")
+.to("rest:patch:users/{id}");
+
+// use the rest DSL to define the rest services
+rest("/users/")
+.patch("{id}")
+.to("mock:input");
+}
+};
+}
+}


 


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


> camel-undertow -

[jira] [Commented] (CAMEL-12436) camel-undertow - should extract body message from PATCH request

2018-04-12 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CAMEL-12436:


Github user davsclaus closed the pull request at:

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


> camel-undertow - should extract body message from PATCH request
> ---
>
> Key: CAMEL-12436
> URL: https://issues.apache.org/jira/browse/CAMEL-12436
> Project: Camel
>  Issue Type: Bug
>  Components: camel-undertow
>Affects Versions: 2.21.0
>Reporter: Tomas Turek
>Priority: Major
>
> Undertow component should process body message of HTTP PATCH request.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (CAMEL-12438) camel-netty4 - Add timeout support for SPI correlation manager

2018-04-12 Thread Claus Ibsen (JIRA) 

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

Claus Ibsen resolved CAMEL-12438.
-
Resolution: Fixed

> camel-netty4 - Add timeout support for SPI correlation manager
> --
>
> Key: CAMEL-12438
> URL: https://issues.apache.org/jira/browse/CAMEL-12438
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-netty4
>Affects Versions: 2.21.0
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 2.21.1, 2.22.0
>
>
> We should make it easier to handle timeouts for responses that do not come 
> back.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (CAMEL-12438) camel-netty4 - Add timeout support for SPI correlation manager

2018-04-12 Thread Claus Ibsen (JIRA) 
Claus Ibsen created CAMEL-12438:
---

 Summary: camel-netty4 - Add timeout support for SPI correlation 
manager
 Key: CAMEL-12438
 URL: https://issues.apache.org/jira/browse/CAMEL-12438
 Project: Camel
  Issue Type: Improvement
  Components: camel-netty4
Affects Versions: 2.21.0
Reporter: Claus Ibsen
Assignee: Claus Ibsen
 Fix For: 2.21.1, 2.22.0


We should make it easier to handle timeouts for responses that do not come back.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (CAMEL-12437) Ability to define dynamic bucket name for s3 router using standard S3Constants.BUCKET_NAME supplied in header

2018-04-12 Thread Andrea Cosentino (JIRA) 

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

Andrea Cosentino updated CAMEL-12437:
-
Fix Version/s: 2.22.0

> Ability to define dynamic bucket name for s3 router using standard 
> S3Constants.BUCKET_NAME supplied in header
> -
>
> Key: CAMEL-12437
> URL: https://issues.apache.org/jira/browse/CAMEL-12437
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-aws
>Affects Versions: 2.20.2
>Reporter: Aliaksandr Laptseu
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 2.22.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (CAMEL-12437) Ability to define dynamic bucket name for s3 router using standard S3Constants.BUCKET_NAME supplied in header

2018-04-12 Thread Andrea Cosentino (JIRA) 

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

Andrea Cosentino reassigned CAMEL-12437:


Assignee: Andrea Cosentino

> Ability to define dynamic bucket name for s3 router using standard 
> S3Constants.BUCKET_NAME supplied in header
> -
>
> Key: CAMEL-12437
> URL: https://issues.apache.org/jira/browse/CAMEL-12437
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-aws
>Affects Versions: 2.20.2
>Reporter: Aliaksandr Laptseu
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 2.22.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CAMEL-12437) Ability to define dynamic bucket name for s3 router using standard S3Constants.BUCKET_NAME supplied in header

2018-04-12 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CAMEL-12437:


oscerd commented on issue #2290: CAMEL-12437
URL: https://github.com/apache/camel/pull/2290#issuecomment-380794923
 
 
   Sounds reasonable. I'll merge ASAP, thanks for the 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


> Ability to define dynamic bucket name for s3 router using standard 
> S3Constants.BUCKET_NAME supplied in header
> -
>
> Key: CAMEL-12437
> URL: https://issues.apache.org/jira/browse/CAMEL-12437
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-aws
>Affects Versions: 2.20.2
>Reporter: Aliaksandr Laptseu
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CAMEL-12437) Ability to define dynamic bucket name for s3 router using standard S3Constants.BUCKET_NAME supplied in header

2018-04-12 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CAMEL-12437:


GitHub user alaptseu opened a pull request:

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

CAMEL-12437

I created a jira ticket for this improvement 
https://issues.apache.org/jira/browse/CAMEL-12437

Basically with current implementation (as per camel version 2.20.2) there 
is no way to provide dynamic s3 bucket name when you upload files (it's 
possible though if copying files from source bucket to destination bucket).
I think we could use S3Constants.BUCKET_NAME provided at exchange header 
and if it is set use that value as bucket name where file will be uploaded, if 
S3Constants.BUCKET_NAME is not provided then  use bucket which is preconfigured 
at configuration.



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

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

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

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


commit 97304063ec80f448ebd7040720f27bc2b8f59d5c
Author: Laptseu 
Date:   2018-04-12T12:28:46Z

CAMEL-12437




> Ability to define dynamic bucket name for s3 router using standard 
> S3Constants.BUCKET_NAME supplied in header
> -
>
> Key: CAMEL-12437
> URL: https://issues.apache.org/jira/browse/CAMEL-12437
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-aws
>Affects Versions: 2.20.2
>Reporter: Aliaksandr Laptseu
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CAMEL-12437) Ability to define dynamic bucket name for s3 router using standard S3Constants.BUCKET_NAME supplied in header

2018-04-12 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CAMEL-12437:


alaptseu opened a new pull request #2290: CAMEL-12437
URL: https://github.com/apache/camel/pull/2290
 
 
   I created a jira ticket for this improvement 
https://issues.apache.org/jira/browse/CAMEL-12437
   
   Basically with current implementation (as per camel version 2.20.2) there is 
no way to provide dynamic s3 bucket name when you upload files (it's possible 
though if copying files from source bucket to destination bucket).
   I think we could use S3Constants.BUCKET_NAME provided at exchange header and 
if it is set use that value as bucket name where file will be uploaded, if 
S3Constants.BUCKET_NAME is not provided then  use bucket which is preconfigured 
at configuration.
   
   


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


> Ability to define dynamic bucket name for s3 router using standard 
> S3Constants.BUCKET_NAME supplied in header
> -
>
> Key: CAMEL-12437
> URL: https://issues.apache.org/jira/browse/CAMEL-12437
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-aws
>Affects Versions: 2.20.2
>Reporter: Aliaksandr Laptseu
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (CAMEL-12437) Ability to define dynamic bucket name for s3 router using standard S3Constants.BUCKET_NAME supplied in header

2018-04-12 Thread Aliaksandr Laptseu (JIRA) 

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

Aliaksandr Laptseu updated CAMEL-12437:
---
Affects Version/s: 2.20.2
  Component/s: camel-aws

> Ability to define dynamic bucket name for s3 router using standard 
> S3Constants.BUCKET_NAME supplied in header
> -
>
> Key: CAMEL-12437
> URL: https://issues.apache.org/jira/browse/CAMEL-12437
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-aws
>Affects Versions: 2.20.2
>Reporter: Aliaksandr Laptseu
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (CAMEL-12437) Ability to define dynamic bucket name for s3 router using standard S3Constants.BUCKET_NAME supplied in header

2018-04-12 Thread Aliaksandr Laptseu (JIRA) 
Aliaksandr Laptseu created CAMEL-12437:
--

 Summary: Ability to define dynamic bucket name for s3 router using 
standard S3Constants.BUCKET_NAME supplied in header
 Key: CAMEL-12437
 URL: https://issues.apache.org/jira/browse/CAMEL-12437
 Project: Camel
  Issue Type: Improvement
Reporter: Aliaksandr Laptseu






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (CAMEL-12436) camel-undertow - should extract body message from PATCH request

2018-04-12 Thread Tomas Turek (JIRA) 

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

Tomas Turek updated CAMEL-12436:

Summary: camel-undertow - should extract body message from PATCH request  
(was: camel-undertow - should extract body massage from PATCH request)

> camel-undertow - should extract body message from PATCH request
> ---
>
> Key: CAMEL-12436
> URL: https://issues.apache.org/jira/browse/CAMEL-12436
> Project: Camel
>  Issue Type: Bug
>  Components: camel-undertow
>Affects Versions: 2.21.0
>Reporter: Tomas Turek
>Priority: Major
>
> Undertow component should process body message of HTTP PATCH request.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CAMEL-12436) camel-undertow - should extract body massage from PATCH request

2018-04-12 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CAMEL-12436:


GitHub user osmman opened a pull request:

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

CAMEL-12436: Fix Undertow to extract body message from PATCH request



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

$ git pull https://github.com/osmman/camel undertow-patch-method

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

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


commit 3dfd992e7a262f4c917351f1ba535e4d3d59d2a9
Author: Tomas Turek 
Date:   2018-04-11T14:35:46Z

CAMEL-12436: Fix Undertow to extract body message from PATCH request




> camel-undertow - should extract body massage from PATCH request
> ---
>
> Key: CAMEL-12436
> URL: https://issues.apache.org/jira/browse/CAMEL-12436
> Project: Camel
>  Issue Type: Bug
>  Components: camel-undertow
>Affects Versions: 2.21.0
>Reporter: Tomas Turek
>Priority: Major
>
> Undertow component should process body message of HTTP PATCH request.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CAMEL-12436) camel-undertow - should extract body massage from PATCH request

2018-04-12 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CAMEL-12436:


osmman opened a new pull request #2289: CAMEL-12436: Fix Undertow to extract 
body message from PATCH request
URL: https://github.com/apache/camel/pull/2289
 
 
   


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


> camel-undertow - should extract body massage from PATCH request
> ---
>
> Key: CAMEL-12436
> URL: https://issues.apache.org/jira/browse/CAMEL-12436
> Project: Camel
>  Issue Type: Bug
>  Components: camel-undertow
>Affects Versions: 2.21.0
>Reporter: Tomas Turek
>Priority: Major
>
> Undertow component should process body message of HTTP PATCH request.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (CAMEL-12436) camel-undertow - should extract body massage from PATCH request

2018-04-12 Thread Tomas Turek (JIRA) 
Tomas Turek created CAMEL-12436:
---

 Summary: camel-undertow - should extract body massage from PATCH 
request
 Key: CAMEL-12436
 URL: https://issues.apache.org/jira/browse/CAMEL-12436
 Project: Camel
  Issue Type: Bug
  Components: camel-undertow
Affects Versions: 2.21.0
Reporter: Tomas Turek


Undertow component should process body message of HTTP PATCH request.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (CAMEL-12435) camel-netty4 - Shared connection pool should re-create connection if its no longer valid

2018-04-12 Thread Claus Ibsen (JIRA) 

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

Claus Ibsen resolved CAMEL-12435.
-
Resolution: Fixed

> camel-netty4 - Shared connection pool should re-create connection if its no 
> longer valid
> 
>
> Key: CAMEL-12435
> URL: https://issues.apache.org/jira/browse/CAMEL-12435
> Project: Camel
>  Issue Type: Bug
>  Components: camel-netty4
>Affects Versions: 2.21.0
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 2.21.1, 2.22.0
>
>
> If you turn of the connection pooling on the producer and use the shared 
> single instance for multiplexing then if the connection becomes invalid such 
> as read time triggered by netty that then closes the connection.
> Then we should re-create the connection, like the pooling does with test on 
> borrow.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (CAMEL-12435) camel-netty4 - Shared connection pool should re-create connection if its no longer valid

2018-04-12 Thread Claus Ibsen (JIRA) 
Claus Ibsen created CAMEL-12435:
---

 Summary: camel-netty4 - Shared connection pool should re-create 
connection if its no longer valid
 Key: CAMEL-12435
 URL: https://issues.apache.org/jira/browse/CAMEL-12435
 Project: Camel
  Issue Type: Bug
  Components: camel-netty4
Affects Versions: 2.21.0
Reporter: Claus Ibsen
Assignee: Claus Ibsen
 Fix For: 2.21.1, 2.22.0


If you turn of the connection pooling on the producer and use the shared single 
instance for multiplexing then if the connection becomes invalid such as read 
time triggered by netty that then closes the connection.

Then we should re-create the connection, like the pooling does with test on 
borrow.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (CAMEL-12434) camel-salesforce - Limits can not be deserialized in API versions >= 41.0

2018-04-12 Thread Claus Ibsen (JIRA) 

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

Claus Ibsen updated CAMEL-12434:

Summary: camel-salesforce - Limits can not be deserialized in API versions 
>= 41.0  (was: Limits can not be deserialized in API versions >= 41.0)

> camel-salesforce - Limits can not be deserialized in API versions >= 41.0
> -
>
> Key: CAMEL-12434
> URL: https://issues.apache.org/jira/browse/CAMEL-12434
> Project: Camel
>  Issue Type: Bug
>  Components: camel-salesforce
>Affects Versions: 2.20.1, 2.20.2, 2.21.0
>Reporter: Chris Romack
>Assignee: Zoran Regvart
>Priority: Minor
>
> Starting with Salesforce REST API 41.0, it appears that they have made a 
> breaking change to the Limits json payload.  Jackson can no longer 
> deserialize.
>  
> Error is
> 2018-04-11T13:02:45.644-0500 ERROR [dispatcherServlet] http-nio-8080-exec-3 
> [] Servlet.service() for servlet [dispatcherServlet] in context with path [] 
> threw exception [Request processing failed; nested exception is 
> org.apache.camel.CamelExecutionException: Exception occurred during execution 
> on the exchange: 
> Exchange[ID-isdv183994l-containerstore-com-1523469717836-0-13]] with root 
> cause
> com.fasterxml.jackson.databind.exc.InvalidFormatException: Can not 
> deserialize Map key of type 
> org.apache.camel.component.salesforce.api.dto.Limits$Operation from String 
> "PermissionSets": not a valid representation, problem: 
> (com.fasterxml.jackson.databind.exc.InvalidFormatException) Can not 
> deserialize Map key of type 
> org.apache.camel.component.salesforce.api.dto.Limits$Operation from String 
> "PermissionSets": not one of values excepted for Enum class: 
> [DailyApiRequests, DailyDurableGenericStreamingApiEvents, 
> ConcurrentAsyncGetReportInstances, DailyGenericStreamingApiEvents, 
> DailyStreamingApiEvents, DailyWorkflowEmails, HourlyDashboardStatuses, 
> HourlySyncReportRuns, DataStorageMB, SingleEmail, HourlyTimeBasedWorkflow, 
> ConcurrentSyncReportRuns, DurableStreamingApiConcurrentClients, 
> DailyBulkApiRequests, FileStorageMB, DailyAsyncApexExecutions, MassEmail, 
> StreamingApiConcurrentClients, HourlyDashboardResults, HourlyAsyncReportRuns, 
> HourlyDashboardRefreshes, HourlyODataCallout, DailyDurableStreamingApiEvents]
>  at [Source: java.io.ByteArrayInputStream@215469a9; line: 1, column: 6646]
>  at [Source: java.io.ByteArrayInputStream@215469a9; line: 1, column: 6646]
>  at 
> com.fasterxml.jackson.databind.exc.InvalidFormatException.from(InvalidFormatException.java:74)
>  at 
> com.fasterxml.jackson.databind.DeserializationContext.weirdKeyException(DeserializationContext.java:1389)
>  at 
> com.fasterxml.jackson.databind.DeserializationContext.handleWeirdKey(DeserializationContext.java:880)
>  at 
> com.fasterxml.jackson.databind.deser.std.StdKeyDeserializer.deserializeKey(StdKeyDeserializer.java:130)
>  at 
> com.fasterxml.jackson.databind.deser.std.MapDeserializer._readAndBind(MapDeserializer.java:445)
>  at 
> com.fasterxml.jackson.databind.deser.std.MapDeserializer.deserialize(MapDeserializer.java:365)
>  at 
> com.fasterxml.jackson.databind.deser.std.MapDeserializer.deserialize(MapDeserializer.java:27)
>  at 
> com.fasterxml.jackson.databind.ObjectMapper._readValue(ObjectMapper.java:3786)
>  at 
> com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:2139)
>  at com.fasterxml.jackson.core.JsonParser.readValueAs(JsonParser.java:1650)
>  at 
> org.apache.camel.component.salesforce.api.dto.Limits$LimitsDeserializer.deserialize(Limits.java:55)
>  at 
> com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:3814)
>  at 
> com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:2924)
>  at 
> org.apache.camel.component.salesforce.internal.processor.JsonRestProcessor.processResponse(JsonRestProcessor.java:197)
>  at 
> org.apache.camel.component.salesforce.internal.processor.AbstractRestProcessor.lambda$processWithResponseCallback$5(AbstractRestProcessor.java:783)
>  at 
> org.apache.camel.component.salesforce.internal.client.DefaultRestClient$DelegatingClientCallback.onResponse(DefaultRestClient.java:502)
>  at 
> org.apache.camel.component.salesforce.internal.client.AbstractClientBase$1.onComplete(AbstractClientBase.java:235)
>  at 
> org.eclipse.jetty.client.ResponseNotifier.notifyComplete(ResponseNotifier.java:193)
>  at 
> org.eclipse.jetty.client.ResponseNotifier.notifyComplete(ResponseNotifier.java:185)
>  at 
> org.eclipse.jetty.client.HttpReceiver.terminateResponse(HttpReceiver.java:459)
>  at 
> org.eclipse.jetty.client.HttpReceiver.responseSuccess(HttpReceiver.java:405)
>  at 
> org.eclipse.jetty.client.http.HttpReceiverOverHTTP.messageComplete(HttpReceiverOverHTTP.java:297)
>  at