[jira] (CAMEL-10772) Spring POJO @Produce @Consume Remoting auto detect binding usage improvement

2017-01-31 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CAMEL-10772:


Github user asfgit closed the pull request at:

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


> Spring POJO @Produce @Consume Remoting auto detect binding usage improvement
> 
>
> Key: CAMEL-10772
> URL: https://issues.apache.org/jira/browse/CAMEL-10772
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core, camel-spring
> Environment: Java 1.8, Spring
>Reporter: Christopher Harris
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.19.0
>
>
> Convention over configuration
> Improvement in AbstractCamelInvocationHandler.invokeProxy, to auto detect if 
> the invocation is binding capable. 
> It is determined by checking the parameter count and annotation types on each 
> parameter, and only use binding if it is capable. Otherwise fallback on to 
> the old bean invocation way.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] (CAMEL-10772) Spring POJO @Produce @Consume Remoting auto detect binding usage improvement

2017-01-31 Thread Claus Ibsen (JIRA) 

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

Claus Ibsen resolved CAMEL-10772.
-
Resolution: Fixed

Thanks for the PR

> Spring POJO @Produce @Consume Remoting auto detect binding usage improvement
> 
>
> Key: CAMEL-10772
> URL: https://issues.apache.org/jira/browse/CAMEL-10772
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core, camel-spring
> Environment: Java 1.8, Spring
>Reporter: Christopher Harris
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.19.0
>
>
> Convention over configuration
> Improvement in AbstractCamelInvocationHandler.invokeProxy, to auto detect if 
> the invocation is binding capable. 
> It is determined by checking the parameter count and annotation types on each 
> parameter, and only use binding if it is capable. Otherwise fallback on to 
> the old bean invocation way.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] (CAMEL-10772) Spring POJO @Produce @Consume Remoting auto detect binding usage improvement

2017-01-31 Thread Claus Ibsen (JIRA) 

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

Claus Ibsen updated CAMEL-10772:

Fix Version/s: 2.19.0

> Spring POJO @Produce @Consume Remoting auto detect binding usage improvement
> 
>
> Key: CAMEL-10772
> URL: https://issues.apache.org/jira/browse/CAMEL-10772
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core, camel-spring
> Environment: Java 1.8, Spring
>Reporter: Christopher Harris
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.19.0
>
>
> Convention over configuration
> Improvement in AbstractCamelInvocationHandler.invokeProxy, to auto detect if 
> the invocation is binding capable. 
> It is determined by checking the parameter count and annotation types on each 
> parameter, and only use binding if it is capable. Otherwise fallback on to 
> the old bean invocation way.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] (CAMEL-10772) Spring POJO @Produce @Consume Remoting auto detect binding usage improvement

2017-01-31 Thread Claus Ibsen (JIRA) 

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

Claus Ibsen updated CAMEL-10772:

Affects Version/s: (was: 2.19.0)
   (was: 2.18.0)
   (was: 2.17.0)
   (was: 2.16.0)

> Spring POJO @Produce @Consume Remoting auto detect binding usage improvement
> 
>
> Key: CAMEL-10772
> URL: https://issues.apache.org/jira/browse/CAMEL-10772
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core, camel-spring
> Environment: Java 1.8, Spring
>Reporter: Christopher Harris
>Priority: Minor
>
> Convention over configuration
> Improvement in AbstractCamelInvocationHandler.invokeProxy, to auto detect if 
> the invocation is binding capable. 
> It is determined by checking the parameter count and annotation types on each 
> parameter, and only use binding if it is capable. Otherwise fallback on to 
> the old bean invocation way.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] (CAMEL-10523) Make Test launchable as JUnit Test from IDEs

2017-01-31 Thread Claus Ibsen (JIRA) 

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

Claus Ibsen resolved CAMEL-10523.
-
   Resolution: Fixed
 Assignee: Claus Ibsen
Fix Version/s: (was: Future)
   2.19.0

Moved the doc tests to itest

> Make Test launchable as JUnit Test from IDEs 
> -
>
> Key: CAMEL-10523
> URL: https://issues.apache.org/jira/browse/CAMEL-10523
> Project: Camel
>  Issue Type: Test
>  Components: build system
>Affects Versions: 2.18.0
>Reporter: Aurelien Pupier
>Assignee: Claus Ibsen
> Fix For: 2.19.0
>
>
> Currently several tests are failing when launching them from Eclipse IDE, I 
> spotted 2 categories for now:
> - several MBean tests
> - test trying to access some *.html generated file
> for instance  for instance with 
> org.apache.camel.component.dataset.DataSetComponentConfigurationAndDocumentationTest.testComponentDocumentation()
>  it is searching for
> org/apache/camel/component/dataset/dataset.html
> Gain:
> - enter the 21st century
> - faster development
> - open ways to leverage usage of Code coverage tools, easier debugging and 
> real-time test execution



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] (CAMEL-10542) DataFormat from registry is used for every dataformat operation (marshal/unmarshal)

2017-01-31 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CAMEL-10542:


GitHub user lburgazzoli opened a pull request:

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

CAMEL-10542: DataFormat from registry is used for every dataformat 
operation (marshal/unmarshal)

I'm opening this PR for review as there are some changes on CamelContext 
level so I'd like to gather some feedback.

As today the DataFormat resolution works as follow:
1. search int the registry if a DataFormat instance exists for a given name
2. if not found in registry create a new one from the resources 
(META-INF/services/...)

This my cause issues as per CAMEL-10542

The proposed solution introduces a new DataFormatFactory and a new method 
to DataFormatResolver to have a way to explicit request for a new instance so 
it looks like:

```java
public interface DataFormatResolver {
// Resolve using registry then fallback to createDataFormat
DataFormat resolveDataFormat(String name, CamelContext context);

// Resolve factory using registry or fallback to resources
DataFormat createDataFormat(String name, CamelContext context);
} 
```

Model's DataFormatDefinition is now using createDataFormat except for 
CustomDataFormat which indeed is supposed to eventually share the same data 
format. 

I still need to implement some stuffs but the basic concept is here.
Any feedback would be really appreciated.


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

$ git pull https://github.com/lburgazzoli/apache-camel CAMEL-10542

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

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






> DataFormat from registry is used for every dataformat operation 
> (marshal/unmarshal)
> ---
>
> Key: CAMEL-10542
> URL: https://issues.apache.org/jira/browse/CAMEL-10542
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
> Fix For: 2.18.3, 2.19.0
>
>
> While working on an issue related to spring-boot I found out that if a data 
> format is registered in camel registry with the same name as the one camel 
> looks-up with the help of DefaultDataFormatResolver, this object is then 
> re-configured for each data format definition so one definition may override 
> previous configuration with an undefined behavior.
> So assume you have an xml route definitions as:
> {code:xml}
> http://camel.apache.org/schema/spring;>
>   
> 
> 
>   
> 
>   
>   
> 
> 
>   
> 
>   
> 
> {code}
> And some code like:
> {code:java}
> InputStream is = getClass().getResourceAsStream("...");
> SimpleRegistry reg = new SimpleRegistry();
> reg.put("csv-dataformat", new CsvDataFormat());
> DefaultCamelContext ctx = new DefaultCamelContext(reg);
> ctx.addRouteDefinitions(ctx.loadRoutesDefinition(is).getRoutes());
> ctx.start();
> ProducerTemplate template = ctx.createProducerTemplate();
> String result = template.requestBody(
> "direct:marshal",
> Arrays.asList(Arrays.asList( "A1", "B1", "C1" )),
> String.class);
> assertEquals("A1,B1,C1", result);
> ctx.stop
> {code}
> Then this test fails with:
> {code}
> Expected :A1,B1,C1
> Actual   :A1;B1;C1
> {code}
> It fails because the object added to the SimpleRegistry is shared among the 
> two csv dataformats  so it is configured to have delimiter = ';' 
> For spring-boot this causes some issues as it registers data formats beans as 
> part of its auto-configuration magic thus if you do not set your own instance 
> of data format, any data format operation like marshal/unmarshal may not work 
> as expected. 
> - for spring-boot a solution would be to annotate auto configured data format 
> beans with prototype scope.
> - a more generic solution would be to make DataFormat Cloneable and clone the 
> bean found in the registry



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] (CAMEL-10771) CxfEndpoint shows WARNING altough endpoint-/port name is configured

2017-01-31 Thread ASF GitHub Bot (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ASF GitHub Bot commented on  CAMEL-10771 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: CxfEndpoint shows WARNING altough endpoint-/port name is configured  
 
 
 
 
 
 
 
 
 
 
Github user jochenr closed the pull request at: 
 https://github.com/apache/camel/pull/1433 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (CAMEL-10773) camel-swagger json files are not part of the camel-catalog

2017-01-31 Thread Claus Ibsen (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Claus Ibsen commented on  CAMEL-10773 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: camel-swagger json files are not part of the camel-catalog  
 
 
 
 
 
 
 
 
 
 
Any runtime should be able to override and provide their view of the catalog 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (CAMEL-10773) camel-swagger json files are not part of the camel-catalog

2017-01-31 Thread Thomas Diesler (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Diesler commented on  CAMEL-10773 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: camel-swagger json files are not part of the camel-catalog  
 
 
 
 
 
 
 
 
 
 
Should a given runtime catalog not report whether e.g. camel-swagger is supported? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (CAMEL-10766) Create a new camel-elasticsearch5 component for supporting ElasticSearch 5.x Java API

2017-01-31 Thread Dmitry Volodin (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dmitry Volodin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Camel /  CAMEL-10766 
 
 
 
  Create a new camel-elasticsearch5 component for supporting ElasticSearch 5.x Java API  
 
 
 
 
 
 
 
 
 

Change By:
 
 Dmitry Volodin 
 
 
 

Attachment:
 
 CAMEL-10766.patch 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (CAMEL-10769) Tika Component - Support Multi-Value Metadata

2017-01-31 Thread Bob Paulin (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bob Paulin closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Closed. Thanks! 
 
 
 
 
 
 
 
 
 
 Camel /  CAMEL-10769 
 
 
 
  Tika Component - Support Multi-Value Metadata  
 
 
 
 
 
 
 
 
 

Change By:
 
 Bob Paulin 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (CAMEL-10766) Create a new camel-elasticsearch5 component for supporting ElasticSearch 5.x Java API

2017-01-31 Thread Dmitry Volodin (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dmitry Volodin commented on  CAMEL-10766 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Create a new camel-elasticsearch5 component for supporting ElasticSearch 5.x Java API  
 
 
 
 
 
 
 
 
 
 
I've submitted a pull request on Github... 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (CAMEL-10766) Create a new camel-elasticsearch5 component for supporting ElasticSearch 5.x Java API

2017-01-31 Thread ASF GitHub Bot (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ASF GitHub Bot commented on  CAMEL-10766 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Create a new camel-elasticsearch5 component for supporting ElasticSearch 5.x Java API  
 
 
 
 
 
 
 
 
 
 
GitHub user dmvolod opened a pull request: 
 https://github.com/apache/camel/pull/1435 
 CAMEL-10766: Create a new camel-elasticsearch5 component for supporting ElasticSearch 5.x Java API 
 For backward compatibility we've migrated current camel-elasticsearch to the new camel-elasticsearch5. As $ {lucene-version} 
 was defined globally, it affected on both ElasticSearch API versions - 2.4.3 and 5.1.2 and one of the components doesn't work correctly. I removed global Apache Lucene library definition and place it to the dependent components. Please correct dependencies if needed. Also uploaded new component and all changes as patch. The following camel-elasticsearch functions were removed as ElasticSearch API deprecated (removed) features: 
 

consistencyLevel parameter (replaced with waitForActiveShards)
 

local JVM ES cluster running (not supported anymore)
 
 
You can merge this pull request into a Git repository by running: 
 $ git pull https://github.com/dmvolod/camel CAMEL-10766 
Alternatively you can review and apply these changes as the patch at: 
 https://github.com/apache/camel/pull/1435.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 #1435 
 
commit c95db786d08bed09ecf783b8c565be05d4fdd79e Author: Dmitry Volodin  Date: 2017-01-31T11:47:33Z 
 CAMEL-10766: Create a new camel-elasticsearch5 component for supporting ElasticSearch 5.x Java API 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 

[jira] (CAMEL-10774) camel-catalog - Include other kind of camel artifacts

2017-01-31 Thread Claus Ibsen (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Claus Ibsen created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Camel /  CAMEL-10774 
 
 
 
  camel-catalog - Include other kind of camel artifacts  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 camel-catalog 
 
 
 

Created:
 

 31/Jan/17 13:33 
 
 
 

Fix Versions:
 

 2.19.0 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Claus Ibsen 
 
 
 
 
 
 
 
 
 
 
We should find a way to add the other kind of Camel artifacts such as camel-swagger-java, camel-zipkin, and so on which are not a component, data format, language etc. 
See also 

CAMEL-10773
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[jira] (CAMEL-10773) camel-swagger json files are not part of the camel-catalog

2017-01-31 Thread Claus Ibsen (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Claus Ibsen resolved as Invalid 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
That is not a Camel component, data format, language or EIP pattern. Those are the ones the camel catalog has JSon information about. And then it holds all the website documentation from the adoc files and hence you can see those two .adoc files. 
There are other Camel artifacts like that such as  
camel-eclipse, camel-blueprint, camel-cdi, camel-jasypt, camel-rx, camel-scala, camel-servletlistener, camel-shiro, camel-stax, camel-swagger, camel-swagger-java, camel-test-*, camel-urlrewrite, camel-zipkin 
 
 
 
 
 
 
 
 
 
 Camel /  CAMEL-10773 
 
 
 
  camel-swagger json files are not part of the camel-catalog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Claus Ibsen 
 
 
 

Resolution:
 
 Invalid 
 
 
 

Status:
 
 Open Resolved 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (CAMEL-10773) camel-swagger json files are not part of the camel-catalog

2017-01-31 Thread Thomas Diesler (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Diesler updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Camel /  CAMEL-10773 
 
 
 
  camel-swagger json files are not part of the camel-catalog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Diesler 
 
 
 
 
 
 
 
 
 
 {code}$ jar -tf ~/.m2/repository/org/apache/camel/camel-catalog/2.18.2/camel-catalog-2.18.2.jar | grep swaggerorg/apache/camel/catalog/docs/swagger-java.adocorg/apache/camel/catalog/docs/swagger.adoc{code} Maybe this is true for other components, dataformats, languages too. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (CAMEL-10773) camel-swagger json files are not part of the camel-catalog

2017-01-31 Thread Thomas Diesler (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Diesler created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Camel /  CAMEL-10773 
 
 
 
  camel-swagger json files are not part of the camel-catalog  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 2.18.2 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 31/Jan/17 13:03 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Thomas Diesler 
 
 
 
 
 
 
 
 
 
 

 

$ jar -tf ~/.m2/repository/org/apache/camel/camel-catalog/2.18.2/camel-catalog-2.18.2.jar | grep swagger
org/apache/camel/catalog/docs/swagger-java.adoc
org/apache/camel/catalog/docs/swagger.adoc
 

 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[jira] (CAMEL-10771) CxfEndpoint shows WARNING altough endpoint-/port name is configured

2017-01-31 Thread Andrea Cosentino (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrea Cosentino updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Camel /  CAMEL-10771 
 
 
 
  CxfEndpoint shows WARNING altough endpoint-/port name is configured  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andrea Cosentino 
 
 
 

Fix Version/s:
 
 2.19.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (CAMEL-10771) CxfEndpoint shows WARNING altough endpoint-/port name is configured

2017-01-31 Thread Andrea Cosentino (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrea Cosentino resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Camel /  CAMEL-10771 
 
 
 
  CxfEndpoint shows WARNING altough endpoint-/port name is configured  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andrea Cosentino 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Open Resolved 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (CAMEL-10771) CxfEndpoint shows WARNING altough endpoint-/port name is configured

2017-01-31 Thread Andrea Cosentino (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrea Cosentino assigned an issue to Andrea Cosentino 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Camel /  CAMEL-10771 
 
 
 
  CxfEndpoint shows WARNING altough endpoint-/port name is configured  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andrea Cosentino 
 
 
 

Assignee:
 
 Andrea Cosentino 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (CAMEL-10772) Spring POJO @Produce @Consume Remoting auto detect binding usage improvement

2017-01-31 Thread Christopher Harris (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Harris commented on  CAMEL-10772 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Spring POJO @Produce @Consume Remoting auto detect binding usage improvement  
 
 
 
 
 
 
 
 
 
 
Pull Request 
https://github.com/apache/camel/pull/1434 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (CAMEL-10772) Spring POJO @Produce @Consume Remoting auto detect binding usage improvement

2017-01-31 Thread Christopher Harris (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Harris created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Camel /  CAMEL-10772 
 
 
 
  Spring POJO @Produce @Consume Remoting auto detect binding usage improvement  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 2.18.0, 2.17.0, 2.16.0, 2.19.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 camel-core, camel-spring 
 
 
 

Created:
 

 31/Jan/17 11:24 
 
 
 

Environment:
 
 
Java 1.8, Spring 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Christopher Harris 
 
 
 
 
 
 
 
 
 
 
Convention over configuration 
Improvement in AbstractCamelInvocationHandler.invokeProxy, to auto detect if the invocation is binding capable.  
It is determined by checking the parameter count and annotation types on each parameter, and only use binding if it is capable. Otherwise fallback on to the old bean invocation way.

[jira] (CAMEL-10771) CxfEndpoint shows WARNING altough endpoint-/port name is configured

2017-01-31 Thread Jochen Riedlinger (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jochen Riedlinger updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Camel /  CAMEL-10771 
 
 
 
  CxfEndpoint shows WARNING altough endpoint-/port name is configured  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jochen Riedlinger 
 
 
 
 
 
 
 
 
 
 Although I have configured the endpoint-/port name I get this WARNING in my logs:2017-01-31 09:27:10.662 | WARN | org.apache.camel.component.cxf.CxfEndpoint | http-0.0.0.0:8443-1 | The endpoint/port name of cxf://https://someURL?cxfEndpointConfigurer=%23myWSCxfEndpointConfigurer=PAYLOAD=defaultOperation=%7Bhttp%3A%2F%2Fexample.com%2Fx%2y%2FGz%7DMyBinding_soap12=true=true=wsdl-reference%2Fmywsdl.wsdl is empty, cxf will try to load the first one in wsdl for you. | org.apache.camel.component.cxf.CxfEndpoint.checkName(CxfEndpoint.java:646)The cause for this is that the "checkName" method checks the instance variable "portName" and not "portNameString"  (see attached screenshot) .Therefore I think it's better if the linescheckName(portName, "endpoint/port name");checkName(serviceName, "service name");get replaced bycheckName(getPortName(), "endpoint/port name");checkName(getServiceName(), "service name");I'll send a Pull Request soon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (CAMEL-10771) CxfEndpoint shows WARNING altough endpoint-/port name is configured

2017-01-31 Thread Jochen Riedlinger (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jochen Riedlinger updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Camel /  CAMEL-10771 
 
 
 
  CxfEndpoint shows WARNING altough endpoint-/port name is configured  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jochen Riedlinger 
 
 
 

Attachment:
 
 CxfEndpoint_in_Debugger.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (CAMEL-10771) CxfEndpoint shows WARNING altough endpoint-/port name is configured

2017-01-31 Thread Jochen Riedlinger (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jochen Riedlinger commented on  CAMEL-10771 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: CxfEndpoint shows WARNING altough endpoint-/port name is configured  
 
 
 
 
 
 
 
 
 
 
https://github.com/apache/camel/pull/1433 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (CAMEL-10771) CxfEndpoint shows WARNING altough endpoint-/port name is configured

2017-01-31 Thread ASF GitHub Bot (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ASF GitHub Bot commented on  CAMEL-10771 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: CxfEndpoint shows WARNING altough endpoint-/port name is configured  
 
 
 
 
 
 
 
 
 
 
GitHub user jochenr opened a pull request: 
 https://github.com/apache/camel/pull/1433 
 CAMEL-10771: check endpoint/port and service names via getter instead of 
 instance variables 
You can merge this pull request into a Git repository by running: 
 $ git pull https://github.com/jochenr/camel master 
Alternatively you can review and apply these changes as the patch at: 
 https://github.com/apache/camel/pull/1433.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 #1433 
 
commit aa129b077801fc8ae13a7e784095b9151b169153 Author: jochenr  Date: 2017-01-31T10:41:30Z 
 CAMEL-10771: check endpoint/port and service names via getter instead of instance variables 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (CAMEL-10770) Upgrade to Spring Boot 1.5.x

2017-01-31 Thread Claus Ibsen (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Claus Ibsen resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Okay gave a little test with 2.18.2 and spring boot 1.5.1 and they work fine together. Its just the deprecated FarJarRouteBuilder etc you should not use. 
 
 
 
 
 
 
 
 
 
 Camel /  CAMEL-10770 
 
 
 
  Upgrade to Spring Boot 1.5.x  
 
 
 
 
 
 
 
 
 

Change By:
 
 Claus Ibsen 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Open Resolved 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (CAMEL-10771) CxfEndpoint shows WARNING altough endpoint-/port name is configured

2017-01-31 Thread Jochen Riedlinger (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jochen Riedlinger created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Camel /  CAMEL-10771 
 
 
 
  CxfEndpoint shows WARNING altough endpoint-/port name is configured  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 2.18.1, 2.17.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 camel-cxf 
 
 
 

Created:
 

 31/Jan/17 10:27 
 
 
 

Fix Versions:
 

 2.17.6, 2.18.2 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Jochen Riedlinger 
 
 
 
 
 
 
 
 
 
 
Although I have configured the endpoint-/port name I get this WARNING in my logs: 
2017-01-31 09:27:10.662 | WARN | org.apache.camel.component.cxf.CxfEndpoint | http-0.0.0.0:8443-1 | The endpoint/port name of cxf://https://someURL?cxfEndpointConfigurer=%23myWSCxfEndpointConfigurer=PAYLOAD=defaultOperation=%7Bhttp%3A%2F%2Fexample.com%2Fx%2y%2FGz%7DMyBinding_soap12=true=true=wsdl-reference%2Fmywsdl.wsdl is empty, cxf will try to load the first one in wsdl for you. | org.apache.camel.component.cxf.CxfEndpoint.checkName(CxfEndpoint.java:646) 
The cause for this is that the "checkName" method checks the

[jira] (CAMEL-10770) Upgrade to Spring Boot 1.5.x

2017-01-31 Thread Claus Ibsen (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Claus Ibsen commented on  CAMEL-10770 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Upgrade to Spring Boot 1.5.x  
 
 
 
 
 
 
 
 
 
 
Because Spring Boot is so popular we may consider add support for it in 2.18.x by dropping the deprecated APIs in 2.18.x so it works against Spring Boot 1.5.x, but keep the spring boot version to 1.4.x. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (CAMEL-10770) Upgrade to Spring Boot 1.5.x

2017-01-31 Thread Claus Ibsen (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Claus Ibsen assigned an issue to Claus Ibsen 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Camel /  CAMEL-10770 
 
 
 
  Upgrade to Spring Boot 1.5.x  
 
 
 
 
 
 
 
 
 

Change By:
 
 Claus Ibsen 
 
 
 

Assignee:
 
 Claus Ibsen 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (CAMEL-10766) Create a new camel-elasticsearch5 component for supporting ElasticSearch 5.x Java API

2017-01-31 Thread Claus Ibsen (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Claus Ibsen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Camel /  CAMEL-10766 
 
 
 
  Create a new camel-elasticsearch5 component for supporting ElasticSearch 5.x Java API  
 
 
 
 
 
 
 
 
 

Change By:
 
 Claus Ibsen 
 
 
 

Fix Version/s:
 
 2.19.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (CAMEL-10766) Create a new camel-elasticsearch5 component for supporting ElasticSearch 5.x Java API

2017-01-31 Thread Claus Ibsen (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Claus Ibsen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Camel /  CAMEL-10766 
 
 
 
  Create a new camel-elasticsearch5 component for supporting ElasticSearch 5.x Java API  
 
 
 
 
 
 
 
 
 

Change By:
 
 Claus Ibsen 
 
 
 

Priority:
 
 Minor Major 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (CAMEL-10766) Create a new camel-elasticsearch5 component for supporting ElasticSearch 5.x Java API

2017-01-31 Thread Claus Ibsen (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Claus Ibsen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Camel /  CAMEL-10766 
 
 
 
  Create a new camel-elasticsearch5 component for supporting ElasticSearch 5.x Java API  
 
 
 
 
 
 
 
 
 

Change By:
 
 Claus Ibsen 
 
 
 

Affects Version/s:
 
 2.19.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (CAMEL-10768) Dropbox component should support specifying route params using headers

2017-01-31 Thread Claus Ibsen (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Claus Ibsen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Camel /  CAMEL-10768 
 
 
 
  Dropbox component should support specifying route params using headers  
 
 
 
 
 
 
 
 
 

Change By:
 
 Claus Ibsen 
 
 
 

Estimated Complexity:
 
 Unknown Novice 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (CAMEL-10766) Create a new camel-elasticsearch5 component for supporting ElasticSearch 5.x Java API

2017-01-31 Thread Claus Ibsen (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Claus Ibsen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Camel /  CAMEL-10766 
 
 
 
  Create a new camel-elasticsearch5 component for supporting ElasticSearch 5.x Java API  
 
 
 
 
 
 
 
 
 

Change By:
 
 Claus Ibsen 
 
 
 

Issue Type:
 
 Task New Feature 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (CAMEL-10769) Tika Component - Support Multi-Value Metadata

2017-01-31 Thread Claus Ibsen (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Claus Ibsen resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Thanks for the PR 
 
 
 
 
 
 
 
 
 
 Camel /  CAMEL-10769 
 
 
 
  Tika Component - Support Multi-Value Metadata  
 
 
 
 
 
 
 
 
 

Change By:
 
 Claus Ibsen 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Assignee:
 
 Claus Ibsen 
 
 
 

Fix Version/s:
 
 2.19.0 
 
 
 

Status:
 
 Open Resolved 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (CAMEL-10760) Allow OGNL expression on square bracket accessed properties and headers in simple language

2017-01-31 Thread Claus Ibsen (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Claus Ibsen resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Thanks for the PR 
 
 
 
 
 
 
 
 
 
 Camel /  CAMEL-10760 
 
 
 
  Allow OGNL _expression_ on square bracket accessed properties and headers in simple language  
 
 
 
 
 
 
 
 
 

Change By:
 
 Claus Ibsen 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Open Resolved 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (CAMEL-10760) Allow OGNL expression on square bracket accessed properties and headers in simple language

2017-01-31 Thread ASF GitHub Bot (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ASF GitHub Bot commented on  CAMEL-10760 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow OGNL _expression_ on square bracket accessed properties and headers in simple language  
 
 
 
 
 
 
 
 
 
 
Github user asfgit closed the pull request at: 
 https://github.com/apache/camel/pull/1430 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (CAMEL-10760) Allow OGNL expression on square bracket accessed properties and headers in simple language

2017-01-31 Thread Claus Ibsen (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Claus Ibsen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Camel /  CAMEL-10760 
 
 
 
  Allow OGNL _expression_ on square bracket accessed properties and headers in simple language  
 
 
 
 
 
 
 
 
 

Change By:
 
 Claus Ibsen 
 
 
 

Affects Version/s:
 
 2.19.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (CAMEL-10760) Allow OGNL expression on square bracket accessed properties and headers in simple language

2017-01-31 Thread Claus Ibsen (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Claus Ibsen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Camel /  CAMEL-10760 
 
 
 
  Allow OGNL _expression_ on square bracket accessed properties and headers in simple language  
 
 
 
 
 
 
 
 
 

Change By:
 
 Claus Ibsen 
 
 
 

Component/s:
 
 camel-core 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (CAMEL-10760) Allow OGNL expression on square bracket accessed properties and headers in simple language

2017-01-31 Thread Claus Ibsen (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Claus Ibsen assigned an issue to Claus Ibsen 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Camel /  CAMEL-10760 
 
 
 
  Allow OGNL _expression_ on square bracket accessed properties and headers in simple language  
 
 
 
 
 
 
 
 
 

Change By:
 
 Claus Ibsen 
 
 
 

Assignee:
 
 Claus Ibsen 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (CAMEL-10760) Allow OGNL expression on square bracket accessed properties and headers in simple language

2017-01-31 Thread Claus Ibsen (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Claus Ibsen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Camel /  CAMEL-10760 
 
 
 
  Allow OGNL _expression_ on square bracket accessed properties and headers in simple language  
 
 
 
 
 
 
 
 
 

Change By:
 
 Claus Ibsen 
 
 
 

Fix Version/s:
 
 2.19.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (CAMEL-10770) Upgrade to Spring Boot 1.5.x

2017-01-31 Thread Claus Ibsen (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Claus Ibsen created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Camel /  CAMEL-10770 
 
 
 
  Upgrade to Spring Boot 1.5.x  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 camel-spring-boot 
 
 
 

Created:
 

 31/Jan/17 08:40 
 
 
 

Fix Versions:
 

 2.19.0 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Claus Ibsen 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)