[jira] [Commented] (CAMEL-11959) New component YQL

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-11959:


carlphilipp opened a new pull request #2070: CAMEL-11959: Add new camel-yql 
component
URL: https://github.com/apache/camel/pull/2070
 
 
   Add a new YQL component


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


> New component YQL
> -
>
> Key: CAMEL-11959
> URL: https://issues.apache.org/jira/browse/CAMEL-11959
> Project: Camel
>  Issue Type: New Feature
>Reporter: Carl-Philipp Harmant
>Priority: Minor
>
> Add a new component, camel-yql that will allow to obtain data from YQL (Yahoo 
> Query Language) 
> https://developer.yahoo.com/yql/



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

[jira] [Commented] (CAMEL-11959) New component YQL

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-11959:


GitHub user carlphilipp opened a pull request:

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

CAMEL-11959: Add new camel-yql component

Add a new YQL component

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

$ git pull https://github.com/carlphilipp/camel feature/camel-yql

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

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


commit f9435e8cd0d2472a325854b799ce2c3bdcd43847
Author: Carl-Philipp Harmant 
Date:   2017-10-31T02:20:57Z

CAMEL-11959: Add new camel-yql component




> New component YQL
> -
>
> Key: CAMEL-11959
> URL: https://issues.apache.org/jira/browse/CAMEL-11959
> Project: Camel
>  Issue Type: New Feature
>Reporter: Carl-Philipp Harmant
>Priority: Minor
>
> Add a new component, camel-yql that will allow to obtain data from YQL (Yahoo 
> Query Language) 
> https://developer.yahoo.com/yql/



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

[jira] [Resolved] (CAMEL-11968) Support literal values in endpoint parameters

[Zoran Regvart (JIRA)]

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

Zoran Regvart resolved CAMEL-11968.
---
Resolution: Implemented

Now literal values can be specified as endpoint parameters for example API 
version
in path such as {{/api/version/users/id}}.

> Support literal values in endpoint parameters
> -
>
> Key: CAMEL-11968
> URL: https://issues.apache.org/jira/browse/CAMEL-11968
> Project: Camel
>  Issue Type: Improvement
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Minor
> Fix For: 2.21.0
>
>
> Sometimes it a value of a query or path parameter can be given in advance on 
> endpoint creation. The Camel REST Swagger component should support these by 
> setting them when constructing the endpoint URI for the delegating component. 



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

[jira] [Comment Edited] (CAMEL-11968) Support literal values in endpoint parameters

[Zoran Regvart (JIRA)]

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

Zoran Regvart edited comment on CAMEL-11968 at 10/30/17 10:48 PM:
--

Now literal values can be specified as endpoint parameters for example API 
version in path such as {{/api/version/users/id}}.


was (Author: zregvart):
Now literal values can be specified as endpoint parameters for example API 
version
in path such as {{/api/version/users/id}}.

> Support literal values in endpoint parameters
> -
>
> Key: CAMEL-11968
> URL: https://issues.apache.org/jira/browse/CAMEL-11968
> Project: Camel
>  Issue Type: Improvement
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Minor
> Fix For: 2.21.0
>
>
> Sometimes it a value of a query or path parameter can be given in advance on 
> endpoint creation. The Camel REST Swagger component should support these by 
> setting them when constructing the endpoint URI for the delegating component. 



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

[jira] [Created] (CAMEL-11968) Support literal values in endpoint parameters

[Zoran Regvart (JIRA)]

Zoran Regvart created CAMEL-11968:
-

 Summary: Support literal values in endpoint parameters
 Key: CAMEL-11968
 URL: https://issues.apache.org/jira/browse/CAMEL-11968
 Project: Camel
  Issue Type: Improvement
Reporter: Zoran Regvart
Assignee: Zoran Regvart
Priority: Minor
 Fix For: 2.21.0


Sometimes it a value of a query or path parameter can be given in advance on 
endpoint creation. The Camel REST Swagger component should support these by 
setting them when constructing the endpoint URI for the delegating component. 



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

[jira] [Updated] (CAMEL-11967) Restlet binding should not create jaxb marshaller when binding mode is set to json

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-11967:

Component/s: rest

> Restlet binding should not create jaxb marshaller when binding mode is set to 
> json
> --
>
> Key: CAMEL-11967
> URL: https://issues.apache.org/jira/browse/CAMEL-11967
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core, rest
>Affects Versions: 2.20.0
>Reporter: john
>Priority: Minor
> Fix For: 2.20.1, 2.21.0
>
>
> The following rest endpoint fails with jaxb exception:
> {code:java}
> .get("/getAllEndpoints").bindingMode(RestBindingMode.json).outType(Map.class)
>   
> .to("bean:IRWebServiceRegistry?method=getAllProperties");
> {code}
> {code:java}
> Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts 
> of IllegalAnnotationExceptions
> java.util.Map is an interface, and JAXB can't handle interfaces.
> {code}
> This is fine if i wanted to marshall to xml but i specifically set binding 
> mode to json.
> Fix:
> Change this line:
> https://github.com/apache/camel/blob/36039c0563dfe9e04527c5eca1058e66326054ee/camel-core/src/main/java/org/apache/camel/model/rest/RestBindingDefinition.java#L174
> To: 
> if (jaxb != null && (mode.contains("xml") || 
> mode.equals(RestBindingMode.auto))) {
> May want to consider doing the same for the json section at line 130



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

[jira] [Updated] (CAMEL-11967) Restlet binding should not create jaxb marshaller when binding mode is set to json

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-11967:

Fix Version/s: 2.21.0
   2.20.1

> Restlet binding should not create jaxb marshaller when binding mode is set to 
> json
> --
>
> Key: CAMEL-11967
> URL: https://issues.apache.org/jira/browse/CAMEL-11967
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core, rest
>Affects Versions: 2.20.0
>Reporter: john
>Priority: Minor
> Fix For: 2.20.1, 2.21.0
>
>
> The following rest endpoint fails with jaxb exception:
> {code:java}
> .get("/getAllEndpoints").bindingMode(RestBindingMode.json).outType(Map.class)
>   
> .to("bean:IRWebServiceRegistry?method=getAllProperties");
> {code}
> {code:java}
> Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts 
> of IllegalAnnotationExceptions
> java.util.Map is an interface, and JAXB can't handle interfaces.
> {code}
> This is fine if i wanted to marshall to xml but i specifically set binding 
> mode to json.
> Fix:
> Change this line:
> https://github.com/apache/camel/blob/36039c0563dfe9e04527c5eca1058e66326054ee/camel-core/src/main/java/org/apache/camel/model/rest/RestBindingDefinition.java#L174
> To: 
> if (jaxb != null && (mode.contains("xml") || 
> mode.equals(RestBindingMode.auto))) {
> May want to consider doing the same for the json section at line 130



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

[jira] [Commented] (CAMEL-11967) Restlet binding should not create jaxb marshaller when binding mode is set to json

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-11967:
-

Thanks John, would you like to try to submit this patch as a github PR (pull 
request), then its easier for us to apply

There is a link from here with some points how to do that
http://camel.apache.org/contributing

And there is also plenty of other resources online about how to work with 
github and do PRs

> Restlet binding should not create jaxb marshaller when binding mode is set to 
> json
> --
>
> Key: CAMEL-11967
> URL: https://issues.apache.org/jira/browse/CAMEL-11967
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core, rest
>Affects Versions: 2.20.0
>Reporter: john
>Priority: Minor
> Fix For: 2.20.1, 2.21.0
>
>
> The following rest endpoint fails with jaxb exception:
> {code:java}
> .get("/getAllEndpoints").bindingMode(RestBindingMode.json).outType(Map.class)
>   
> .to("bean:IRWebServiceRegistry?method=getAllProperties");
> {code}
> {code:java}
> Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts 
> of IllegalAnnotationExceptions
> java.util.Map is an interface, and JAXB can't handle interfaces.
> {code}
> This is fine if i wanted to marshall to xml but i specifically set binding 
> mode to json.
> Fix:
> Change this line:
> https://github.com/apache/camel/blob/36039c0563dfe9e04527c5eca1058e66326054ee/camel-core/src/main/java/org/apache/camel/model/rest/RestBindingDefinition.java#L174
> To: 
> if (jaxb != null && (mode.contains("xml") || 
> mode.equals(RestBindingMode.auto))) {
> May want to consider doing the same for the json section at line 130



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

[jira] [Commented] (CAMEL-11965) camel BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-11965:


davsclaus closed pull request #2069: CAMEL-11965: added in parent/pom.xml all 
the hapi structures dependen…
URL: https://github.com/apache/camel/pull/2069
 
 
   

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/parent/pom.xml b/parent/pom.xml
index eacdfe12390..49e80de 100644
--- a/parent/pom.xml
+++ b/parent/pom.xml
@@ -4203,6 +4203,21 @@
   
   
   ca.uhn.hapi
+  hapi-structures-v22
+  ${hapi-version}
+  
+  
+  ca.uhn.hapi
+  hapi-structures-v23
+  ${hapi-version}
+  
+  
+  ca.uhn.hapi
+  hapi-structures-v231
+  ${hapi-version}
+  
+  
+  ca.uhn.hapi
   hapi-structures-v24
   ${hapi-version}
   
@@ -4211,6 +4226,16 @@
   hapi-structures-v25
   ${hapi-version}
   
+  
+  ca.uhn.hapi
+  hapi-structures-v251
+  ${hapi-version}
+  
+  
+  ca.uhn.hapi
+  hapi-structures-v26
+  ${hapi-version}
+  
 
   
   


 


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 BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251
> --
>
> Key: CAMEL-11965
> URL: https://issues.apache.org/jira/browse/CAMEL-11965
> Project: Camel
>  Issue Type: Task
>  Components: build system
>Affects Versions: 2.20.0
>Reporter: Andrea Tarocchi
>Assignee: Andrea Cosentino
>Priority: Minor
>
> Camel BOM and camel-hl7 lack the optional dependency to 
> {{hapi-structures-v251}} while  }
> {{hapi-structures-v25}} and  {{hapi-structures-v24}} are present.
> So if a maven project use dependency management like:
> {code:XML}
>   
> 
>   
> org.apache.camel
> camel-parent
> ${camel.version}
> pom
> import
>   
> 
>   
> {code}
> is not able to do:
> {code:java}
>   
>   ca.uhn.hapi
>   hapi-structures-v251
>   
> {code}
> but need to specify the right version defeating the purpose of using a BOM.
>  



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

[jira] [Commented] (CAMEL-11965) camel BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-11965:


Github user davsclaus closed the pull request at:

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


> camel BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251
> --
>
> Key: CAMEL-11965
> URL: https://issues.apache.org/jira/browse/CAMEL-11965
> Project: Camel
>  Issue Type: Task
>  Components: build system
>Affects Versions: 2.20.0
>Reporter: Andrea Tarocchi
>Assignee: Andrea Cosentino
>Priority: Minor
>
> Camel BOM and camel-hl7 lack the optional dependency to 
> {{hapi-structures-v251}} while  }
> {{hapi-structures-v25}} and  {{hapi-structures-v24}} are present.
> So if a maven project use dependency management like:
> {code:XML}
>   
> 
>   
> org.apache.camel
> camel-parent
> ${camel.version}
> pom
> import
>   
> 
>   
> {code}
> is not able to do:
> {code:java}
>   
>   ca.uhn.hapi
>   hapi-structures-v251
>   
> {code}
> but need to specify the right version defeating the purpose of using a BOM.
>  



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

[jira] [Created] (CAMEL-11967) Restlet binding should not create jaxb marshaller when binding mode is set to json

[john (JIRA)]

john created CAMEL-11967:


 Summary: Restlet binding should not create jaxb marshaller when 
binding mode is set to json
 Key: CAMEL-11967
 URL: https://issues.apache.org/jira/browse/CAMEL-11967
 Project: Camel
  Issue Type: Bug
  Components: camel-core
Affects Versions: 2.20.0
Reporter: john
Priority: Minor


The following rest endpoint fails with jaxb exception:


{code:java}
.get("/getAllEndpoints").bindingMode(RestBindingMode.json).outType(Map.class)

.to("bean:IRWebServiceRegistry?method=getAllProperties");
{code}



{code:java}
Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts of 
IllegalAnnotationExceptions
java.util.Map is an interface, and JAXB can't handle interfaces.
{code}


This is fine if i wanted to marshall to xml but i specifically set binding mode 
to json.

Fix:
Change this line:
https://github.com/apache/camel/blob/36039c0563dfe9e04527c5eca1058e66326054ee/camel-core/src/main/java/org/apache/camel/model/rest/RestBindingDefinition.java#L174

To: 
if (jaxb != null && (mode.contains("xml") || 
mode.equals(RestBindingMode.auto))) {

May want to consider doing the same for the json section at line 130




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

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

[Robert Hillier (JIRA)]

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

Robert Hillier updated CAMEL-11951:
---
Attachment: camel-bug-demo.zip

Apologies, the properties aren't used in this demo, and can be removed.  I have 
updated the source and attached a zip file.

Many thanks,

Rob

> Uri matching does not match request type
> 
>
> Key: CAMEL-11951
> URL: https://issues.apache.org/jira/browse/CAMEL-11951
> Project: Camel
>  Issue Type: Bug
>  Components: camel-http-common
>Affects Versions: 2.20.0
> Environment: camel-spring, camel-jetty
> OS - RHEL
>Reporter: Robert Hillier
> Attachments: camel-bug-demo.zip
>
>
> I had previously described the problem here:
> https://stackoverflow.com/questions/46936348/apache-camel-rest-dsl-405-method-not-allowed
> It appears that the problem is down to a possible bug in the way URIs are 
> matched (not to mention my rather obscure use-case)
> I have a number of REST-DSL endpoints with the same URI but different request 
> types (POST, PUT, GET, DELETE).  In my case, the URI is getting selected by
> HttpServletResolveConsumerStrategy.resolve (in addition to these, I have some 
> specific endpoints with wildcards in them)
> This method matches the URI, but not the request type.  When I send a GET 
> request, it returns the first consumer candidate it finds which, in my case, 
> always seems to be PUT.  Later, when CamelContinuationServlet.doService 
> checks that the request type and cadidate type match, they don't.  It then 
> returns 405 Method Not Allowed.
> I believe that the HttpServletResolveConsumerStrategy.resolve method IN 
> camel-hhtp-common should check the request type as well as the URI.



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

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

[Robert Hillier (JIRA)]

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

Robert Hillier updated CAMEL-11951:
---
Attachment: (was: camel-bug-demo.zip)

> Uri matching does not match request type
> 
>
> Key: CAMEL-11951
> URL: https://issues.apache.org/jira/browse/CAMEL-11951
> Project: Camel
>  Issue Type: Bug
>  Components: camel-http-common
>Affects Versions: 2.20.0
> Environment: camel-spring, camel-jetty
> OS - RHEL
>Reporter: Robert Hillier
>
> I had previously described the problem here:
> https://stackoverflow.com/questions/46936348/apache-camel-rest-dsl-405-method-not-allowed
> It appears that the problem is down to a possible bug in the way URIs are 
> matched (not to mention my rather obscure use-case)
> I have a number of REST-DSL endpoints with the same URI but different request 
> types (POST, PUT, GET, DELETE).  In my case, the URI is getting selected by
> HttpServletResolveConsumerStrategy.resolve (in addition to these, I have some 
> specific endpoints with wildcards in them)
> This method matches the URI, but not the request type.  When I send a GET 
> request, it returns the first consumer candidate it finds which, in my case, 
> always seems to be PUT.  Later, when CamelContinuationServlet.doService 
> checks that the request type and cadidate type match, they don't.  It then 
> returns 405 Method Not Allowed.
> I believe that the HttpServletResolveConsumerStrategy.resolve method IN 
> camel-hhtp-common should check the request type as well as the URI.



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

[jira] [Commented] (CAMEL-11965) camel BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251

[Andrea Tarocchi (JIRA)]

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

Andrea Tarocchi commented on CAMEL-11965:
-

Fair enough, 
create PR with all the version compatible with hapi v 2.2.

> camel BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251
> --
>
> Key: CAMEL-11965
> URL: https://issues.apache.org/jira/browse/CAMEL-11965
> Project: Camel
>  Issue Type: Task
>  Components: build system
>Affects Versions: 2.20.0
>Reporter: Andrea Tarocchi
>Assignee: Andrea Cosentino
>Priority: Minor
>
> Camel BOM and camel-hl7 lack the optional dependency to 
> {{hapi-structures-v251}} while  }
> {{hapi-structures-v25}} and  {{hapi-structures-v24}} are present.
> So if a maven project use dependency management like:
> {code:XML}
>   
> 
>   
> org.apache.camel
> camel-parent
> ${camel.version}
> pom
> import
>   
> 
>   
> {code}
> is not able to do:
> {code:java}
>   
>   ca.uhn.hapi
>   hapi-structures-v251
>   
> {code}
> but need to specify the right version defeating the purpose of using a BOM.
>  



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

[jira] [Commented] (CAMEL-11965) camel BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-11965:


GitHub user valdar opened a pull request:

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

CAMEL-11965: added in parent/pom.xml all the hapi structures dependen…

…cies compatible vit version 2.2

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

$ git pull https://github.com/valdar/camel CAMEL-11965

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

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


commit bd6d0aeaeeac200e6381a1773e6cadcdc8f7859e
Author: Andrea Tarocchi 
Date:   2017-10-30T17:04:57Z

CAMEL-11965: added in parent/pom.xml all the hapi structures dependencies 
compatible vit version 2.2




> camel BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251
> --
>
> Key: CAMEL-11965
> URL: https://issues.apache.org/jira/browse/CAMEL-11965
> Project: Camel
>  Issue Type: Task
>  Components: build system
>Affects Versions: 2.20.0
>Reporter: Andrea Tarocchi
>Assignee: Andrea Cosentino
>Priority: Minor
>
> Camel BOM and camel-hl7 lack the optional dependency to 
> {{hapi-structures-v251}} while  }
> {{hapi-structures-v25}} and  {{hapi-structures-v24}} are present.
> So if a maven project use dependency management like:
> {code:XML}
>   
> 
>   
> org.apache.camel
> camel-parent
> ${camel.version}
> pom
> import
>   
> 
>   
> {code}
> is not able to do:
> {code:java}
>   
>   ca.uhn.hapi
>   hapi-structures-v251
>   
> {code}
> but need to specify the right version defeating the purpose of using a BOM.
>  



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

[jira] [Commented] (CAMEL-11965) camel BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-11965:


valdar opened a new pull request #2069: CAMEL-11965: added in parent/pom.xml 
all the hapi structures dependen…
URL: https://github.com/apache/camel/pull/2069
 
 
   …cies compatible vit version 2.2


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 BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251
> --
>
> Key: CAMEL-11965
> URL: https://issues.apache.org/jira/browse/CAMEL-11965
> Project: Camel
>  Issue Type: Task
>  Components: build system
>Affects Versions: 2.20.0
>Reporter: Andrea Tarocchi
>Assignee: Andrea Cosentino
>Priority: Minor
>
> Camel BOM and camel-hl7 lack the optional dependency to 
> {{hapi-structures-v251}} while  }
> {{hapi-structures-v25}} and  {{hapi-structures-v24}} are present.
> So if a maven project use dependency management like:
> {code:XML}
>   
> 
>   
> org.apache.camel
> camel-parent
> ${camel.version}
> pom
> import
>   
> 
>   
> {code}
> is not able to do:
> {code:java}
>   
>   ca.uhn.hapi
>   hapi-structures-v251
>   
> {code}
> but need to specify the right version defeating the purpose of using a BOM.
>  



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

[jira] [Commented] (CAMEL-11954) Camel JMX name for cluster service

[Viral Gohel (JIRA)]

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

Viral Gohel commented on CAMEL-11954:
-

I will take a look at this. 
Do we also rename the packages to say: 
org.apache.camel.ha to org.apache.camel.clusterservices and
org.apache.camel.impl.ha to org.apache.camel.impl.clusterservices  ?

> Camel JMX name for cluster service
> --
>
> Key: CAMEL-11954
> URL: https://issues.apache.org/jira/browse/CAMEL-11954
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core, jmx
>Reporter: Claus Ibsen
> Fix For: 2.21.0
>
>
> We use ha today, which is a bit too short and confusing.
> Lets rename this to something better, like cluster.



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

[jira] [Created] (CAMEL-11966) camel-parent - Cleanup and it is not a BOM!

[Claus Ibsen (JIRA)]

Claus Ibsen created CAMEL-11966:
---

 Summary: camel-parent - Cleanup and it is not a BOM!
 Key: CAMEL-11966
 URL: https://issues.apache.org/jira/browse/CAMEL-11966
 Project: Camel
  Issue Type: Task
  Components: build system
Reporter: Claus Ibsen
 Fix For: 3.0.0


camel-parent is not a BOM but has been abused as one for long time. 

There is a new camel-bom that is minimal and more favorable to be used for 
future.

In Camel 3.0 we can cleanup camel-parent to not be a BOM and just setup 
dependency versions and a few other common thing, so it can be an internal pom 
file - as it should be.



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

[jira] [Commented] (CAMEL-11965) camel BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-11965:
-

However to be backwards compatible its likely better to sadly not remove them, 
and add the other 12 or so.

Then we can cleanup for camel 3.0

> camel BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251
> --
>
> Key: CAMEL-11965
> URL: https://issues.apache.org/jira/browse/CAMEL-11965
> Project: Camel
>  Issue Type: Task
>  Components: build system
>Affects Versions: 2.20.0
>Reporter: Andrea Tarocchi
>Assignee: Andrea Cosentino
>Priority: Minor
>
> Camel BOM and camel-hl7 lack the optional dependency to 
> {{hapi-structures-v251}} while  }
> {{hapi-structures-v25}} and  {{hapi-structures-v24}} are present.
> So if a maven project use dependency management like:
> {code:XML}
>   
> 
>   
> org.apache.camel
> camel-parent
> ${camel.version}
> pom
> import
>   
> 
>   
> {code}
> is not able to do:
> {code:java}
>   
>   ca.uhn.hapi
>   hapi-structures-v251
>   
> {code}
> but need to specify the right version defeating the purpose of using a BOM.
>  



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

[jira] [Commented] (CAMEL-11965) camel BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-11965:
-

Yeah they should be removed - if we did this for all 200 components to include 
whatever they may have extra then the parent pom file is too big and 
unmaintainable for us also. It has some old cruft today and would be a good 
idea to clean it up in camel 3.

There is BOM in camel-bom you can import. Its a minimalistic for camel artifact.

> camel BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251
> --
>
> Key: CAMEL-11965
> URL: https://issues.apache.org/jira/browse/CAMEL-11965
> Project: Camel
>  Issue Type: Task
>  Components: build system
>Affects Versions: 2.20.0
>Reporter: Andrea Tarocchi
>Assignee: Andrea Cosentino
>Priority: Minor
>
> Camel BOM and camel-hl7 lack the optional dependency to 
> {{hapi-structures-v251}} while  }
> {{hapi-structures-v25}} and  {{hapi-structures-v24}} are present.
> So if a maven project use dependency management like:
> {code:XML}
>   
> 
>   
> org.apache.camel
> camel-parent
> ${camel.version}
> pom
> import
>   
> 
>   
> {code}
> is not able to do:
> {code:java}
>   
>   ca.uhn.hapi
>   hapi-structures-v251
>   
> {code}
> but need to specify the right version defeating the purpose of using a BOM.
>  



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

[jira] [Commented] (CAMEL-11965) camel BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-11965:
-

They are used for testing.

> camel BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251
> --
>
> Key: CAMEL-11965
> URL: https://issues.apache.org/jira/browse/CAMEL-11965
> Project: Camel
>  Issue Type: Task
>  Components: build system
>Affects Versions: 2.20.0
>Reporter: Andrea Tarocchi
>Assignee: Andrea Cosentino
>Priority: Minor
>
> Camel BOM and camel-hl7 lack the optional dependency to 
> {{hapi-structures-v251}} while  }
> {{hapi-structures-v25}} and  {{hapi-structures-v24}} are present.
> So if a maven project use dependency management like:
> {code:XML}
>   
> 
>   
> org.apache.camel
> camel-parent
> ${camel.version}
> pom
> import
>   
> 
>   
> {code}
> is not able to do:
> {code:java}
>   
>   ca.uhn.hapi
>   hapi-structures-v251
>   
> {code}
> but need to specify the right version defeating the purpose of using a BOM.
>  



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

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

[Viral Gohel (JIRA)]

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

Viral Gohel commented on CAMEL-11951:
-

Hi Robert, 

Your attached reproducer is missing, mandatory 'location' attribute in 
 in your route file. Can you make the changes and upload 
the reproducer so that we can check ? Which is the property file you are 
referring in the reproducer ?

{code:java}




{code}


> Uri matching does not match request type
> 
>
> Key: CAMEL-11951
> URL: https://issues.apache.org/jira/browse/CAMEL-11951
> Project: Camel
>  Issue Type: Bug
>  Components: camel-http-common
>Affects Versions: 2.20.0
> Environment: camel-spring, camel-jetty
> OS - RHEL
>Reporter: Robert Hillier
> Attachments: camel-bug-demo.zip
>
>
> I had previously described the problem here:
> https://stackoverflow.com/questions/46936348/apache-camel-rest-dsl-405-method-not-allowed
> It appears that the problem is down to a possible bug in the way URIs are 
> matched (not to mention my rather obscure use-case)
> I have a number of REST-DSL endpoints with the same URI but different request 
> types (POST, PUT, GET, DELETE).  In my case, the URI is getting selected by
> HttpServletResolveConsumerStrategy.resolve (in addition to these, I have some 
> specific endpoints with wildcards in them)
> This method matches the URI, but not the request type.  When I send a GET 
> request, it returns the first consumer candidate it finds which, in my case, 
> always seems to be PUT.  Later, when CamelContinuationServlet.doService 
> checks that the request type and cadidate type match, they don't.  It then 
> returns 405 Method Not Allowed.
> I believe that the HttpServletResolveConsumerStrategy.resolve method IN 
> camel-hhtp-common should check the request type as well as the URI.



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

[jira] [Commented] (CAMEL-11965) camel BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251

[Andrea Tarocchi (JIRA)]

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

Andrea Tarocchi commented on CAMEL-11965:
-

[~davsclaus] that is a perfectly sensible approach, but in that case we should 
remove the optional dependency on v24 and v25 or add them all (which are 12).
Otherwise I fail to see the criteria in picking some versions over the others. 
Is there a specific reason why just v24 and v25 are included?

Regards,
Andrea.

> camel BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251
> --
>
> Key: CAMEL-11965
> URL: https://issues.apache.org/jira/browse/CAMEL-11965
> Project: Camel
>  Issue Type: Task
>  Components: build system
>Affects Versions: 2.20.0
>Reporter: Andrea Tarocchi
>Assignee: Andrea Cosentino
>Priority: Minor
>
> Camel BOM and camel-hl7 lack the optional dependency to 
> {{hapi-structures-v251}} while  }
> {{hapi-structures-v25}} and  {{hapi-structures-v24}} are present.
> So if a maven project use dependency management like:
> {code:XML}
>   
> 
>   
> org.apache.camel
> camel-parent
> ${camel.version}
> pom
> import
>   
> 
>   
> {code}
> is not able to do:
> {code:java}
>   
>   ca.uhn.hapi
>   hapi-structures-v251
>   
> {code}
> but need to specify the right version defeating the purpose of using a BOM.
>  



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

[jira] [Commented] (CAMEL-11965) camel BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-11965:
-

There are many hapi structures for different hapi versions. It is NOT our 
intention to have camel-parent as 100% of every single JAR ever possible.


> camel BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251
> --
>
> Key: CAMEL-11965
> URL: https://issues.apache.org/jira/browse/CAMEL-11965
> Project: Camel
>  Issue Type: Task
>  Components: build system
>Affects Versions: 2.20.0
>Reporter: Andrea Tarocchi
>Assignee: Andrea Cosentino
>Priority: Minor
>
> Camel BOM and camel-hl7 lack the optional dependency to 
> {{hapi-structures-v251}} while  }
> {{hapi-structures-v25}} and  {{hapi-structures-v24}} are present.
> So if a maven project use dependency management like:
> {code:XML}
>   
> 
>   
> org.apache.camel
> camel-parent
> ${camel.version}
> pom
> import
>   
> 
>   
> {code}
> is not able to do:
> {code:java}
>   
>   ca.uhn.hapi
>   hapi-structures-v251
>   
> {code}
> but need to specify the right version defeating the purpose of using a BOM.
>  



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

[jira] [Updated] (CAMEL-11965) camel BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-11965:

Component/s: build system

> camel BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251
> --
>
> Key: CAMEL-11965
> URL: https://issues.apache.org/jira/browse/CAMEL-11965
> Project: Camel
>  Issue Type: Task
>  Components: build system
>Affects Versions: 2.20.0
>Reporter: Andrea Tarocchi
>Assignee: Andrea Cosentino
>Priority: Minor
>
> Camel BOM and camel-hl7 lack the optional dependency to 
> {{hapi-structures-v251}} while  }
> {{hapi-structures-v25}} and  {{hapi-structures-v24}} are present.
> So if a maven project use dependency management like:
> {code:XML}
>   
> 
>   
> org.apache.camel
> camel-parent
> ${camel.version}
> pom
> import
>   
> 
>   
> {code}
> is not able to do:
> {code:java}
>   
>   ca.uhn.hapi
>   hapi-structures-v251
>   
> {code}
> but need to specify the right version defeating the purpose of using a BOM.
>  



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

[jira] [Updated] (CAMEL-11965) camel BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-11965:

Estimated Complexity: Novice  (was: Unknown)

> camel BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251
> --
>
> Key: CAMEL-11965
> URL: https://issues.apache.org/jira/browse/CAMEL-11965
> Project: Camel
>  Issue Type: Task
>  Components: build system
>Affects Versions: 2.20.0
>Reporter: Andrea Tarocchi
>Assignee: Andrea Cosentino
>Priority: Minor
>
> Camel BOM and camel-hl7 lack the optional dependency to 
> {{hapi-structures-v251}} while  }
> {{hapi-structures-v25}} and  {{hapi-structures-v24}} are present.
> So if a maven project use dependency management like:
> {code:XML}
>   
> 
>   
> org.apache.camel
> camel-parent
> ${camel.version}
> pom
> import
>   
> 
>   
> {code}
> is not able to do:
> {code:java}
>   
>   ca.uhn.hapi
>   hapi-structures-v251
>   
> {code}
> but need to specify the right version defeating the purpose of using a BOM.
>  



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

[jira] [Updated] (CAMEL-11965) camel BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-11965:

Issue Type: Task  (was: Bug)

> camel BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251
> --
>
> Key: CAMEL-11965
> URL: https://issues.apache.org/jira/browse/CAMEL-11965
> Project: Camel
>  Issue Type: Task
>Affects Versions: 2.20.0
>Reporter: Andrea Tarocchi
>Assignee: Andrea Cosentino
>Priority: Minor
>
> Camel BOM and camel-hl7 lack the optional dependency to 
> {{hapi-structures-v251}} while  }
> {{hapi-structures-v25}} and  {{hapi-structures-v24}} are present.
> So if a maven project use dependency management like:
> {code:XML}
>   
> 
>   
> org.apache.camel
> camel-parent
> ${camel.version}
> pom
> import
>   
> 
>   
> {code}
> is not able to do:
> {code:java}
>   
>   ca.uhn.hapi
>   hapi-structures-v251
>   
> {code}
> but need to specify the right version defeating the purpose of using a BOM.
>  



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

[jira] [Updated] (CAMEL-11965) camel BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-11965:

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

> camel BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251
> --
>
> Key: CAMEL-11965
> URL: https://issues.apache.org/jira/browse/CAMEL-11965
> Project: Camel
>  Issue Type: Bug
>Affects Versions: 2.20.0
>Reporter: Andrea Tarocchi
>Assignee: Andrea Cosentino
>Priority: Minor
>
> Camel BOM and camel-hl7 lack the optional dependency to 
> {{hapi-structures-v251}} while  }
> {{hapi-structures-v25}} and  {{hapi-structures-v24}} are present.
> So if a maven project use dependency management like:
> {code:XML}
>   
> 
>   
> org.apache.camel
> camel-parent
> ${camel.version}
> pom
> import
>   
> 
>   
> {code}
> is not able to do:
> {code:java}
>   
>   ca.uhn.hapi
>   hapi-structures-v251
>   
> {code}
> but need to specify the right version defeating the purpose of using a BOM.
>  



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

[jira] [Assigned] (CAMEL-11965) camel BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino reassigned CAMEL-11965:


Assignee: Andrea Cosentino

> camel BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251
> --
>
> Key: CAMEL-11965
> URL: https://issues.apache.org/jira/browse/CAMEL-11965
> Project: Camel
>  Issue Type: Bug
>Affects Versions: 2.17.0, 2.18.0, 2.19.0, 2.20.0
>Reporter: Andrea Tarocchi
>Assignee: Andrea Cosentino
>Priority: Minor
>
> Camel BOM and camel-hl7 lack the optional dependency to 
> {{hapi-structures-v251}} while  }
> {{hapi-structures-v25}} and  {{hapi-structures-v24}} are present.
> So if a maven project use dependency management like:
> {code:XML}
>   
> 
>   
> org.apache.camel
> camel-parent
> ${camel.version}
> pom
> import
>   
> 
>   
> {code}
> is not able to do:
> {code:java}
>   
>   ca.uhn.hapi
>   hapi-structures-v251
>   
> {code}
> but need to specify the right version defeating the purpose of using a BOM.
>  



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

[jira] [Created] (CAMEL-11965) camel BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251

[Andrea Tarocchi (JIRA)]

Andrea Tarocchi created CAMEL-11965:
---

 Summary: camel BOM (and camel-hl7) lack the optional dependency to 
hapi-structures-v251
 Key: CAMEL-11965
 URL: https://issues.apache.org/jira/browse/CAMEL-11965
 Project: Camel
  Issue Type: Bug
Affects Versions: 2.20.0, 2.19.0, 2.18.0, 2.17.0
Reporter: Andrea Tarocchi
Priority: Minor


Camel BOM and camel-hl7 lack the optional dependency to 
{{hapi-structures-v251}} while  }
{{hapi-structures-v25}} and  {{hapi-structures-v24}} are present.

So if a maven project use dependency management like:

{code:XML}
  

  
org.apache.camel
camel-parent
${camel.version}
pom
import
  

  
{code}
is not able to do:

{code:java}

ca.uhn.hapi
hapi-structures-v251

{code}
but need to specify the right version defeating the purpose of using a BOM.
 



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

[jira] [Resolved] (CAMEL-11964) Upgrade chemistry-opencmis to 1.1.0

[Andrea Cosentino (JIRA)]

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

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

> Upgrade chemistry-opencmis to 1.1.0
> ---
>
> Key: CAMEL-11964
> URL: https://issues.apache.org/jira/browse/CAMEL-11964
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-cmis
>Reporter: James Netherton
>Assignee: James Netherton
>Priority: Minor
> Fix For: 2.21.0
>
>
> The version camel-cmis is using for chemistry-opencmis is a little old now. 
> It'd be nice to upgrade to the latest 1.1.0 release as it'd help with 
> integrating the component on WildFly.



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

[jira] [Updated] (CAMEL-11964) Upgrade chemistry-opencmis to 1.1.0

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino updated CAMEL-11964:
-
Fix Version/s: 2.21.0

> Upgrade chemistry-opencmis to 1.1.0
> ---
>
> Key: CAMEL-11964
> URL: https://issues.apache.org/jira/browse/CAMEL-11964
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-cmis
>Reporter: James Netherton
>Assignee: James Netherton
>Priority: Minor
> Fix For: 2.21.0
>
>
> The version camel-cmis is using for chemistry-opencmis is a little old now. 
> It'd be nice to upgrade to the latest 1.1.0 release as it'd help with 
> integrating the component on WildFly.



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

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

[Robert Hillier (JIRA)]

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

Robert Hillier updated CAMEL-11951:
---
Attachment: camel-bug-demo.zip

As requested, Camel Bug Demo project attached.

To start the project, run:
mvn clean install camel:run

The project contains a number of routes which make http calls to a dummy server 
running on a Heroku instance.  There are two REST calls which demonstrate the 
problem:

http://{{serverAddr}}/integration/api/v1/customer/123456/devices

http://{{serverAddr}}/integration/api/v1/customer/123456/detail

The "devices" request is a specific uri, which performs some simple 
aggregation.  It contains a variable part in it's URI, used in subsequent 
calls.  This one is working fine

The "detail" request should be simply proxied through to the other server.  
However, this call returns a 405 Method Not Allowed.

Furthermore, if you comment out the "devices" request and restart, the proxied 
"detail" call then works fine.

> Uri matching does not match request type
> 
>
> Key: CAMEL-11951
> URL: https://issues.apache.org/jira/browse/CAMEL-11951
> Project: Camel
>  Issue Type: Bug
>  Components: camel-http-common
>Affects Versions: 2.20.0
> Environment: camel-spring, camel-jetty
> OS - RHEL
>Reporter: Robert Hillier
> Attachments: camel-bug-demo.zip
>
>
> I had previously described the problem here:
> https://stackoverflow.com/questions/46936348/apache-camel-rest-dsl-405-method-not-allowed
> It appears that the problem is down to a possible bug in the way URIs are 
> matched (not to mention my rather obscure use-case)
> I have a number of REST-DSL endpoints with the same URI but different request 
> types (POST, PUT, GET, DELETE).  In my case, the URI is getting selected by
> HttpServletResolveConsumerStrategy.resolve (in addition to these, I have some 
> specific endpoints with wildcards in them)
> This method matches the URI, but not the request type.  When I send a GET 
> request, it returns the first consumer candidate it finds which, in my case, 
> always seems to be PUT.  Later, when CamelContinuationServlet.doService 
> checks that the request type and cadidate type match, they don't.  It then 
> returns 405 Method Not Allowed.
> I believe that the HttpServletResolveConsumerStrategy.resolve method IN 
> camel-hhtp-common should check the request type as well as the URI.



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

[jira] [Commented] (CAMEL-11964) Upgrade chemistry-opencmis to 1.1.0

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-11964:


Github user oscerd closed the pull request at:

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


> Upgrade chemistry-opencmis to 1.1.0
> ---
>
> Key: CAMEL-11964
> URL: https://issues.apache.org/jira/browse/CAMEL-11964
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-cmis
>Reporter: James Netherton
>Assignee: James Netherton
>Priority: Minor
>
> The version camel-cmis is using for chemistry-opencmis is a little old now. 
> It'd be nice to upgrade to the latest 1.1.0 release as it'd help with 
> integrating the component on WildFly.



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

[jira] [Commented] (CAMEL-11964) Upgrade chemistry-opencmis to 1.1.0

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-11964:


oscerd commented on issue #2068: CAMEL-11964: Upgrade chemistry-opencmis to 
1.1.0
URL: https://github.com/apache/camel/pull/2068#issuecomment-340415073
 
 
   Thanks @jamesnetherton the PR has been merged. 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


> Upgrade chemistry-opencmis to 1.1.0
> ---
>
> Key: CAMEL-11964
> URL: https://issues.apache.org/jira/browse/CAMEL-11964
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-cmis
>Reporter: James Netherton
>Assignee: James Netherton
>Priority: Minor
>
> The version camel-cmis is using for chemistry-opencmis is a little old now. 
> It'd be nice to upgrade to the latest 1.1.0 release as it'd help with 
> integrating the component on WildFly.



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

[jira] [Commented] (CAMEL-11964) Upgrade chemistry-opencmis to 1.1.0

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-11964:


oscerd closed pull request #2068: CAMEL-11964: Upgrade chemistry-opencmis to 
1.1.0
URL: https://github.com/apache/camel/pull/2068
 
 
   

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-cmis/pom.xml b/components/camel-cmis/pom.xml
index 087bb48a4c4..5b1b63a6d9d 100644
--- a/components/camel-cmis/pom.xml
+++ b/components/camel-cmis/pom.xml
@@ -144,6 +144,7 @@
 
 
 
target/dependency
+true
 
 
 
org.apache.chemistry.opencmis
diff --git 
a/components/camel-cmis/src/main/java/org/apache/camel/component/cmis/CMISConsumer.java
 
b/components/camel-cmis/src/main/java/org/apache/camel/component/cmis/CMISConsumer.java
index 0432679cc21..e51aaef00e7 100644
--- 
a/components/camel-cmis/src/main/java/org/apache/camel/component/cmis/CMISConsumer.java
+++ 
b/components/camel-cmis/src/main/java/org/apache/camel/component/cmis/CMISConsumer.java
@@ -19,7 +19,6 @@
 import java.io.InputStream;
 import java.util.Map;
 
-import org.apache.camel.Endpoint;
 import org.apache.camel.Exchange;
 import org.apache.camel.Processor;
 import org.apache.camel.impl.ScheduledPollConsumer;
diff --git 
a/components/camel-cmis/src/main/java/org/apache/camel/component/cmis/CMISQueryProducer.java
 
b/components/camel-cmis/src/main/java/org/apache/camel/component/cmis/CMISQueryProducer.java
index 0a5c2c6ea85..b0f7bdc5564 100644
--- 
a/components/camel-cmis/src/main/java/org/apache/camel/component/cmis/CMISQueryProducer.java
+++ 
b/components/camel-cmis/src/main/java/org/apache/camel/component/cmis/CMISQueryProducer.java
@@ -19,7 +19,6 @@
 import java.util.List;
 import java.util.Map;
 
-import org.apache.camel.Endpoint;
 import org.apache.camel.Exchange;
 import org.apache.camel.impl.DefaultProducer;
 import org.apache.chemistry.opencmis.client.api.ItemIterable;
diff --git 
a/components/camel-cmis/src/main/java/org/apache/camel/component/cmis/CMISSessionFacade.java
 
b/components/camel-cmis/src/main/java/org/apache/camel/component/cmis/CMISSessionFacade.java
index f5da95fe8f0..70dc73f6843 100644
--- 
a/components/camel-cmis/src/main/java/org/apache/camel/component/cmis/CMISSessionFacade.java
+++ 
b/components/camel-cmis/src/main/java/org/apache/camel/component/cmis/CMISSessionFacade.java
@@ -26,7 +26,6 @@
 
 import org.apache.camel.spi.UriParam;
 import org.apache.camel.spi.UriParams;
-import org.apache.camel.spi.UriPath;
 import org.apache.chemistry.opencmis.client.api.CmisObject;
 import org.apache.chemistry.opencmis.client.api.Document;
 import org.apache.chemistry.opencmis.client.api.DocumentType;
diff --git 
a/components/camel-cmis/src/test/java/org/apache/camel/component/cmis/CMISTestSupport.java
 
b/components/camel-cmis/src/test/java/org/apache/camel/component/cmis/CMISTestSupport.java
index 1c0bc9e2be9..6ac0cceccfb 100644
--- 
a/components/camel-cmis/src/test/java/org/apache/camel/component/cmis/CMISTestSupport.java
+++ 
b/components/camel-cmis/src/test/java/org/apache/camel/component/cmis/CMISTestSupport.java
@@ -53,7 +53,7 @@
 protected static final String CMIS_ENDPOINT_TEST_SERVER
 = "http://localhost:%s/chemistry-opencmis-server-inmemory/atom11;;
 protected static final String OPEN_CMIS_SERVER_WAR_PATH
-= "target/dependency/chemistry-opencmis-server-inmemory-0.13.0.war";
+= "target/dependency/chemistry-opencmis-server-inmemory.war";
 
 protected static Server cmisServer;
 protected static int port;
diff --git a/parent/pom.xml b/parent/pom.xml
index 58e6ff3faee..0981a8fa201 100644
--- a/parent/pom.xml
+++ b/parent/pom.xml
@@ -130,7 +130,7 @@
 3.3.1
 3.3.1_1
 1.3.4
-0.13.0
+1.1.0
 6.1.11
 3.1.2
 
2.3.1_2


 


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 chemistry-opencmis to 1.1.0
> ---
>
> Key: CAMEL-11964
> URL: https://issues.apache.org/jira/browse/CAMEL-11964
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-cmis
>Reporter: James Netherton
>Assignee: James Netherton
>   

[jira] [Commented] (CAMEL-11964) Upgrade chemistry-opencmis to 1.1.0

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-11964:


GitHub user jamesnetherton opened a pull request:

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

CAMEL-11964: Upgrade chemistry-opencmis to 1.1.0

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

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

$ git pull https://github.com/jamesnetherton/camel CAMEL-11964

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

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


commit c230b7504289a10de647f1de84f58142666009ae
Author: James Netherton 
Date:   2017-10-30T11:07:02Z

CAMEL-11964: Upgrade chemistry-opencmis to 1.1.0




> Upgrade chemistry-opencmis to 1.1.0
> ---
>
> Key: CAMEL-11964
> URL: https://issues.apache.org/jira/browse/CAMEL-11964
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-cmis
>Reporter: James Netherton
>Assignee: James Netherton
>Priority: Minor
>
> The version camel-cmis is using for chemistry-opencmis is a little old now. 
> It'd be nice to upgrade to the latest 1.1.0 release as it'd help with 
> integrating the component on WildFly.



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

[jira] [Commented] (CAMEL-11964) Upgrade chemistry-opencmis to 1.1.0

[James Netherton (JIRA)]

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

James Netherton commented on CAMEL-11964:
-

PR sent for the master branch. Can this be backported to the 2.20.x branch? Or 
is the policy that we don't do version bumps on the older releases unless it's 
necessary?

> Upgrade chemistry-opencmis to 1.1.0
> ---
>
> Key: CAMEL-11964
> URL: https://issues.apache.org/jira/browse/CAMEL-11964
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-cmis
>Reporter: James Netherton
>Assignee: James Netherton
>Priority: Minor
>
> The version camel-cmis is using for chemistry-opencmis is a little old now. 
> It'd be nice to upgrade to the latest 1.1.0 release as it'd help with 
> integrating the component on WildFly.



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

[jira] [Commented] (CAMEL-11964) Upgrade chemistry-opencmis to 1.1.0

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-11964:


jamesnetherton opened a new pull request #2068: CAMEL-11964: Upgrade 
chemistry-opencmis to 1.1.0
URL: https://github.com/apache/camel/pull/2068
 
 
   https://issues.apache.org/jira/browse/CAMEL-11964


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 chemistry-opencmis to 1.1.0
> ---
>
> Key: CAMEL-11964
> URL: https://issues.apache.org/jira/browse/CAMEL-11964
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-cmis
>Reporter: James Netherton
>Assignee: James Netherton
>Priority: Minor
>
> The version camel-cmis is using for chemistry-opencmis is a little old now. 
> It'd be nice to upgrade to the latest 1.1.0 release as it'd help with 
> integrating the component on WildFly.



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

[jira] [Created] (CAMEL-11964) Upgrade chemistry-opencmis to 1.1.0

[James Netherton (JIRA)]

James Netherton created CAMEL-11964:
---

 Summary: Upgrade chemistry-opencmis to 1.1.0
 Key: CAMEL-11964
 URL: https://issues.apache.org/jira/browse/CAMEL-11964
 Project: Camel
  Issue Type: Improvement
  Components: camel-cmis
Reporter: James Netherton
Assignee: James Netherton
Priority: Minor


The version camel-cmis is using for chemistry-opencmis is a little old now. 
It'd be nice to upgrade to the latest 1.1.0 release as it'd help with 
integrating the component on WildFly.





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

[jira] [Commented] (CAMEL-11927) camel-spring-ws - Support for header transformation

[Richard Groote (JIRA)]

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

Richard Groote commented on CAMEL-11927:


Also added the documentation: See chapter 'How to transform the soap header 
using a stylesheet'

> camel-spring-ws - Support for header transformation
> ---
>
> Key: CAMEL-11927
> URL: https://issues.apache.org/jira/browse/CAMEL-11927
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-spring-ws
>Affects Versions: 2.19.3
>Reporter: Richard Groote
>Assignee: Önder Sezgin
> Fix For: 2.21.0
>
> Attachments: CompositeMessageFilter.java, 
> HeaderTransformationMessageFilter.java, SoapHeaderTest-context.xml, 
> SoapHeaderTest.java, soap-header-transform.xslt, spring-ws-component.adoc
>
>
> Improve support for soap header transformations:
> - The composite message filter is to have multiple filters applied
> - Header transformation filters is use to transform the soap header using a 
> stylesheet.
> I was not able to create a pull request for it



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

[jira] [Updated] (CAMEL-11927) camel-spring-ws - Support for header transformation

[Richard Groote (JIRA)]

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

Richard Groote updated CAMEL-11927:
---
Attachment: spring-ws-component.adoc

> camel-spring-ws - Support for header transformation
> ---
>
> Key: CAMEL-11927
> URL: https://issues.apache.org/jira/browse/CAMEL-11927
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-spring-ws
>Affects Versions: 2.19.3
>Reporter: Richard Groote
>Assignee: Önder Sezgin
> Fix For: 2.21.0
>
> Attachments: CompositeMessageFilter.java, 
> HeaderTransformationMessageFilter.java, SoapHeaderTest-context.xml, 
> SoapHeaderTest.java, soap-header-transform.xslt, spring-ws-component.adoc
>
>
> Improve support for soap header transformations:
> - The composite message filter is to have multiple filters applied
> - Header transformation filters is use to transform the soap header using a 
> stylesheet.
> I was not able to create a pull request for it



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

[jira] [Commented] (CAMEL-11927) camel-spring-ws - Support for header transformation

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-11927:


richardgroote commented on issue #2055: CAMEL-11927 - Improve support for soap 
header transformations - [Than…
URL: https://github.com/apache/camel/pull/2055#issuecomment-340354347
 
 
   See issue for the javadoc


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-spring-ws - Support for header transformation
> ---
>
> Key: CAMEL-11927
> URL: https://issues.apache.org/jira/browse/CAMEL-11927
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-spring-ws
>Affects Versions: 2.19.3
>Reporter: Richard Groote
>Assignee: Önder Sezgin
> Fix For: 2.21.0
>
> Attachments: CompositeMessageFilter.java, 
> HeaderTransformationMessageFilter.java, SoapHeaderTest-context.xml, 
> SoapHeaderTest.java, soap-header-transform.xslt
>
>
> Improve support for soap header transformations:
> - The composite message filter is to have multiple filters applied
> - Header transformation filters is use to transform the soap header using a 
> stylesheet.
> I was not able to create a pull request for it



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

[jira] [Updated] (CAMEL-11927) camel-spring-ws - Support for header transformation

[Richard Groote (JIRA)]

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

Richard Groote updated CAMEL-11927:
---
Attachment: HeaderTransformationMessageFilter.java

> camel-spring-ws - Support for header transformation
> ---
>
> Key: CAMEL-11927
> URL: https://issues.apache.org/jira/browse/CAMEL-11927
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-spring-ws
>Affects Versions: 2.19.3
>Reporter: Richard Groote
>Assignee: Önder Sezgin
> Fix For: 2.21.0
>
> Attachments: CompositeMessageFilter.java, 
> HeaderTransformationMessageFilter.java, SoapHeaderTest-context.xml, 
> SoapHeaderTest.java, soap-header-transform.xslt
>
>
> Improve support for soap header transformations:
> - The composite message filter is to have multiple filters applied
> - Header transformation filters is use to transform the soap header using a 
> stylesheet.
> I was not able to create a pull request for it



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

[jira] [Updated] (CAMEL-11927) camel-spring-ws - Support for header transformation

[Richard Groote (JIRA)]

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

Richard Groote updated CAMEL-11927:
---
Attachment: (was: HeaderTransformationMessageFilter.java)

> camel-spring-ws - Support for header transformation
> ---
>
> Key: CAMEL-11927
> URL: https://issues.apache.org/jira/browse/CAMEL-11927
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-spring-ws
>Affects Versions: 2.19.3
>Reporter: Richard Groote
>Assignee: Önder Sezgin
> Fix For: 2.21.0
>
> Attachments: CompositeMessageFilter.java, 
> HeaderTransformationMessageFilter.java, SoapHeaderTest-context.xml, 
> SoapHeaderTest.java, soap-header-transform.xslt
>
>
> Improve support for soap header transformations:
> - The composite message filter is to have multiple filters applied
> - Header transformation filters is use to transform the soap header using a 
> stylesheet.
> I was not able to create a pull request for it



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

[jira] [Commented] (CAMEL-11927) camel-spring-ws - Support for header transformation

[Richard Groote (JIRA)]

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

Richard Groote commented on CAMEL-11927:


Included java doc in the header transformation file

> camel-spring-ws - Support for header transformation
> ---
>
> Key: CAMEL-11927
> URL: https://issues.apache.org/jira/browse/CAMEL-11927
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-spring-ws
>Affects Versions: 2.19.3
>Reporter: Richard Groote
>Assignee: Önder Sezgin
> Fix For: 2.21.0
>
> Attachments: CompositeMessageFilter.java, 
> HeaderTransformationMessageFilter.java, SoapHeaderTest-context.xml, 
> SoapHeaderTest.java, soap-header-transform.xslt
>
>
> Improve support for soap header transformations:
> - The composite message filter is to have multiple filters applied
> - Header transformation filters is use to transform the soap header using a 
> stylesheet.
> I was not able to create a pull request for it



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