[jira] [Resolved] (CAMEL-12399) CxfRsProducer doesn't configure CxfRsEndpointConfigurer while using the Proxy API

[Freeman Fang (JIRA)]

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

Freeman Fang resolved CAMEL-12399.
--
   Resolution: Fixed
Fix Version/s: 2.22.0
   2.21.1

> CxfRsProducer doesn't configure CxfRsEndpointConfigurer while using the Proxy 
> API
> -
>
> Key: CAMEL-12399
> URL: https://issues.apache.org/jira/browse/CAMEL-12399
> Project: Camel
>  Issue Type: Bug
>  Components: camel-cxfrs
>Affects Versions: 2.21.0
>Reporter: Mike Schippers
>Assignee: Freeman Fang
>Priority: Major
> Fix For: 2.21.1, 2.22.0
>
>
> The CxfRsProducer doesn't configure a CxfRsEndpointConfigurer on the client 
> while using the Proxy API. When using the HTTP API this is working fine.
> So when i create an endpoint like this:
>  
> {code:java}
> CxfRsEndpoint endpoint = new CxfRsEndpoint(); 
> endpoint.setCxfRsEndpointConfigurer(new MyCxfRsEndpointConfigurer());
> {code}
>  
> {code:java}
> public static class MyCxfRsEndpointConfigurer implements 
> CxfRsEndpointConfigurer {
> @Override
> public void configure(AbstractJAXRSFactoryBean factoryBean) {
> }
> @Override
> public void configureClient(Client client) {
> client.header("foo", "bar");
> }
> @Override
> public void configureServer(Server server) {
> }
> }
> {code}
> In case i use the HTTP API the header "foo" is sent but not when i use the 
> Proxy API.



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

[jira] [Commented] (CAMEL-12399) CxfRsProducer doesn't configure CxfRsEndpointConfigurer while using the Proxy API

[Freeman Fang (JIRA)]

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

Freeman Fang commented on CAMEL-12399:
--

patch applied on behalf of Mike Schippers  with thanks!

> CxfRsProducer doesn't configure CxfRsEndpointConfigurer while using the Proxy 
> API
> -
>
> Key: CAMEL-12399
> URL: https://issues.apache.org/jira/browse/CAMEL-12399
> Project: Camel
>  Issue Type: Bug
>  Components: camel-cxfrs
>Affects Versions: 2.21.0
>Reporter: Mike Schippers
>Assignee: Freeman Fang
>Priority: Major
>
> The CxfRsProducer doesn't configure a CxfRsEndpointConfigurer on the client 
> while using the Proxy API. When using the HTTP API this is working fine.
> So when i create an endpoint like this:
>  
> {code:java}
> CxfRsEndpoint endpoint = new CxfRsEndpoint(); 
> endpoint.setCxfRsEndpointConfigurer(new MyCxfRsEndpointConfigurer());
> {code}
>  
> {code:java}
> public static class MyCxfRsEndpointConfigurer implements 
> CxfRsEndpointConfigurer {
> @Override
> public void configure(AbstractJAXRSFactoryBean factoryBean) {
> }
> @Override
> public void configureClient(Client client) {
> client.header("foo", "bar");
> }
> @Override
> public void configureServer(Server server) {
> }
> }
> {code}
> In case i use the HTTP API the header "foo" is sent but not when i use the 
> Proxy API.



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

[jira] [Commented] (CAMEL-12399) CxfRsProducer doesn't configure CxfRsEndpointConfigurer while using the Proxy API

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-12399:


ffang closed pull request #2265: CAMEL-12399: CxfRsProducer configures 
CxfRsEndpointConfigurer while using the Proxy API
URL: https://github.com/apache/camel/pull/2265
 
 
   

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-cxf/src/main/java/org/apache/camel/component/cxf/jaxrs/CxfRsProducer.java
 
b/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/jaxrs/CxfRsProducer.java
index fa9978c71b3..7edd0ba83e3 100644
--- 
a/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/jaxrs/CxfRsProducer.java
+++ 
b/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/jaxrs/CxfRsProducer.java
@@ -200,6 +200,8 @@ protected void invokeAsyncProxyClient(Exchange exchange, 
final AsyncCallback cal
 target = cfb.createWithValues(varValues);
 }
 
+((CxfRsEndpoint) 
getEndpoint()).getChainedCxfRsEndpointConfigurer().configureClient(target);
+
 setupClientHeaders(target, exchange);
 
 // find out the method which we want to invoke
@@ -421,7 +423,9 @@ protected void invokeProxyClient(Exchange exchange) throws 
Exception {
 } else {
 target = cfb.createWithValues(varValues);
 }
-
+
+((CxfRsEndpoint) 
getEndpoint()).getChainedCxfRsEndpointConfigurer().configureClient(target);
+
 setupClientHeaders(target, exchange);
 
 // find out the method which we want to invoke
diff --git 
a/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/jaxrs/CxfRsProducerEndpointConfigurerTest.java
 
b/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/jaxrs/CxfRsProducerEndpointConfigurerTest.java
new file mode 100644
index 000..035a79aede0
--- /dev/null
+++ 
b/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/jaxrs/CxfRsProducerEndpointConfigurerTest.java
@@ -0,0 +1,103 @@
+/**
+ * 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.cxf.jaxrs;
+
+import org.apache.camel.Exchange;
+import org.apache.camel.ExchangePattern;
+import org.apache.camel.Message;
+import org.apache.camel.builder.RouteBuilder;
+import org.apache.camel.component.cxf.common.message.CxfConstants;
+import org.apache.camel.component.cxf.jaxrs.testbean.Customer;
+import org.apache.camel.component.cxf.jaxrs.testbean.CustomerService;
+import org.apache.camel.test.junit4.CamelTestSupport;
+import org.apache.cxf.endpoint.Server;
+import org.apache.cxf.jaxrs.AbstractJAXRSFactoryBean;
+import org.apache.cxf.jaxrs.client.Client;
+import org.apache.cxf.message.MessageContentsList;
+import org.junit.Test;
+
+import javax.ws.rs.HttpMethod;
+
+public class CxfRsProducerEndpointConfigurerTest extends CamelTestSupport {
+
+protected RouteBuilder createRouteBuilder() {
+return new RouteBuilder() {
+public void configure() {
+CxfRsEndpoint endpoint = new CxfRsEndpoint();
+endpoint.setAddress("http://localhost:8000;);
+endpoint.setCamelContext(context);
+endpoint.setResourceClasses(CustomerService.class);
+endpoint.setEndpointUriIfNotSpecified("cxfrs:simple");
+endpoint.setCxfRsEndpointConfigurer(new 
MyCxfRsEndpointConfigurer());
+
+from("direct:start")
+.to(endpoint)
+.to("mock:end");
+
+from("jetty:http://localhost:8000?matchOnUriPrefix=true;)
+.to("mock:result")
+.process(exchange -> exchange.getIn().setBody(new 
Customer()));
+}
+};
+}
+
+@Test
+public void testCxfRsEndpoinConfigurerProxyApi() throws 
InterruptedException {
+

[jira] [Commented] (CAMEL-12399) CxfRsProducer doesn't configure CxfRsEndpointConfigurer while using the Proxy API

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-12399:


Github user ffang closed the pull request at:

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


> CxfRsProducer doesn't configure CxfRsEndpointConfigurer while using the Proxy 
> API
> -
>
> Key: CAMEL-12399
> URL: https://issues.apache.org/jira/browse/CAMEL-12399
> Project: Camel
>  Issue Type: Bug
>  Components: camel-cxfrs
>Affects Versions: 2.21.0
>Reporter: Mike Schippers
>Assignee: Freeman Fang
>Priority: Major
>
> The CxfRsProducer doesn't configure a CxfRsEndpointConfigurer on the client 
> while using the Proxy API. When using the HTTP API this is working fine.
> So when i create an endpoint like this:
>  
> {code:java}
> CxfRsEndpoint endpoint = new CxfRsEndpoint(); 
> endpoint.setCxfRsEndpointConfigurer(new MyCxfRsEndpointConfigurer());
> {code}
>  
> {code:java}
> public static class MyCxfRsEndpointConfigurer implements 
> CxfRsEndpointConfigurer {
> @Override
> public void configure(AbstractJAXRSFactoryBean factoryBean) {
> }
> @Override
> public void configureClient(Client client) {
> client.header("foo", "bar");
> }
> @Override
> public void configureServer(Server server) {
> }
> }
> {code}
> In case i use the HTTP API the header "foo" is sent but not when i use the 
> Proxy API.



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

[jira] [Resolved] (CAMEL-12408) camel-cxf feature should not be tied to cxf-http-jetty feature

[Freeman Fang (JIRA)]

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

Freeman Fang resolved CAMEL-12408.
--
Resolution: Fixed

> camel-cxf feature should not be tied to cxf-http-jetty feature
> --
>
> Key: CAMEL-12408
> URL: https://issues.apache.org/jira/browse/CAMEL-12408
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-cxf, osgi
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>Priority: Major
> Fix For: 2.22.0
>
>
> should use cxf-http-provider instead, so that can use any http transport from 
> CXF (like jetty or undertow) in the underlying OSGi container



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

[jira] [Commented] (CAMEL-12378) Spring Boot 2 - Fix the camel-example-spring-cloud-servicecall

[Tomohisa Igarashi (JIRA)]

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

Tomohisa Igarashi commented on CAMEL-12378:
---

So in 1.x, the instanceId is generated from ApplicationContext.getId() which 
has default value, but in 2.0 it's generated from spring.application.name or 
spring.application.instance_id where they are null if not explicitly specified. 
So specifying one of them looks legit at least for now.

> Spring Boot 2 - Fix the camel-example-spring-cloud-servicecall
> --
>
> Key: CAMEL-12378
> URL: https://issues.apache.org/jira/browse/CAMEL-12378
> Project: Camel
>  Issue Type: Sub-task
>Reporter: Claus Ibsen
>Assignee: Tomohisa Igarashi
>Priority: Major
> Fix For: 2.22.0
>
>
> This example fails with starting the consumer. Some weird SB classpath 
> problem.



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

[jira] [Updated] (CAMEL-12409) Temporary revert CAMEL-12104 Unintuitive default cxf timeout behavior

[Peter Palaga (JIRA)]

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

Peter Palaga updated CAMEL-12409:
-
Summary: Temporary revert CAMEL-12104 Unintuitive default cxf timeout 
behavior  (was: camel-cxf - Temporary disable the new isTimeout API as its a 
breaking API change in CXF)

> Temporary revert CAMEL-12104 Unintuitive default cxf timeout behavior
> -
>
> Key: CAMEL-12409
> URL: https://issues.apache.org/jira/browse/CAMEL-12409
> Project: Camel
>  Issue Type: Task
>  Components: camel-cxf
>Reporter: Claus Ibsen
>Assignee: Peter Palaga
>Priority: Major
> Fix For: 2.22.0
>
>
> There is a problem with some Camel related projects that follow master branch 
> that cannot upgrade to CXF 3.2.4 at this time. We can therefore temporary go 
> back to avoid using the new isTimeout API on CXF 3.2.3 onwards, and then add 
> this back to camel-cxf  when twe are getting closed down for Camel 2.22 
> release.
> There was an API change in CXF 3.2.3 onwards started by CAMEL-12104



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

[jira] [Assigned] (CAMEL-12409) camel-cxf - Temporary disable the new isTimeout API as its a breaking API change in CXF

[Claus Ibsen (JIRA)]

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

Claus Ibsen reassigned CAMEL-12409:
---

Assignee: Peter Palaga

> camel-cxf - Temporary disable the new isTimeout API as its a breaking API 
> change in CXF
> ---
>
> Key: CAMEL-12409
> URL: https://issues.apache.org/jira/browse/CAMEL-12409
> Project: Camel
>  Issue Type: Task
>  Components: camel-cxf
>Reporter: Claus Ibsen
>Assignee: Peter Palaga
>Priority: Major
> Fix For: 2.22.0
>
>
> There is a problem with some Camel related projects that follow master branch 
> that cannot upgrade to CXF 3.2.4 at this time. We can therefore temporary go 
> back to avoid using the new isTimeout API on CXF 3.2.3 onwards, and then add 
> this back to camel-cxf  when twe are getting closed down for Camel 2.22 
> release.
> There was an API change in CXF 3.2.3 onwards started by CAMEL-12104



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

[jira] [Updated] (CAMEL-12409) camel-cxf - Temporary disable the new isTimeout API as its a breaking API change in CXF

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-12409:

Description: 
There is a problem with some Camel related projects that follow master branch 
that cannot upgrade to CXF 3.2.4 at this time. We can therefore temporary go 
back to avoid using the new isTimeout API on CXF 3.2.3 onwards, and then add 
this back to camel-cxf  when twe are getting closed down for Camel 2.22 release.

There was an API change in CXF 3.2.3 onwards started by CAMEL-12104

  was:
There is a problem with some Camel related projects that follow master branch 
that cannot upgrade to CXF 3.2.4 at this time. We can therefore temporary go 
back to CXF 3.2.2, and then go back to CXF 3.2.4 later when they are ready or 
when we are getting closed down for Camel 2.22 release.

There was an API change in CXF 3.2.3 onwards started by CAMEL-12104


> camel-cxf - Temporary disable the new isTimeout API as its a breaking API 
> change in CXF
> ---
>
> Key: CAMEL-12409
> URL: https://issues.apache.org/jira/browse/CAMEL-12409
> Project: Camel
>  Issue Type: Task
>  Components: camel-cxf
>Reporter: Claus Ibsen
>Priority: Major
> Fix For: 2.22.0
>
>
> There is a problem with some Camel related projects that follow master branch 
> that cannot upgrade to CXF 3.2.4 at this time. We can therefore temporary go 
> back to avoid using the new isTimeout API on CXF 3.2.3 onwards, and then add 
> this back to camel-cxf  when twe are getting closed down for Camel 2.22 
> release.
> There was an API change in CXF 3.2.3 onwards started by CAMEL-12104



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

[jira] [Updated] (CAMEL-12409) camel-cxf - Temporary disable the new isTimeout API as its a breaking API change in CXF

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-12409:

Summary: camel-cxf - Temporary disable the new isTimeout API as its a 
breaking API change in CXF  (was: Temporary go back to CXF 3.2.2)

> camel-cxf - Temporary disable the new isTimeout API as its a breaking API 
> change in CXF
> ---
>
> Key: CAMEL-12409
> URL: https://issues.apache.org/jira/browse/CAMEL-12409
> Project: Camel
>  Issue Type: Task
>  Components: camel-cxf
>Reporter: Claus Ibsen
>Priority: Major
> Fix For: 2.22.0
>
>
> There is a problem with some Camel related projects that follow master branch 
> that cannot upgrade to CXF 3.2.4 at this time. We can therefore temporary go 
> back to CXF 3.2.2, and then go back to CXF 3.2.4 later when they are ready or 
> when we are getting closed down for Camel 2.22 release.
> There was an API change in CXF 3.2.3 onwards started by CAMEL-12104



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

[jira] [Created] (CAMEL-12409) Temporary go back to CXF 3.2.2

[Claus Ibsen (JIRA)]

Claus Ibsen created CAMEL-12409:
---

 Summary: Temporary go back to CXF 3.2.2
 Key: CAMEL-12409
 URL: https://issues.apache.org/jira/browse/CAMEL-12409
 Project: Camel
  Issue Type: Task
  Components: camel-cxf
Reporter: Claus Ibsen
 Fix For: 2.22.0


There is a problem with some Camel related projects that follow master branch 
that cannot upgrade to CXF 3.2.4 at this time. We can therefore temporary go 
back to CXF 3.2.2, and then go back to CXF 3.2.4 later when they are ready or 
when we are getting closed down for Camel 2.22 release.

There was an API change in CXF 3.2.3 onwards started by CAMEL-12104



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

[jira] [Updated] (CAMEL-12403) Documentation - Update build instructions to be per module

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-12403:

Fix Version/s: 2.22.0

> Documentation - Update build instructions to be per module
> --
>
> Key: CAMEL-12403
> URL: https://issues.apache.org/jira/browse/CAMEL-12403
> Project: Camel
>  Issue Type: Improvement
>  Components: documentation
>Reporter: Claus Ibsen
>Priority: Major
> Fix For: 2.22.0
>
>
> The build instructions talks about loading 100% of the source code in one 
> giant import in Eclipse. That should be rarely used. And that takes a lot of 
> memory and slows down Eclipse etc. Instead you import the component you work 
> on.
> See this PR
> https://github.com/apache/camel/pull/2267



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

[jira] [Commented] (CAMEL-12403) Documentation - Update build instructions to be per module

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-12403:
-

Thanks you that would be great. We love contributions

http://camel.apache.org/contributing

> Documentation - Update build instructions to be per module
> --
>
> Key: CAMEL-12403
> URL: https://issues.apache.org/jira/browse/CAMEL-12403
> Project: Camel
>  Issue Type: Improvement
>  Components: documentation
>Reporter: Claus Ibsen
>Priority: Major
> Fix For: 2.22.0
>
>
> The build instructions talks about loading 100% of the source code in one 
> giant import in Eclipse. That should be rarely used. And that takes a lot of 
> memory and slows down Eclipse etc. Instead you import the component you work 
> on.
> See this PR
> https://github.com/apache/camel/pull/2267



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

[jira] [Commented] (CAMEL-12403) Documentation - Update build instructions to be per module

[Satyajit Rakshit (JIRA)]

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

Satyajit Rakshit commented on CAMEL-12403:
--

shall I update the page for GC options along with build instruction on "import 
component/sub-modules rather than entire camel project".

> Documentation - Update build instructions to be per module
> --
>
> Key: CAMEL-12403
> URL: https://issues.apache.org/jira/browse/CAMEL-12403
> Project: Camel
>  Issue Type: Improvement
>  Components: documentation
>Reporter: Claus Ibsen
>Priority: Major
>
> The build instructions talks about loading 100% of the source code in one 
> giant import in Eclipse. That should be rarely used. And that takes a lot of 
> memory and slows down Eclipse etc. Instead you import the component you work 
> on.
> See this PR
> https://github.com/apache/camel/pull/2267



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

[jira] [Updated] (CAMEL-12408) camel-cxf feature should not be tied to cxf-http-jetty feature

[Freeman Fang (JIRA)]

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

Freeman Fang updated CAMEL-12408:
-
Description: should use cxf-http-provider instead, so that can use any http 
transport from CXF (like jetty or undertow) in the underlying OSGi container  
(was: should use cxf-http-provider instead, so that can use any http OSGI 
service implementation(like jetty or undertow) from the underlying OSGi 
container)

> camel-cxf feature should not be tied to cxf-http-jetty feature
> --
>
> Key: CAMEL-12408
> URL: https://issues.apache.org/jira/browse/CAMEL-12408
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-cxf, osgi
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>Priority: Major
> Fix For: 2.22.0
>
>
> should use cxf-http-provider instead, so that can use any http transport from 
> CXF (like jetty or undertow) in the underlying OSGi container



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

[jira] [Updated] (CAMEL-12407) camel-olingo4-api should explicitly depend on commons-io

[Peter Palaga (JIRA)]

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

Peter Palaga updated CAMEL-12407:
-
Affects Version/s: 2.22.0

> camel-olingo4-api should explicitly depend on commons-io
> 
>
> Key: CAMEL-12407
> URL: https://issues.apache.org/jira/browse/CAMEL-12407
> Project: Camel
>  Issue Type: Bug
>  Components: camel-olingo4
>Affects Versions: 2.21.1, 2.22.0
>Reporter: Peter Palaga
>Assignee: Peter Palaga
>Priority: Major
>
> Otherwise, routes fail with ClassNotFoundException IOUtils, e.g. when running 
> Olingo4IntegrationTest in WildFly Camel



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

[jira] [Updated] (CAMEL-12408) camel-cxf feature should not be tied to cxf-http-jetty feature

[Freeman Fang (JIRA)]

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

Freeman Fang updated CAMEL-12408:
-
Component/s: osgi
 camel-cxf

> camel-cxf feature should not be tied to cxf-http-jetty feature
> --
>
> Key: CAMEL-12408
> URL: https://issues.apache.org/jira/browse/CAMEL-12408
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-cxf, osgi
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>Priority: Major
>
> should use cxf-http-provider instead, so that can use any http OSGI service 
> implementation(like jetty or undertow) from the underlying OSGi container



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

[jira] [Commented] (CAMEL-12403) Documentation - Update build instructions to be per module

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-12403:
-

I dont think you need any of these special GC options, I just use 

MAVEN_OPTS="-Xmx3500m"

> Documentation - Update build instructions to be per module
> --
>
> Key: CAMEL-12403
> URL: https://issues.apache.org/jira/browse/CAMEL-12403
> Project: Camel
>  Issue Type: Improvement
>  Components: documentation
>Reporter: Claus Ibsen
>Priority: Major
>
> The build instructions talks about loading 100% of the source code in one 
> giant import in Eclipse. That should be rarely used. And that takes a lot of 
> memory and slows down Eclipse etc. Instead you import the component you work 
> on.
> See this PR
> https://github.com/apache/camel/pull/2267



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

[jira] [Updated] (CAMEL-12408) camel-cxf feature should not be tied to cxf-http-jetty feature

[Freeman Fang (JIRA)]

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

Freeman Fang updated CAMEL-12408:
-
Fix Version/s: 2.22.0

> camel-cxf feature should not be tied to cxf-http-jetty feature
> --
>
> Key: CAMEL-12408
> URL: https://issues.apache.org/jira/browse/CAMEL-12408
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-cxf, osgi
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>Priority: Major
> Fix For: 2.22.0
>
>
> should use cxf-http-provider instead, so that can use any http OSGI service 
> implementation(like jetty or undertow) from the underlying OSGi container



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

[jira] [Updated] (CAMEL-12407) camel-olingo4-api should explicitly depend on commons-io

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-12407:

Fix Version/s: 2.22.0
   2.21.1

> camel-olingo4-api should explicitly depend on commons-io
> 
>
> Key: CAMEL-12407
> URL: https://issues.apache.org/jira/browse/CAMEL-12407
> Project: Camel
>  Issue Type: Bug
>  Components: camel-olingo4
>Affects Versions: 2.21.0
>Reporter: Peter Palaga
>Assignee: Peter Palaga
>Priority: Major
> Fix For: 2.21.1, 2.22.0
>
>
> Otherwise, routes fail with ClassNotFoundException IOUtils, e.g. when running 
> Olingo4IntegrationTest in WildFly Camel



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

[jira] [Assigned] (CAMEL-12399) CxfRsProducer doesn't configure CxfRsEndpointConfigurer while using the Proxy API

[Freeman Fang (JIRA)]

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

Freeman Fang reassigned CAMEL-12399:


Assignee: Freeman Fang

> CxfRsProducer doesn't configure CxfRsEndpointConfigurer while using the Proxy 
> API
> -
>
> Key: CAMEL-12399
> URL: https://issues.apache.org/jira/browse/CAMEL-12399
> Project: Camel
>  Issue Type: Bug
>  Components: camel-cxfrs
>Affects Versions: 2.21.0
>Reporter: Mike Schippers
>Assignee: Freeman Fang
>Priority: Major
>
> The CxfRsProducer doesn't configure a CxfRsEndpointConfigurer on the client 
> while using the Proxy API. When using the HTTP API this is working fine.
> So when i create an endpoint like this:
>  
> {code:java}
> CxfRsEndpoint endpoint = new CxfRsEndpoint(); 
> endpoint.setCxfRsEndpointConfigurer(new MyCxfRsEndpointConfigurer());
> {code}
>  
> {code:java}
> public static class MyCxfRsEndpointConfigurer implements 
> CxfRsEndpointConfigurer {
> @Override
> public void configure(AbstractJAXRSFactoryBean factoryBean) {
> }
> @Override
> public void configureClient(Client client) {
> client.header("foo", "bar");
> }
> @Override
> public void configureServer(Server server) {
> }
> }
> {code}
> In case i use the HTTP API the header "foo" is sent but not when i use the 
> Proxy API.



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

[jira] [Created] (CAMEL-12408) camel-cxf feature should not be tied to cxf-http-jetty feature

[Freeman Fang (JIRA)]

Freeman Fang created CAMEL-12408:


 Summary: camel-cxf feature should not be tied to cxf-http-jetty 
feature
 Key: CAMEL-12408
 URL: https://issues.apache.org/jira/browse/CAMEL-12408
 Project: Camel
  Issue Type: Improvement
Reporter: Freeman Fang


should use cxf-http-provider instead, so that can use any http OSGI service 
implementation(like jetty or undertow) from the underlying OSGi container



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

[jira] [Assigned] (CAMEL-12408) camel-cxf feature should not be tied to cxf-http-jetty feature

[Freeman Fang (JIRA)]

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

Freeman Fang reassigned CAMEL-12408:


Assignee: Freeman Fang

> camel-cxf feature should not be tied to cxf-http-jetty feature
> --
>
> Key: CAMEL-12408
> URL: https://issues.apache.org/jira/browse/CAMEL-12408
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-cxf, osgi
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>Priority: Major
>
> should use cxf-http-provider instead, so that can use any http OSGI service 
> implementation(like jetty or undertow) from the underlying OSGi container



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

[jira] [Resolved] (CAMEL-12407) camel-olingo4-api should explicitly depend on commons-io

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-12407.
-
Resolution: Fixed

> camel-olingo4-api should explicitly depend on commons-io
> 
>
> Key: CAMEL-12407
> URL: https://issues.apache.org/jira/browse/CAMEL-12407
> Project: Camel
>  Issue Type: Bug
>  Components: camel-olingo4
>Affects Versions: 2.21.0
>Reporter: Peter Palaga
>Assignee: Peter Palaga
>Priority: Major
> Fix For: 2.21.1, 2.22.0
>
>
> Otherwise, routes fail with ClassNotFoundException IOUtils, e.g. when running 
> Olingo4IntegrationTest in WildFly Camel



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

[jira] [Commented] (CAMEL-12407) camel-olingo4-api should explicitly depend on commons-io

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-12407:


Github user davsclaus closed the pull request at:

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


> camel-olingo4-api should explicitly depend on commons-io
> 
>
> Key: CAMEL-12407
> URL: https://issues.apache.org/jira/browse/CAMEL-12407
> Project: Camel
>  Issue Type: Bug
>  Components: camel-olingo4
>Affects Versions: 2.21.0
>Reporter: Peter Palaga
>Assignee: Peter Palaga
>Priority: Major
> Fix For: 2.21.1, 2.22.0
>
>
> Otherwise, routes fail with ClassNotFoundException IOUtils, e.g. when running 
> Olingo4IntegrationTest in WildFly Camel



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

[jira] [Commented] (CAMEL-12407) camel-olingo4-api should explicitly depend on commons-io

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-12407:


ppalaga opened a new pull request #2270: CAMEL-12407: camel-olingo4-api should 
explicitly depend on commons-io
URL: https://github.com/apache/camel/pull/2270
 
 
   This should please be ported to `camel-2.21.x` too


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-olingo4-api should explicitly depend on commons-io
> 
>
> Key: CAMEL-12407
> URL: https://issues.apache.org/jira/browse/CAMEL-12407
> Project: Camel
>  Issue Type: Bug
>  Components: camel-olingo4
>Affects Versions: 2.21.0
>Reporter: Peter Palaga
>Assignee: Peter Palaga
>Priority: Major
> Fix For: 2.21.1, 2.22.0
>
>
> Otherwise, routes fail with ClassNotFoundException IOUtils, e.g. when running 
> Olingo4IntegrationTest in WildFly Camel



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

[jira] [Commented] (CAMEL-12407) camel-olingo4-api should explicitly depend on commons-io

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-12407:


davsclaus closed pull request #2270: CAMEL-12407: camel-olingo4-api should 
explicitly depend on commons-io
URL: https://github.com/apache/camel/pull/2270
 
 
   

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-olingo4/camel-olingo4-api/pom.xml 
b/components/camel-olingo4/camel-olingo4-api/pom.xml
index 30a6220efba..d41bfb94d3d 100644
--- a/components/camel-olingo4/camel-olingo4-api/pom.xml
+++ b/components/camel-olingo4/camel-olingo4-api/pom.xml
@@ -58,17 +58,22 @@
   odata-server-core
   ${olingo4-version}
 
-
+
 
   org.apache.camel
   camel-core
 
-
+
 
   org.apache.httpcomponents
   httpasyncclient
 
 
+
+  commons-io
+  commons-io
+
+
 
 
   org.apache.logging.log4j


 


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-olingo4-api should explicitly depend on commons-io
> 
>
> Key: CAMEL-12407
> URL: https://issues.apache.org/jira/browse/CAMEL-12407
> Project: Camel
>  Issue Type: Bug
>  Components: camel-olingo4
>Affects Versions: 2.21.0
>Reporter: Peter Palaga
>Assignee: Peter Palaga
>Priority: Major
> Fix For: 2.21.1, 2.22.0
>
>
> Otherwise, routes fail with ClassNotFoundException IOUtils, e.g. when running 
> Olingo4IntegrationTest in WildFly Camel



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

[jira] [Commented] (CAMEL-12407) camel-olingo4-api should explicitly depend on commons-io

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-12407:


GitHub user ppalaga opened a pull request:

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

CAMEL-12407: camel-olingo4-api should explicitly depend on commons-io

This should please be ported to `camel-2.21.x` too

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

$ git pull https://github.com/ppalaga/camel CAMEL-12407

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

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


commit c20cf523de8af4a74442afe2f1f52081443c
Author: Peter Palaga 
Date:   2018-03-26T11:53:57Z

CAMEL-12407: camel-olingo4-api should explicitly depend on commons-io




> camel-olingo4-api should explicitly depend on commons-io
> 
>
> Key: CAMEL-12407
> URL: https://issues.apache.org/jira/browse/CAMEL-12407
> Project: Camel
>  Issue Type: Bug
>  Components: camel-olingo4
>Affects Versions: 2.21.0
>Reporter: Peter Palaga
>Assignee: Peter Palaga
>Priority: Major
> Fix For: 2.21.1, 2.22.0
>
>
> Otherwise, routes fail with ClassNotFoundException IOUtils, e.g. when running 
> Olingo4IntegrationTest in WildFly Camel



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

[jira] [Updated] (CAMEL-12407) camel-olingo4-api should explicitly depend on commons-io

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-12407:

Affects Version/s: (was: 2.21.1)
   (was: 2.22.0)
   2.21.0

> camel-olingo4-api should explicitly depend on commons-io
> 
>
> Key: CAMEL-12407
> URL: https://issues.apache.org/jira/browse/CAMEL-12407
> Project: Camel
>  Issue Type: Bug
>  Components: camel-olingo4
>Affects Versions: 2.21.0
>Reporter: Peter Palaga
>Assignee: Peter Palaga
>Priority: Major
> Fix For: 2.21.1, 2.22.0
>
>
> Otherwise, routes fail with ClassNotFoundException IOUtils, e.g. when running 
> Olingo4IntegrationTest in WildFly Camel



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

[jira] [Updated] (CAMEL-12407) camel-olingo4-api should explicitly depend on commons-io

[Peter Palaga (JIRA)]

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

Peter Palaga updated CAMEL-12407:
-
Affects Version/s: (was: 2.21.0)
   2.21.1

> camel-olingo4-api should explicitly depend on commons-io
> 
>
> Key: CAMEL-12407
> URL: https://issues.apache.org/jira/browse/CAMEL-12407
> Project: Camel
>  Issue Type: Bug
>  Components: camel-olingo4
>Affects Versions: 2.21.1
>Reporter: Peter Palaga
>Assignee: Peter Palaga
>Priority: Major
>
> Otherwise, routes fail with ClassNotFoundException IOUtils, e.g. when running 
> Olingo4IntegrationTest in WildFly Camel



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

[jira] [Created] (CAMEL-12407) camel-olingo4-api should explicitly depend on commons-io

[Peter Palaga (JIRA)]

Peter Palaga created CAMEL-12407:


 Summary: camel-olingo4-api should explicitly depend on commons-io
 Key: CAMEL-12407
 URL: https://issues.apache.org/jira/browse/CAMEL-12407
 Project: Camel
  Issue Type: Bug
  Components: camel-olingo4
Affects Versions: 2.21.0
Reporter: Peter Palaga
Assignee: Peter Palaga


Otherwise, routes fail with ClassNotFoundException IOUtils, e.g. when running 
Olingo4IntegrationTest in WildFly Camel



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

[jira] [Resolved] (CAMEL-12406) camel-dropbox - Need to use force to check for file/folder exists

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-12406.
-
Resolution: Fixed

> camel-dropbox - Need to use force to check for file/folder exists
> -
>
> Key: CAMEL-12406
> URL: https://issues.apache.org/jira/browse/CAMEL-12406
> Project: Camel
>  Issue Type: Bug
>  Components: camel-dropbox
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 2.20.4, 2.21.1, 2.22.0
>
>
> See this PR
> https://github.com/apache/camel/pull/2269



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

[jira] [Created] (CAMEL-12406) camel-dropbox - Need to use force to check for file/folder exists

[Claus Ibsen (JIRA)]

Claus Ibsen created CAMEL-12406:
---

 Summary: camel-dropbox - Need to use force to check for 
file/folder exists
 Key: CAMEL-12406
 URL: https://issues.apache.org/jira/browse/CAMEL-12406
 Project: Camel
  Issue Type: Bug
  Components: camel-dropbox
Reporter: Claus Ibsen
Assignee: Claus Ibsen
 Fix For: 2.20.4, 2.21.1, 2.22.0


See this PR

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



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

[jira] [Commented] (CAMEL-12288) Need method call feature for milo client component

[Jens Reimann (JIRA)]

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

Jens Reimann commented on CAMEL-12288:
--

Hi [~herleraja] … the changes have been merged to the "master" branch and you 
should be able to use Camel "2.22.0-SNAPSHOT" for testing.

> Need method call feature for milo client component
> --
>
> Key: CAMEL-12288
> URL: https://issues.apache.org/jira/browse/CAMEL-12288
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-milo
>Affects Versions: 2.20.2
>Reporter: Amritha Raj Herle
>Assignee: Jens Reimann
>Priority: Major
> Fix For: 2.22.0
>
> Attachments: image.png
>
>
> I'm using Apache camel Milo component for one of my project. Where I'm  
> having a use-case scenario in which i need to CALL THE METHOD (for example 
> *START*(), *STOP*()) with some input parameter (ex:*START("APPLICATIONNAME")* 
> ) which returns some output parameter. (*StatusCode*, or *ErrorCode*). Please 
> note that the input and output parameter can be complex data type (Not just 
> int/double... ).
>   
> [ SceenShot of my sample server ]
>  !image.png!
>   
>  I have tested the read node functionality with the node id and the 
> namespace. The milo-client component will be more better suited if it provide 
> the call functionality.
>   
>  Please do look into it.
>   



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

[jira] [Commented] (CAMEL-12404) Upgrade jackson-databind minor version in Camel 2.20.x and 2.21.x

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino commented on CAMEL-12404:
--

I had to revert this, because only jackson-databind has been released with that 
version, so we'll have to specify the databind version only.

> Upgrade jackson-databind minor version in Camel 2.20.x and 2.21.x
> -
>
> Key: CAMEL-12404
> URL: https://issues.apache.org/jira/browse/CAMEL-12404
> Project: Camel
>  Issue Type: Improvement
>Reporter: Darius Cooper
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 2.20.4, 2.21.1
>
>
> jackson-databind.jar v2.8.10 has some reported vulnerabilities.
> The latest minor release has a fix
> Upgrade to v2.8.11.1 of jackson-databind



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

[jira] [Reopened] (CAMEL-12404) Upgrade jackson-databind minor version in Camel 2.20.x and 2.21.x

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino reopened CAMEL-12404:
--

> Upgrade jackson-databind minor version in Camel 2.20.x and 2.21.x
> -
>
> Key: CAMEL-12404
> URL: https://issues.apache.org/jira/browse/CAMEL-12404
> Project: Camel
>  Issue Type: Improvement
>Reporter: Darius Cooper
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 2.20.4, 2.21.1
>
>
> jackson-databind.jar v2.8.10 has some reported vulnerabilities.
> The latest minor release has a fix
> Upgrade to v2.8.11.1 of jackson-databind



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

[jira] [Resolved] (CAMEL-12404) Upgrade jackson-databind minor version in Camel 2.20.x and 2.21.x

[Andrea Cosentino (JIRA)]

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

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

> Upgrade jackson-databind minor version in Camel 2.20.x and 2.21.x
> -
>
> Key: CAMEL-12404
> URL: https://issues.apache.org/jira/browse/CAMEL-12404
> Project: Camel
>  Issue Type: Improvement
>Reporter: Darius Cooper
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 2.20.4, 2.21.1
>
>
> jackson-databind.jar v2.8.10 has some reported vulnerabilities.
> The latest minor release has a fix
> Upgrade to v2.8.11.1 of jackson-databind



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

[jira] [Commented] (CAMEL-12404) Upgrade jackson-databind minor version in Camel 2.20.x and 2.21.x

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino commented on CAMEL-12404:
--

https://github.com/apache/camel/commit/6e30776c3e34fd1bf8e1ec7c11b34d2c7c986806

> Upgrade jackson-databind minor version in Camel 2.20.x and 2.21.x
> -
>
> Key: CAMEL-12404
> URL: https://issues.apache.org/jira/browse/CAMEL-12404
> Project: Camel
>  Issue Type: Improvement
>Reporter: Darius Cooper
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 2.20.4, 2.21.1
>
>
> jackson-databind.jar v2.8.10 has some reported vulnerabilities.
> The latest minor release has a fix
> Upgrade to v2.8.11.1 of jackson-databind



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

[jira] [Updated] (CAMEL-12404) Upgrade jackson-databind minor version in Camel 2.20.x and 2.21.x

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino updated CAMEL-12404:
-
Fix Version/s: 2.21.1

> Upgrade jackson-databind minor version in Camel 2.20.x and 2.21.x
> -
>
> Key: CAMEL-12404
> URL: https://issues.apache.org/jira/browse/CAMEL-12404
> Project: Camel
>  Issue Type: Improvement
>Reporter: Darius Cooper
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 2.20.4, 2.21.1
>
>
> jackson-databind.jar v2.8.10 has some reported vulnerabilities.
> The latest minor release has a fix
> Upgrade to v2.8.11.1 of jackson-databind



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

[jira] [Commented] (CAMEL-12404) Upgrade jackson-databind minor version in Camel 2.20.x and 2.21.x

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino commented on CAMEL-12404:
--

https://github.com/apache/camel/commit/1f12c7597b50a65893af12d04fd061270363e6af

> Upgrade jackson-databind minor version in Camel 2.20.x and 2.21.x
> -
>
> Key: CAMEL-12404
> URL: https://issues.apache.org/jira/browse/CAMEL-12404
> Project: Camel
>  Issue Type: Improvement
>Reporter: Darius Cooper
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 2.20.4
>
>
> jackson-databind.jar v2.8.10 has some reported vulnerabilities.
> The latest minor release has a fix
> Upgrade to v2.8.11.1 of jackson-databind



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

[jira] [Assigned] (CAMEL-12404) Upgrade jackson-databind minor version in Camel 2.20.x and 2.21.x

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino reassigned CAMEL-12404:


Assignee: Andrea Cosentino

> Upgrade jackson-databind minor version in Camel 2.20.x and 2.21.x
> -
>
> Key: CAMEL-12404
> URL: https://issues.apache.org/jira/browse/CAMEL-12404
> Project: Camel
>  Issue Type: Improvement
>Reporter: Darius Cooper
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 2.20.4
>
>
> jackson-databind.jar v2.8.10 has some reported vulnerabilities.
> The latest minor release has a fix
> Upgrade to v2.8.11.1 of jackson-databind



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