[jira] [Updated] (CAMEL-9125) Cannot build camel-scr-example

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-9125:
---
Priority: Major  (was: Blocker)

> Cannot build camel-scr-example
> --
>
> Key: CAMEL-9125
> URL: https://issues.apache.org/jira/browse/CAMEL-9125
> Project: Camel
>  Issue Type: Bug
>  Components: camel-scr, tooling
>Affects Versions: 2.15.4
>Reporter: Thomas Diesler
>
> affects branch 2.15.x
> {code}
> [INFO] [INFO] --- maven-compiler-plugin:2.5.1:testCompile 
> (default-testCompile) @ camel-scr-example ---
> [INFO] [INFO] Compiling 1 source file to 
> /Users/tdiesler/git/camel/tooling/archetypes/camel-archetype-scr/target/test-classes/projects/camel-scr-example/project/camel-scr-example/target/test-classes
> [INFO] [INFO] -
> [INFO] [ERROR] COMPILATION ERROR : 
> [INFO] [INFO] -
> [INFO] [ERROR] 
> /Users/tdiesler/git/camel/tooling/archetypes/camel-archetype-scr/target/test-classes/projects/camel-scr-example/project/camel-scr-example/src/test/java/example/CamelScrExampleTest.java:[44,40]
>  error: incompatible types: CamelContext cannot be converted to 
> ModelCamelContext
> [INFO] [INFO] 1 error
> [INFO] [INFO] -
> [INFO] [INFO] 
> 
> [INFO] [INFO] BUILD FAILURE
> [INFO] [INFO] 
> 
> [INFO] [INFO] Total time: 2.409 s
> [INFO] [INFO] Finished at: 2015-09-09T15:19:20+02:00
> [INFO] [INFO] Final Memory: 22M/243M
> [INFO] [INFO] 
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-9125) Cannot build camel-scr-example

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-9125:
---
Component/s: tooling

> Cannot build camel-scr-example
> --
>
> Key: CAMEL-9125
> URL: https://issues.apache.org/jira/browse/CAMEL-9125
> Project: Camel
>  Issue Type: Bug
>  Components: camel-scr, tooling
>Affects Versions: 2.15.4
>Reporter: Thomas Diesler
>
> affects branch 2.15.x
> {code}
> [INFO] [INFO] --- maven-compiler-plugin:2.5.1:testCompile 
> (default-testCompile) @ camel-scr-example ---
> [INFO] [INFO] Compiling 1 source file to 
> /Users/tdiesler/git/camel/tooling/archetypes/camel-archetype-scr/target/test-classes/projects/camel-scr-example/project/camel-scr-example/target/test-classes
> [INFO] [INFO] -
> [INFO] [ERROR] COMPILATION ERROR : 
> [INFO] [INFO] -
> [INFO] [ERROR] 
> /Users/tdiesler/git/camel/tooling/archetypes/camel-archetype-scr/target/test-classes/projects/camel-scr-example/project/camel-scr-example/src/test/java/example/CamelScrExampleTest.java:[44,40]
>  error: incompatible types: CamelContext cannot be converted to 
> ModelCamelContext
> [INFO] [INFO] 1 error
> [INFO] [INFO] -
> [INFO] [INFO] 
> 
> [INFO] [INFO] BUILD FAILURE
> [INFO] [INFO] 
> 
> [INFO] [INFO] Total time: 2.409 s
> [INFO] [INFO] Finished at: 2015-09-09T15:19:20+02:00
> [INFO] [INFO] Final Memory: 22M/243M
> [INFO] [INFO] 
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-9125) Cannot build camel-scr-example

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-9125:
---
Affects Version/s: 2.15.4

> Cannot build camel-scr-example
> --
>
> Key: CAMEL-9125
> URL: https://issues.apache.org/jira/browse/CAMEL-9125
> Project: Camel
>  Issue Type: Bug
>  Components: camel-scr, tooling
>Affects Versions: 2.15.4
>Reporter: Thomas Diesler
>
> affects branch 2.15.x
> {code}
> [INFO] [INFO] --- maven-compiler-plugin:2.5.1:testCompile 
> (default-testCompile) @ camel-scr-example ---
> [INFO] [INFO] Compiling 1 source file to 
> /Users/tdiesler/git/camel/tooling/archetypes/camel-archetype-scr/target/test-classes/projects/camel-scr-example/project/camel-scr-example/target/test-classes
> [INFO] [INFO] -
> [INFO] [ERROR] COMPILATION ERROR : 
> [INFO] [INFO] -
> [INFO] [ERROR] 
> /Users/tdiesler/git/camel/tooling/archetypes/camel-archetype-scr/target/test-classes/projects/camel-scr-example/project/camel-scr-example/src/test/java/example/CamelScrExampleTest.java:[44,40]
>  error: incompatible types: CamelContext cannot be converted to 
> ModelCamelContext
> [INFO] [INFO] 1 error
> [INFO] [INFO] -
> [INFO] [INFO] 
> 
> [INFO] [INFO] BUILD FAILURE
> [INFO] [INFO] 
> 
> [INFO] [INFO] Total time: 2.409 s
> [INFO] [INFO] Finished at: 2015-09-09T15:19:20+02:00
> [INFO] [INFO] Final Memory: 22M/243M
> [INFO] [INFO] 
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-9127) SmppConsumer throws IllegalArgumentException if the delivery receipt contains vendor specific optional parameters

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-9127.

   Resolution: Fixed
 Assignee: Claus Ibsen
Fix Version/s: 2.15.4
   2.16.0

Thanks for the patch.

> SmppConsumer throws IllegalArgumentException if the delivery receipt contains 
> vendor specific optional parameters
> -
>
> Key: CAMEL-9127
> URL: https://issues.apache.org/jira/browse/CAMEL-9127
> Project: Camel
>  Issue Type: Bug
>  Components: camel-smpp
>Reporter: Anshu Avinash
>Assignee: Claus Ibsen
> Fix For: 2.16.0, 2.15.4
>
> Attachments: CAMEL-9127.patch
>
>
> Error stack:
> Cannot create exchange. This exception will be ignored.. Caused by: 
> [java.lang.IllegalArgumentException - No tag for: 5120]
> java.lang.IllegalArgumentException: No tag for: 5120
> at 
> org.jsmpp.bean.OptionalParameter$Tag.valueOf(OptionalParameter.java:308)
> at 
> org.apache.camel.component.smpp.SmppBinding.createOptionalParameterByName(SmppBinding.java:161)
> at 
> org.apache.camel.component.smpp.SmppBinding.createSmppMessage(SmppBinding.java:112)
> at 
> org.apache.camel.component.smpp.SmppEndpoint.createOnAcceptDeliverSmExchange(SmppEndpoint.java:123)
> at 
> org.apache.camel.component.smpp.SmppEndpoint.createOnAcceptDeliverSmExchange(SmppEndpoint.java:107)
> at 
> org.apache.camel.component.smpp.MessageReceiverListenerImpl.onAcceptDeliverSm(MessageReceiverListenerImpl.java:70)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9126) camel-swagger may see unrelated type=context mbeans

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-9126:
---

Github user asfgit closed the pull request at:

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


> camel-swagger may see unrelated type=context mbeans
> ---
>
> Key: CAMEL-9126
> URL: https://issues.apache.org/jira/browse/CAMEL-9126
> Project: Camel
>  Issue Type: Bug
>  Components: camel-swagger
>Affects Versions: 2.15.3
>Reporter: Thomas Diesler
> Fix For: 2.16.0, 2.15.4
>
>
> {code}
> val names = server.queryNames(new ObjectName("*:type=context,*"), null)
> for (name <- names.asScala) {
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9126) camel-swagger may see unrelated type=context mbeans

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-9126:
---

Github user asfgit closed the pull request at:

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


> camel-swagger may see unrelated type=context mbeans
> ---
>
> Key: CAMEL-9126
> URL: https://issues.apache.org/jira/browse/CAMEL-9126
> Project: Camel
>  Issue Type: Bug
>  Components: camel-swagger
>Affects Versions: 2.15.3
>Reporter: Thomas Diesler
> Fix For: 2.16.0, 2.15.4
>
>
> {code}
> val names = server.queryNames(new ObjectName("*:type=context,*"), null)
> for (name <- names.asScala) {
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-9126) camel-swagger may see unrelated type=context mbeans

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-9126:
---
Priority: Minor  (was: Major)

> camel-swagger may see unrelated type=context mbeans
> ---
>
> Key: CAMEL-9126
> URL: https://issues.apache.org/jira/browse/CAMEL-9126
> Project: Camel
>  Issue Type: Bug
>  Components: camel-swagger
>Affects Versions: 2.15.3
>Reporter: Thomas Diesler
>Priority: Minor
> Fix For: 2.16.0, 2.15.4
>
>
> {code}
> val names = server.queryNames(new ObjectName("*:type=context,*"), null)
> for (name <- names.asScala) {
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-8734) camel-netty-http - Should ignore case of context-path

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-8734:


The header is as the user typed. The check is only on the matching of whether 
the consumer should trigger or not which is case insensitive.

If users would like case sensitive then log a new ticket. And use the vote 
system to see what the demand is.

> camel-netty-http - Should ignore case of context-path
> -
>
> Key: CAMEL-8734
> URL: https://issues.apache.org/jira/browse/CAMEL-8734
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-netty-http, camel-netty4-http
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
> Fix For: 2.15.3, 2.16.0
>
>
> We should ignore case when matching context-path. We have some code that 
> matches using .startsWith. But that does not match with different case, such 
> as Customer vs customer.
> People dont really want to expose HTTP services where the context path uses 
> different case. So if people type /customer or /Customer or /CUSTOMER then it 
> should match the same.
> See nabble
> http://camel.465427.n5.nabble.com/How-to-create-case-insensitive-URI-route-with-netty4-http-tp5766517.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-8748) DozerBeanMapper cannot instantiate DozerThreadContextClassLoader

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-8748.

Resolution: Fixed

> DozerBeanMapper cannot instantiate DozerThreadContextClassLoader 
> -
>
> Key: CAMEL-8748
> URL: https://issues.apache.org/jira/browse/CAMEL-8748
> Project: Camel
>  Issue Type: Bug
>  Components: camel-dozer
>Affects Versions: 2.15.3
>Reporter: Thomas Diesler
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.16.0, 2.15.4
>
>
> {code}
> 15:26:16,518 SEVERE [org.jboss.arquillian.protocol.jmx.JMXTestRunner] 
> (pool-2-thread-1) Failed: 
> org.wildfly.camel.test.csv.CSVIntegrationTest.testMarshal: 
> org.dozer.MappingException: java.lang.InstantiationException: 
> org.apache.camel.converter.dozer.DozerThreadContextClassLoader
>   at 
> org.dozer.util.MappingUtils.throwMappingException(MappingUtils.java:82) 
> [dozer-5.5.1.jar:]
>   at org.dozer.util.ReflectionUtils.newInstance(ReflectionUtils.java:366) 
> [dozer-5.5.1.jar:]
>   at 
> org.dozer.DozerInitializer.registerClassLoader(DozerInitializer.java:118) 
> [dozer-5.5.1.jar:]
>   at org.dozer.DozerInitializer.initialize(DozerInitializer.java:98) 
> [dozer-5.5.1.jar:]
>   at org.dozer.DozerInitializer.init(DozerInitializer.java:79) 
> [dozer-5.5.1.jar:]
>   at org.dozer.DozerInitializer.init(DozerInitializer.java:64) 
> [dozer-5.5.1.jar:]
>   at org.dozer.DozerBeanMapper.init(DozerBeanMapper.java:173) 
> [dozer-5.5.1.jar:]
>   at org.dozer.DozerBeanMapper.(DozerBeanMapper.java:99) 
> [dozer-5.5.1.jar:]
>   at 
> org.apache.camel.converter.dozer.DozerTypeConverterLoader.createDozerBeanMapper(DozerTypeConverterLoader.java:232)
>  [camel-dozer-2.16-SNAPSHOT.jar:2.16-SNAPSHOT]
>   at 
> org.apache.camel.converter.dozer.DozerTypeConverterLoader.(DozerTypeConverterLoader.java:118)
>  [camel-dozer-2.16-SNAPSHOT.jar:2.16-SNAPSHOT]
>   at 
> org.wildfly.camel.test.csv.CSVIntegrationTest.testMarshal(CSVIntegrationTest.java:68)
>  [csv-dataformat-tests:]
> ...
> Caused by: java.lang.InstantiationException: 
> org.apache.camel.converter.dozer.DozerThreadContextClassLoader
>   at java.lang.Class.newInstance(Class.java:423) [rt.jar:1.8.0_31]
>   at org.dozer.util.ReflectionUtils.newInstance(ReflectionUtils.java:364) 
> [dozer-5.5.1.jar:]
>   ... 150 more
> Caused by: java.lang.NoSuchMethodException: 
> org.apache.camel.converter.dozer.DozerThreadContextClassLoader.()
>   at java.lang.Class.getConstructor0(Class.java:3074) [rt.jar:1.8.0_31]
>   at java.lang.Class.newInstance(Class.java:408) [rt.jar:1.8.0_31]
>   ... 151 more
> {code}
> The {{org.dozer.DozerInitializer}} does
> {code}
>   private void registerClassLoader(GlobalSettings globalSettings, ClassLoader 
> classLoader, BeanContainer beanContainer) {
> String classLoaderName = globalSettings.getClassLoaderName();
> if (!DozerConstants.DEFAULT_CLASS_LOADER_BEAN.equals(classLoaderName)) {
>   DefaultClassLoader defaultClassLoader = new 
> DefaultClassLoader(classLoader);
>   Class classLoaderType = 
> loadBeanType(classLoaderName, defaultClassLoader, DozerClassLoader.class);
>   DozerClassLoader classLoaderBean = 
> ReflectionUtils.newInstance(classLoaderType);
>   beanContainer.setClassLoader(classLoaderBean);
> }
>   }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-9126) camel-swagger may see unrelated type=context mbeans

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-9126.

Resolution: Fixed
  Assignee: Claus Ibsen

> camel-swagger may see unrelated type=context mbeans
> ---
>
> Key: CAMEL-9126
> URL: https://issues.apache.org/jira/browse/CAMEL-9126
> Project: Camel
>  Issue Type: Bug
>  Components: camel-swagger
>Affects Versions: 2.15.3
>Reporter: Thomas Diesler
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.16.0, 2.15.4
>
>
> {code}
> val names = server.queryNames(new ObjectName("*:type=context,*"), null)
> for (name <- names.asScala) {
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-9125) Cannot build camel-scr-example

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-9125.

   Resolution: Fixed
 Assignee: Claus Ibsen
Fix Version/s: 2.15.4

Its only the archetype that generated invalid unit test code.

> Cannot build camel-scr-example
> --
>
> Key: CAMEL-9125
> URL: https://issues.apache.org/jira/browse/CAMEL-9125
> Project: Camel
>  Issue Type: Bug
>  Components: camel-scr, tooling
>Affects Versions: 2.15.4
>Reporter: Thomas Diesler
>Assignee: Claus Ibsen
> Fix For: 2.15.4
>
>
> affects branch 2.15.x
> {code}
> [INFO] [INFO] --- maven-compiler-plugin:2.5.1:testCompile 
> (default-testCompile) @ camel-scr-example ---
> [INFO] [INFO] Compiling 1 source file to 
> /Users/tdiesler/git/camel/tooling/archetypes/camel-archetype-scr/target/test-classes/projects/camel-scr-example/project/camel-scr-example/target/test-classes
> [INFO] [INFO] -
> [INFO] [ERROR] COMPILATION ERROR : 
> [INFO] [INFO] -
> [INFO] [ERROR] 
> /Users/tdiesler/git/camel/tooling/archetypes/camel-archetype-scr/target/test-classes/projects/camel-scr-example/project/camel-scr-example/src/test/java/example/CamelScrExampleTest.java:[44,40]
>  error: incompatible types: CamelContext cannot be converted to 
> ModelCamelContext
> [INFO] [INFO] 1 error
> [INFO] [INFO] -
> [INFO] [INFO] 
> 
> [INFO] [INFO] BUILD FAILURE
> [INFO] [INFO] 
> 
> [INFO] [INFO] Total time: 2.409 s
> [INFO] [INFO] Finished at: 2015-09-09T15:19:20+02:00
> [INFO] [INFO] Final Memory: 22M/243M
> [INFO] [INFO] 
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-9123) Camel is not invoking JAX-RS Client (jax-rs) providers" readFrom" method while returing the response back to the CXF server

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-9123:
---
Priority: Major  (was: Critical)

> Camel is not invoking JAX-RS Client (jax-rs) providers" readFrom" method 
> while returing the response back to the CXF server
> ---
>
> Key: CAMEL-9123
> URL: https://issues.apache.org/jira/browse/CAMEL-9123
> Project: Camel
>  Issue Type: Bug
>  Components: camel-cxfrs
>Affects Versions: 2.15.3
>Reporter: Varun
>
> I have a CXF JAX-RS server talking to a CXF JAX-rs client in my camel route, 
> The RS client inturn talks to REST API, both the server and client have been 
> configured with custom JAX-RS providers to perform custom 
> deserlization/serilizations. The JAX-RS server "readFrom" method is invoked 
> followed by the clients "writeTo" which perfroms the  REST API call once the 
> API rerurns the response , camel is not invoking CXF client providers 
> readFrom/isReadable method, rather  its directly calling JAX-RS servers 
> writeTO method where the Object is coming as LoadedByteArray instead of the 
> actual Java POJO.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-8734) camel-netty-http - Should ignore case of context-path

[JIRA]

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

Frédérik ROULEAU commented on CAMEL-8734:
-

The problem is that the HTTP_PATH header is modified, and thus the case 
insensitiveness is not only for context match.
See in netty4, DefaultNettyHttpBinding.java  the path is converted to lower 
case and put back to header,  overwritting the original HTTP_PATH. :

if (configuration.getPath() != null) {
  // need to match by lower case as we want to ignore case on context-path
  path = path.toLowerCase(Locale.US);
  
}
headers.put(Exchange.HTTP_PATH, path);

> camel-netty-http - Should ignore case of context-path
> -
>
> Key: CAMEL-8734
> URL: https://issues.apache.org/jira/browse/CAMEL-8734
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-netty-http, camel-netty4-http
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
> Fix For: 2.15.3, 2.16.0
>
>
> We should ignore case when matching context-path. We have some code that 
> matches using .startsWith. But that does not match with different case, such 
> as Customer vs customer.
> People dont really want to expose HTTP services where the context path uses 
> different case. So if people type /customer or /Customer or /CUSTOMER then it 
> should match the same.
> See nabble
> http://camel.465427.n5.nabble.com/How-to-create-case-insensitive-URI-route-with-netty4-http-tp5766517.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-8748) DozerBeanMapper cannot instantiate DozerThreadContextClassLoader

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-8748:
---

Github user tdiesler closed the pull request at:

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


> DozerBeanMapper cannot instantiate DozerThreadContextClassLoader 
> -
>
> Key: CAMEL-8748
> URL: https://issues.apache.org/jira/browse/CAMEL-8748
> Project: Camel
>  Issue Type: Bug
>  Components: camel-dozer
>Affects Versions: 2.15.3
>Reporter: Thomas Diesler
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.16.0, 2.15.4
>
>
> {code}
> 15:26:16,518 SEVERE [org.jboss.arquillian.protocol.jmx.JMXTestRunner] 
> (pool-2-thread-1) Failed: 
> org.wildfly.camel.test.csv.CSVIntegrationTest.testMarshal: 
> org.dozer.MappingException: java.lang.InstantiationException: 
> org.apache.camel.converter.dozer.DozerThreadContextClassLoader
>   at 
> org.dozer.util.MappingUtils.throwMappingException(MappingUtils.java:82) 
> [dozer-5.5.1.jar:]
>   at org.dozer.util.ReflectionUtils.newInstance(ReflectionUtils.java:366) 
> [dozer-5.5.1.jar:]
>   at 
> org.dozer.DozerInitializer.registerClassLoader(DozerInitializer.java:118) 
> [dozer-5.5.1.jar:]
>   at org.dozer.DozerInitializer.initialize(DozerInitializer.java:98) 
> [dozer-5.5.1.jar:]
>   at org.dozer.DozerInitializer.init(DozerInitializer.java:79) 
> [dozer-5.5.1.jar:]
>   at org.dozer.DozerInitializer.init(DozerInitializer.java:64) 
> [dozer-5.5.1.jar:]
>   at org.dozer.DozerBeanMapper.init(DozerBeanMapper.java:173) 
> [dozer-5.5.1.jar:]
>   at org.dozer.DozerBeanMapper.(DozerBeanMapper.java:99) 
> [dozer-5.5.1.jar:]
>   at 
> org.apache.camel.converter.dozer.DozerTypeConverterLoader.createDozerBeanMapper(DozerTypeConverterLoader.java:232)
>  [camel-dozer-2.16-SNAPSHOT.jar:2.16-SNAPSHOT]
>   at 
> org.apache.camel.converter.dozer.DozerTypeConverterLoader.(DozerTypeConverterLoader.java:118)
>  [camel-dozer-2.16-SNAPSHOT.jar:2.16-SNAPSHOT]
>   at 
> org.wildfly.camel.test.csv.CSVIntegrationTest.testMarshal(CSVIntegrationTest.java:68)
>  [csv-dataformat-tests:]
> ...
> Caused by: java.lang.InstantiationException: 
> org.apache.camel.converter.dozer.DozerThreadContextClassLoader
>   at java.lang.Class.newInstance(Class.java:423) [rt.jar:1.8.0_31]
>   at org.dozer.util.ReflectionUtils.newInstance(ReflectionUtils.java:364) 
> [dozer-5.5.1.jar:]
>   ... 150 more
> Caused by: java.lang.NoSuchMethodException: 
> org.apache.camel.converter.dozer.DozerThreadContextClassLoader.()
>   at java.lang.Class.getConstructor0(Class.java:3074) [rt.jar:1.8.0_31]
>   at java.lang.Class.newInstance(Class.java:408) [rt.jar:1.8.0_31]
>   ... 151 more
> {code}
> The {{org.dozer.DozerInitializer}} does
> {code}
>   private void registerClassLoader(GlobalSettings globalSettings, ClassLoader 
> classLoader, BeanContainer beanContainer) {
> String classLoaderName = globalSettings.getClassLoaderName();
> if (!DozerConstants.DEFAULT_CLASS_LOADER_BEAN.equals(classLoaderName)) {
>   DefaultClassLoader defaultClassLoader = new 
> DefaultClassLoader(classLoader);
>   Class classLoaderType = 
> loadBeanType(classLoaderName, defaultClassLoader, DozerClassLoader.class);
>   DozerClassLoader classLoaderBean = 
> ReflectionUtils.newInstance(classLoaderType);
>   beanContainer.setClassLoader(classLoaderBean);
> }
>   }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (CAMEL-8596) Add getRequestHeaders to JettyContentExchange

[Claus Ibsen (JIRA)]

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

Claus Ibsen reassigned CAMEL-8596:
--

Assignee: Claus Ibsen

> Add getRequestHeaders to JettyContentExchange
> -
>
> Key: CAMEL-8596
> URL: https://issues.apache.org/jira/browse/CAMEL-8596
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-jetty
>Affects Versions: 2.15.1
>Reporter: Mateusz Nowakowski
>Assignee: Claus Ibsen
> Fix For: Future
>
> Attachments: 8596.patch
>
>
> Could you add
> Map getRequestHeaders() method to 
> JettyContentExchange interface?
> Context:
> In Camel 2.14.x JettyContentExchange was a class extending ContentExchange so 
> that it gives access to ContentExchange methods.
> Currently it is an interface and it is impossible to access (without hacking 
> access to private final field hell yeah ]:->)  for example in order to 
> access to HTTP request headers...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-8596) Add getRequestHeaders to JettyContentExchange

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-8596.

   Resolution: Fixed
Fix Version/s: (was: Future)
   2.16.0

Thanks James for the patch.

> Add getRequestHeaders to JettyContentExchange
> -
>
> Key: CAMEL-8596
> URL: https://issues.apache.org/jira/browse/CAMEL-8596
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-jetty
>Affects Versions: 2.15.1
>Reporter: Mateusz Nowakowski
>Assignee: Claus Ibsen
> Fix For: 2.16.0
>
> Attachments: 8596.patch
>
>
> Could you add
> Map getRequestHeaders() method to 
> JettyContentExchange interface?
> Context:
> In Camel 2.14.x JettyContentExchange was a class extending ContentExchange so 
> that it gives access to ContentExchange methods.
> Currently it is an interface and it is impossible to access (without hacking 
> access to private final field hell yeah ]:->)  for example in order to 
> access to HTTP request headers...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9094) Can't use custom FTPParser on OSGI

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-9094:
---

GitHub user cunningt opened a pull request:

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

CAMEL-9094 Can't use custom FTPParser on OSGI

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

Use ClassResolver to resolve class instead of Class.forName in 
DefaultFTPFileEntryParserFactory 

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

$ git pull https://github.com/cunningt/camel CAMEL-9094

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

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


commit 6e1950d349a66298a315a63a0bb1db34fe7db715
Author: cunningt 
Date:   2015-09-11T20:12:17Z

CAMEL-9094 Can't use custom FTPParser on OSGI




> Can't use custom FTPParser on OSGI
> --
>
> Key: CAMEL-9094
> URL: https://issues.apache.org/jira/browse/CAMEL-9094
> Project: Camel
>  Issue Type: Bug
>  Components: camel-ftp
>Affects Versions: 2.15.2
>Reporter: Tom Cunningham
>Priority: Minor
> Fix For: Future
>
>
> Using a custom ftp entry parser on OSGI results in an exception because of 
> the use of Class.forName in commons-net DefaultFTPFileEntryParserFactory :
> {code}
> org.apache.commons.net.ftp.parser.ParserInitializationException: Unknown 
> parser type: com.example.CustomFTPEntryParser
>  
> at 
> org.apache.commons.net.ftp.parser.DefaultFTPFileEntryParserFactory.createFileEntryParser(DefaultFTPFileEntryParserFactory.java:166)[commons-net:commons-net:3.3]
> at 
> org.apache.commons.net.ftp.parser.DefaultFTPFileEntryParserFactory.createFileEntryParser(DefaultFTPFileEntryParserFactory.java:202)[commons-net:commons-net:3.3]
> at 
> org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:3246)[commons-net:commons-net:3.3]
> at 
> org.apache.commons.net.ftp.FTPClient.listFiles(FTPClient.java:2930)[commons-net:commons-net:3.3]
> at 
> org.apache.commons.net.ftp.FTPClient.listFiles(FTPClient.java:2977)[commons-net:commons-net:3.3]
> at 
> org.apache.camel.component.file.remote.FtpOperations.listFiles(FtpOperations.java:779)[org.apache.camel:camel-ftp:2.12.0.redhat-611433]
> at 
> org.apache.camel.component.file.remote.FtpConsumer.doPollDirectory(FtpConsumer.java:91)[org.apache.camel:camel-ftp:2.12.0.redhat-611433]
> at 
> org.apache.camel.component.file.remote.FtpConsumer.pollDirectory(FtpConsumer.java:53)[org.apache.camel:camel-ftp:2.12.0.redhat-611433]
> at 
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:117)[org.apache.camel:camel-core:2.12.0.redhat-611433
>  com.googlecode.concurrentlinkedhashmap:concurrentlinkedhashmap-lru:1.4]
> at 
> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:187)[org.apache.camel:camel-core:2.12.0.redhat-611433
>  com.googlecode.concurrentlinkedhashmap:concurrentlinkedhashmap-lru:1.4]
> at 
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:114)[org.apache.camel:camel-core:2.12.0.redhat-611433
>  com.googlecode.concurrentlinkedhashmap:concurrentlinkedhashmap-lru:1.4]
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)[:1.7.0_10]
> at 
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)[:1.7.0_10]
> at 
> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)[:1.7.0_10]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)[:1.7.0_10]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.7.0_10]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)[:1.7.0_10]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)[:1.7.0_10]
> at java.lang.Thread.run(Thread.java:722)[:1.7.0_10]
> {code}
> Camel can work around this by creating a ParserFactory that is used if Camel 
> is being used in an OSGI environment that simply extends the 
> DefaultFTPFileEntryParserFactory and uses the Camel class resolver rather 
> than Class.forName.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9094) Can't use custom FTPParser on OSGI

[Tom Cunningham (JIRA)]

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

Tom Cunningham commented on CAMEL-9094:
---

Submitted a pull :

https://github.com/apache/camel/pull/610/files

> Can't use custom FTPParser on OSGI
> --
>
> Key: CAMEL-9094
> URL: https://issues.apache.org/jira/browse/CAMEL-9094
> Project: Camel
>  Issue Type: Bug
>  Components: camel-ftp
>Affects Versions: 2.15.2
>Reporter: Tom Cunningham
>Priority: Minor
> Fix For: Future
>
>
> Using a custom ftp entry parser on OSGI results in an exception because of 
> the use of Class.forName in commons-net DefaultFTPFileEntryParserFactory :
> {code}
> org.apache.commons.net.ftp.parser.ParserInitializationException: Unknown 
> parser type: com.example.CustomFTPEntryParser
>  
> at 
> org.apache.commons.net.ftp.parser.DefaultFTPFileEntryParserFactory.createFileEntryParser(DefaultFTPFileEntryParserFactory.java:166)[commons-net:commons-net:3.3]
> at 
> org.apache.commons.net.ftp.parser.DefaultFTPFileEntryParserFactory.createFileEntryParser(DefaultFTPFileEntryParserFactory.java:202)[commons-net:commons-net:3.3]
> at 
> org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:3246)[commons-net:commons-net:3.3]
> at 
> org.apache.commons.net.ftp.FTPClient.listFiles(FTPClient.java:2930)[commons-net:commons-net:3.3]
> at 
> org.apache.commons.net.ftp.FTPClient.listFiles(FTPClient.java:2977)[commons-net:commons-net:3.3]
> at 
> org.apache.camel.component.file.remote.FtpOperations.listFiles(FtpOperations.java:779)[org.apache.camel:camel-ftp:2.12.0.redhat-611433]
> at 
> org.apache.camel.component.file.remote.FtpConsumer.doPollDirectory(FtpConsumer.java:91)[org.apache.camel:camel-ftp:2.12.0.redhat-611433]
> at 
> org.apache.camel.component.file.remote.FtpConsumer.pollDirectory(FtpConsumer.java:53)[org.apache.camel:camel-ftp:2.12.0.redhat-611433]
> at 
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:117)[org.apache.camel:camel-core:2.12.0.redhat-611433
>  com.googlecode.concurrentlinkedhashmap:concurrentlinkedhashmap-lru:1.4]
> at 
> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:187)[org.apache.camel:camel-core:2.12.0.redhat-611433
>  com.googlecode.concurrentlinkedhashmap:concurrentlinkedhashmap-lru:1.4]
> at 
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:114)[org.apache.camel:camel-core:2.12.0.redhat-611433
>  com.googlecode.concurrentlinkedhashmap:concurrentlinkedhashmap-lru:1.4]
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)[:1.7.0_10]
> at 
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)[:1.7.0_10]
> at 
> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)[:1.7.0_10]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)[:1.7.0_10]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.7.0_10]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)[:1.7.0_10]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)[:1.7.0_10]
> at java.lang.Thread.run(Thread.java:722)[:1.7.0_10]
> {code}
> Camel can work around this by creating a ParserFactory that is used if Camel 
> is being used in an OSGI environment that simply extends the 
> DefaultFTPFileEntryParserFactory and uses the Camel class resolver rather 
> than Class.forName.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (CAMEL-9128) Camel-Hazelcast: Add a Ringbuffer producer

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino reassigned CAMEL-9128:
---

Assignee: Andrea Cosentino

> Camel-Hazelcast: Add a Ringbuffer producer
> --
>
> Key: CAMEL-9128
> URL: https://issues.apache.org/jira/browse/CAMEL-9128
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-hazelcast
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 2.16.0
>
>
> A Ringbuffer data structure is available from Hazelcast 3.5.
> http://docs.hazelcast.org/docs/3.5/manual/html/ringbuffer.html
> I think it can be useful in our producers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-8486) Producer should not bind exchange to queue

[Raymond Cuenen (JIRA)]

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

Raymond Cuenen updated CAMEL-8486:
--
 Flags: Patch
Patch Info: Patch Available

> Producer should not bind exchange to queue
> --
>
> Key: CAMEL-8486
> URL: https://issues.apache.org/jira/browse/CAMEL-8486
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-rabbitmq
>Affects Versions: 2.15.0
>Reporter: Raymond Cuenen
> Fix For: 2.16.0
>
>
> The {{RabbitMQConsumer}} and {{RabbitMQProducer}} classes both use the 
> {{declareExchangeAndQueue(Channel)}} method of the {{RabbitMQEndpoint}} 
> class, where an exchange always is declared and when the {{getQueue}} method 
> does not return {{null}} (line 222) a queue is declared and bound to the 
> exchange.
> First the {{getQueue}} method cannot return {{null}}, since the underlying 
> parameter is initialized at line 75 and as far as I know cannot be set to 
> {{null}} by an URI specification.
> The fact that both the consumer and producer _connect_ the same way is wrong 
> I think. A producer should always publish to a queue or an exchange, while a 
> consumer always consumes from a queue, which optionally can be bound to an 
> exchange.
> I would suggest to make separate declare methods for consumers and producers.
> For consumers:
> * always declare exchange (because of component URI specification)
> * always declare queue (specified name or _random_)
> * bind queue to exchange
> ** basicConsume(, ...)
> For producers:
> * only declare exchange when no queue specified
> ** basicPublish(, routingKey, ...)
> * only declare queue when specified (ignore exchange in URI specification)
> ** basicPublish("", , ...)
> Unless the {{declare=false}} property is specified ofcourse. Note that the 
> binding still needs to be performed for a consumer (even when the queue and 
> the exchange are not declared)
> With this the processing of the camel exchange for a producer might have to 
> be changed also; the current implementation always publishes to the exchange, 
> but it has to publish to the queue (exchange="", routingKey=) in the 
> case a queue is specified.
> Because the current implementation also creates a binding between a (random 
> named) queue and an exchange the RabbitMQ broker is left with unused bounded 
> queues every time the application is started, which results in a new random 
> queue being created. The created queues with their bindings are not deleted 
> after the application stops (might be a bug in the broker. I'm not sure).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-8486) Producer should not bind exchange to queue

[Raymond Cuenen (JIRA)]

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

Raymond Cuenen updated CAMEL-8486:
--
Attachment: change.patch

> Producer should not bind exchange to queue
> --
>
> Key: CAMEL-8486
> URL: https://issues.apache.org/jira/browse/CAMEL-8486
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-rabbitmq
>Affects Versions: 2.15.0
>Reporter: Raymond Cuenen
> Fix For: 2.16.0
>
> Attachments: change.patch
>
>
> The {{RabbitMQConsumer}} and {{RabbitMQProducer}} classes both use the 
> {{declareExchangeAndQueue(Channel)}} method of the {{RabbitMQEndpoint}} 
> class, where an exchange always is declared and when the {{getQueue}} method 
> does not return {{null}} (line 222) a queue is declared and bound to the 
> exchange.
> First the {{getQueue}} method cannot return {{null}}, since the underlying 
> parameter is initialized at line 75 and as far as I know cannot be set to 
> {{null}} by an URI specification.
> The fact that both the consumer and producer _connect_ the same way is wrong 
> I think. A producer should always publish to a queue or an exchange, while a 
> consumer always consumes from a queue, which optionally can be bound to an 
> exchange.
> I would suggest to make separate declare methods for consumers and producers.
> For consumers:
> * always declare exchange (because of component URI specification)
> * always declare queue (specified name or _random_)
> * bind queue to exchange
> ** basicConsume(, ...)
> For producers:
> * only declare exchange when no queue specified
> ** basicPublish(, routingKey, ...)
> * only declare queue when specified (ignore exchange in URI specification)
> ** basicPublish("", , ...)
> Unless the {{declare=false}} property is specified ofcourse. Note that the 
> binding still needs to be performed for a consumer (even when the queue and 
> the exchange are not declared)
> With this the processing of the camel exchange for a producer might have to 
> be changed also; the current implementation always publishes to the exchange, 
> but it has to publish to the queue (exchange="", routingKey=) in the 
> case a queue is specified.
> Because the current implementation also creates a binding between a (random 
> named) queue and an exchange the RabbitMQ broker is left with unused bounded 
> queues every time the application is started, which results in a new random 
> queue being created. The created queues with their bindings are not deleted 
> after the application stops (might be a bug in the broker. I'm not sure).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-9128) Camel-Hazelcast: Add a Ringbuffer producer

[Andrea Cosentino (JIRA)]

Andrea Cosentino created CAMEL-9128:
---

 Summary: Camel-Hazelcast: Add a Ringbuffer producer
 Key: CAMEL-9128
 URL: https://issues.apache.org/jira/browse/CAMEL-9128
 Project: Camel
  Issue Type: New Feature
  Components: camel-hazelcast
Reporter: Andrea Cosentino
Priority: Minor
 Fix For: 2.16.0


A Ringbuffer data structure is available from Hazelcast 3.5.

http://docs.hazelcast.org/docs/3.5/manual/html/ringbuffer.html

I think it can be useful in our producers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-9128) Camel-Hazelcast: Add a Ringbuffer producer

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino resolved CAMEL-9128.
-
Resolution: Fixed

> Camel-Hazelcast: Add a Ringbuffer producer
> --
>
> Key: CAMEL-9128
> URL: https://issues.apache.org/jira/browse/CAMEL-9128
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-hazelcast
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 2.16.0
>
>
> A Ringbuffer data structure is available from Hazelcast 3.5.
> http://docs.hazelcast.org/docs/3.5/manual/html/ringbuffer.html
> I think it can be useful in our producers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9123) Camel is not invoking JAX-RS Client (jax-rs) providers" readFrom" method while returing the response back to the CXF server

[Willem Jiang (JIRA)]

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

Willem Jiang commented on CAMEL-9123:
-

You are using the [SimpleConsumer binding 
style|https://camel.apache.org/cxfrs#CXFRS-ConsumingaRESTRequest-SimpleBindingStyle]
 which just provides a simple way for the camel route to access the RS request 
message data from the camel message. As it skip the some process of the 
original CXF RS.


> Camel is not invoking JAX-RS Client (jax-rs) providers" readFrom" method 
> while returing the response back to the CXF server
> ---
>
> Key: CAMEL-9123
> URL: https://issues.apache.org/jira/browse/CAMEL-9123
> Project: Camel
>  Issue Type: Bug
>  Components: camel-cxfrs
>Affects Versions: 2.15.3
>Reporter: Varun
>
> I have a CXF JAX-RS server talking to a CXF JAX-rs client in my camel route, 
> The RS client inturn talks to REST API, both the server and client have been 
> configured with custom JAX-RS providers to perform custom 
> deserlization/serilizations. The JAX-RS server "readFrom" method is invoked 
> followed by the clients "writeTo" which perfroms the  REST API call once the 
> API rerurns the response , camel is not invoking CXF client providers 
> readFrom/isReadable method, rather  its directly calling JAX-RS servers 
> writeTO method where the Object is coming as LoadedByteArray instead of the 
> actual Java POJO.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-8734) camel-netty-http - Should ignore case of context-path

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-8734:


Thanks the header is no longer lower cased but kept as is. Fixed on both master 
and 2.15.x branch.

> camel-netty-http - Should ignore case of context-path
> -
>
> Key: CAMEL-8734
> URL: https://issues.apache.org/jira/browse/CAMEL-8734
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-netty-http, camel-netty4-http
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
> Fix For: 2.15.3, 2.16.0
>
>
> We should ignore case when matching context-path. We have some code that 
> matches using .startsWith. But that does not match with different case, such 
> as Customer vs customer.
> People dont really want to expose HTTP services where the context path uses 
> different case. So if people type /customer or /Customer or /CUSTOMER then it 
> should match the same.
> See nabble
> http://camel.465427.n5.nabble.com/How-to-create-case-insensitive-URI-route-with-netty4-http-tp5766517.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-9120) Add Camel-Undertow to Camel features

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino resolved CAMEL-9120.
-
Resolution: Fixed

> Add Camel-Undertow to Camel features
> 
>
> Key: CAMEL-9120
> URL: https://issues.apache.org/jira/browse/CAMEL-9120
> Project: Camel
>  Issue Type: Task
>  Components: camel-undertow
>Reporter: Andrea Cosentino
>
> Actually camel-undertow is not available as feature. I think we have to add 
> it to features list.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-8373) rest-dsl - CORS may have issue with non simple requests

[Charles Moulliard (JIRA)]

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

Charles Moulliard commented on CAMEL-8373:
--

Such option should be added for REST DSL. Otherwise we can't answer to CORS 
preflight requests of Swagger where OPTIONS requests are send

> rest-dsl - CORS may have issue with non simple requests
> ---
>
> Key: CAMEL-8373
> URL: https://issues.apache.org/jira/browse/CAMEL-8373
> Project: Camel
>  Issue Type: Task
>  Components: camel-core
>Affects Versions: 2.14.1
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>
> Look into reported on SO
> http://stackoverflow.com/questions/28562817/camel-rest-dsl-enablecors-only-working-for-get
> For non simple requests, such as PUT see
> http://www.w3.org/TR/cors/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-8821) Support to disable the stream caching in camel-servlet from the camel context

[Mateusz Nowakowski (JIRA)]

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

Mateusz Nowakowski commented on CAMEL-8821:
---

HttpHelper helper class wasn't merged to 2.15.3.



> Support to disable the stream caching in camel-servlet from the camel context
> -
>
> Key: CAMEL-8821
> URL: https://issues.apache.org/jira/browse/CAMEL-8821
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-servlet
>Affects Versions: 2.14.3, 2.15.2
>Reporter: Willem Jiang
>Assignee: Willem Jiang
> Fix For: 2.15.3, 2.16.0, 2.14.4
>
>
> Current camel-servlet doesn't support to disable the stream caching from the 
> camel context, it just check the exchange property for it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (CAMEL-9120) Add Camel-Undertow to Camel features

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino reassigned CAMEL-9120:
---

Assignee: Andrea Cosentino

> Add Camel-Undertow to Camel features
> 
>
> Key: CAMEL-9120
> URL: https://issues.apache.org/jira/browse/CAMEL-9120
> Project: Camel
>  Issue Type: Task
>  Components: camel-undertow
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
>
> Actually camel-undertow is not available as feature. I think we have to add 
> it to features list.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-8821) Support to disable the stream caching in camel-servlet from the camel context

[Willem Jiang (JIRA)]

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

Willem Jiang commented on CAMEL-8821:
-

I just checked the patches which were merged into 2.15.x, they should be part 
of Camel 2.15.3.
Can you double check it ?

> Support to disable the stream caching in camel-servlet from the camel context
> -
>
> Key: CAMEL-8821
> URL: https://issues.apache.org/jira/browse/CAMEL-8821
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-servlet
>Affects Versions: 2.14.3, 2.15.2
>Reporter: Willem Jiang
>Assignee: Willem Jiang
> Fix For: 2.15.3, 2.16.0, 2.14.4
>
>
> Current camel-servlet doesn't support to disable the stream caching from the 
> camel context, it just check the exchange property for it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)