[jira] [Commented] (CAMEL-9108) Camel Kafka component builds Producer topic off of message instead of to() URI
[
https://issues.apache.org/jira/browse/CAMEL-9108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736968#comment-14736968
]
ASF GitHub Bot commented on CAMEL-9108:
---
Github user williamd1618 closed the pull request at:
https://github.com/apache/camel/pull/597
> Camel Kafka component builds Producer topic off of message instead of to() URI
> --
>
> Key: CAMEL-9108
> URL: https://issues.apache.org/jira/browse/CAMEL-9108
> Project: Camel
> Issue Type: Bug
> Components: camel-kafka
>Affects Versions: 2.15.0, 2.15.1, 2.15.2, 2.15.3
> Environment: All
>Reporter: Daniel Williams
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> It was noticed in camel-kafka 2.15.3 that the KafkaProducer was reading the
> kafka.TOPIC off of the Exchange envelope instead of reading it off of the
> configured KafkaEndpoint/Configuration which subsequently breaks the ability
> to route messages from a Kafka topic to a Kafka topic based upon a Predicate.
> ```
> from("kafka:localhost:9092?topic=A&groupId=B").to("kafka:localhost:9092?topic=B.")
> ```
> I've created a pull request on github that addresses this issue:
> https://github.com/apache/camel/pull/597
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-7921) The soapAction HTTP header is not correctly set when running the CXF client in POJO mode using Camel
[
https://issues.apache.org/jira/browse/CAMEL-7921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736939#comment-14736939
]
Ton Swieb commented on CAMEL-7921:
--
Hi [~ffang],
Thanks for fixing this.
> The soapAction HTTP header is not correctly set when running the CXF client
> in POJO mode using Camel
>
>
> Key: CAMEL-7921
> URL: https://issues.apache.org/jira/browse/CAMEL-7921
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf
>Affects Versions: 2.12.3, 2.12.4, 2.13.2, 2.14.0
>Reporter: Ton Swieb
>Assignee: Freeman Fang
> Fix For: 2.16.0, 2.14.4, 2.15.4
>
> Attachments: soapActionTest.zip
>
>
> The soapAction HTTP header is not correctly set when running the CXF client
> in POJO mode using Camel.
> The root cause seems to be that the service name from the generated service
> class differs from the service name in the WSDL.
> For me it is unclear if this should be an issue with the cxf-codegen-plugin
> or with the Camel CXF component. When running the CXF client without Camel
> then the soapAction HTTP header is correctly set and the issue does not
> occur. So that's why I first report the bug with Camel.
> Possible workarounds I found are:
> 1) Explicitly specifying the correct serviceName as CXF endpoint attribute.
> 2) Explicitly setting the soapAction header in the Camel route prior to
> calling the CXF endpoint.
> Both workarounds are not desirable, because they are easily forgotten and CXF
> does not throw an exception when you do. According to the basic profile v1.0
> the soapAction HTTP header must match the value in the WSDL and receiving
> SOAP servers may throw a SOAP Fault if it doesn't. Some SOAP servers do throw
> an exception when the soapAction HTTP header is invalid. Resulting in
> communication failures between some SOAP client/server combinations.
> I created a test project to verify the above behaviour with the following
> tests:
> 1) CXF in PAYLOAD with Camel. => OK
> 2) CXF in POJO mode without Camel => OK
> 3) CXF in POJO mode with Camel => *NOT OK*
> 4) CXF in POJO mode with service name set => OK
> 5) CXF in POJO mode with soapAction set => OK
> I run the test project with multiple combinations of Camel and CXF. The
> following combinations I have tried:
> 1) Camel 2.12.3 and CXF 2.7.10 (Apache Servicemix 5.0.0 setup)
> 2) Camel 2.12.4 and CXF 2.7.11 (Apache Servicemix 5.0.5 setup)
> 3) Camel 2.13.2 and CXF 2.7.11 (Apache Servicemix 5.1.3 and 5.3.0 setup)
> 4) Camel 2.14.0 and CXF 3.0.1
> In the example project the mismatch occurs between an annotation in the
> generated service class:
> {code}
> @WebService(targetNamespace = "http://finalist.nl/ai/";, name =
> "ICamelCxfTestService")
> {code}
> and the definition of the service name in the WSDL:
> {code}
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-9126) camel-swagger may see unrelated type=context mbeans
[
https://issues.apache.org/jira/browse/CAMEL-9126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736935#comment-14736935
]
ASF GitHub Bot commented on CAMEL-9126:
---
GitHub user tdiesler opened a pull request:
https://github.com/apache/camel/pull/609
[CAMEL-9126] camel-swagger may see unrelated type=context mbeans
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tdiesler/camel CAMEL-9126m
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/609.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 #609
commit 6342cda29d7a901433d82d90b7b1fc2c6b189349
Author: Thomas Diesler
Date: 2015-09-09T14:23:19Z
[CAMEL-9126] camel-swagger may see unrelated type=context mbeans
> 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
[
https://issues.apache.org/jira/browse/CAMEL-9126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736933#comment-14736933
]
ASF GitHub Bot commented on CAMEL-9126:
---
GitHub user tdiesler opened a pull request:
https://github.com/apache/camel/pull/608
[CAMEL-9126] camel-swagger may see unrelated type=context mbeans
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tdiesler/camel CAMEL-9126
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/608.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 #608
commit 97233dc866968eadf1b1a3f8145cfeaa81f799a3
Author: Thomas Diesler
Date: 2015-09-09T14:23:19Z
[CAMEL-9126] camel-swagger may see unrelated type=context mbeans
> 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] [Created] (CAMEL-9126) camel-swagger may see unrelated type=context mbeans
Thomas Diesler created CAMEL-9126:
-
Summary: 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-8748) DozerBeanMapper cannot instantiate DozerThreadContextClassLoader
[
https://issues.apache.org/jira/browse/CAMEL-8748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736882#comment-14736882
]
ASF GitHub Bot commented on CAMEL-8748:
---
GitHub user tdiesler opened a pull request:
https://github.com/apache/camel/pull/607
[CAMEL-8748] DozerBeanMapper cannot instantiate DozerThreadContextCla…
…ssLoader
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tdiesler/camel CAMEL-8748
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/607.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 #607
commit 6e5d5ee6c553cb7d94e4a7094d00414676b97983
Author: Thomas Diesler
Date: 2015-07-27T11:57:42Z
[CAMEL-8748] DozerBeanMapper cannot instantiate
DozerThreadContextClassLoader
> 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] [Created] (CAMEL-9125) Cannot build camel-scr-example
Thomas Diesler created CAMEL-9125:
-
Summary: 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
Reporter: Thomas Diesler
Priority: Blocker
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-8748) DozerBeanMapper cannot instantiate DozerThreadContextClassLoader
[
https://issues.apache.org/jira/browse/CAMEL-8748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Diesler updated CAMEL-8748:
--
Fix Version/s: 2.15.4
> 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] [Commented] (CAMEL-8748) DozerBeanMapper cannot instantiate DozerThreadContextClassLoader
[
https://issues.apache.org/jira/browse/CAMEL-8748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736805#comment-14736805
]
Thomas Diesler commented on CAMEL-8748:
---
Reopened, also needed in 2.15.4. I'll provide a PR
> 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] [Reopened] (CAMEL-8748) DozerBeanMapper cannot instantiate DozerThreadContextClassLoader
[
https://issues.apache.org/jira/browse/CAMEL-8748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Diesler reopened CAMEL-8748:
---
> 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
>
>
> {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-9124) RedeliveryPattern should support property placeholders
[ https://issues.apache.org/jira/browse/CAMEL-9124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-9124. Resolution: Fixed > RedeliveryPattern should support property placeholders > -- > > Key: CAMEL-9124 > URL: https://issues.apache.org/jira/browse/CAMEL-9124 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 2.15.3 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 2.16.0, 2.15.4 > > > See nabble > http://camel.465427.n5.nabble.com/Can-t-configure-delayPattern-with-property-placeholders-tp5771356.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-9124) RedeliveryPattern should support property placeholders
Claus Ibsen created CAMEL-9124: -- Summary: RedeliveryPattern should support property placeholders Key: CAMEL-9124 URL: https://issues.apache.org/jira/browse/CAMEL-9124 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.15.3 Reporter: Claus Ibsen Assignee: Claus Ibsen Priority: Minor Fix For: 2.16.0, 2.15.4 See nabble http://camel.465427.n5.nabble.com/Can-t-configure-delayPattern-with-property-placeholders-tp5771356.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (CAMEL-7835) camel-test-spring doesn't support Spring 4.1.0.RELEASE
[ https://issues.apache.org/jira/browse/CAMEL-7835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Sambourg updated CAMEL-7835: Comment: was deleted (was: Same here, stuck with 2.14.x (because of Java 6) but now we can't upgrade Spring to 4.1 because of this. Any chance of a camel-test-spring41 in 2.14.x?) > camel-test-spring doesn't support Spring 4.1.0.RELEASE > -- > > Key: CAMEL-7835 > URL: https://issues.apache.org/jira/browse/CAMEL-7835 > Project: Camel > Issue Type: Task > Components: camel-test >Affects Versions: 2.14.0 >Reporter: Henrik >Assignee: Claus Ibsen > Labels: deprecation, junit, spring, test > Fix For: 2.15.0 > > > CamelSpringJUnit4ClassRunner calls the TestContextManager(Class, String) > constructor, and the > TestContextManager.getDefaultTestExecutionListenerClasses() method. > Both of these are deprecated in spring-test-4.0.x, and are gone in 4.1.x. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7835) camel-test-spring doesn't support Spring 4.1.0.RELEASE
[ https://issues.apache.org/jira/browse/CAMEL-7835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736726#comment-14736726 ] Olivier Sambourg commented on CAMEL-7835: - Same here, stuck with 2.14.x (because of Java 6) but now we can't upgrade Spring to 4.1 because of this. Any chance of a camel-test-spring41 in 2.14.x? > camel-test-spring doesn't support Spring 4.1.0.RELEASE > -- > > Key: CAMEL-7835 > URL: https://issues.apache.org/jira/browse/CAMEL-7835 > Project: Camel > Issue Type: Task > Components: camel-test >Affects Versions: 2.14.0 >Reporter: Henrik >Assignee: Claus Ibsen > Labels: deprecation, junit, spring, test > Fix For: 2.15.0 > > > CamelSpringJUnit4ClassRunner calls the TestContextManager(Class, String) > constructor, and the > TestContextManager.getDefaultTestExecutionListenerClasses() method. > Both of these are deprecated in spring-test-4.0.x, and are gone in 4.1.x. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7835) camel-test-spring doesn't support Spring 4.1.0.RELEASE
[ https://issues.apache.org/jira/browse/CAMEL-7835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736725#comment-14736725 ] Olivier Sambourg commented on CAMEL-7835: - Same here, stuck with 2.14.x (because of Java 6) but now we can't upgrade Spring to 4.1 because of this. Any chance of a camel-test-spring41 in 2.14.x? > camel-test-spring doesn't support Spring 4.1.0.RELEASE > -- > > Key: CAMEL-7835 > URL: https://issues.apache.org/jira/browse/CAMEL-7835 > Project: Camel > Issue Type: Task > Components: camel-test >Affects Versions: 2.14.0 >Reporter: Henrik >Assignee: Claus Ibsen > Labels: deprecation, junit, spring, test > Fix For: 2.15.0 > > > CamelSpringJUnit4ClassRunner calls the TestContextManager(Class, String) > constructor, and the > TestContextManager.getDefaultTestExecutionListenerClasses() method. > Both of these are deprecated in spring-test-4.0.x, and are gone in 4.1.x. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8975) camel-kafka - Message loss with batch commit
[ https://issues.apache.org/jira/browse/CAMEL-8975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736711#comment-14736711 ] Jonathan Anstey commented on CAMEL-8975: [~mcoyote] would you mind submitting a PR for this? Sounds like an awesome improvement! > camel-kafka - Message loss with batch commit > > > Key: CAMEL-8975 > URL: https://issues.apache.org/jira/browse/CAMEL-8975 > Project: Camel > Issue Type: Bug > Components: camel-kafka >Affects Versions: 2.15.2 > Environment: Unbuntu LTS 14.x, Java 7 >Reporter: Michael J. Kitchin > > These issues center around Kafka consumer (KafaConsumer.java, line numbers > below): > # Exchange exceptions/failures ignored at process() (:148), meaning: > ## Automatic offset commit on exchange failure (e.g., processor/endpoint > exception) > ## In-flight exchange loss on Camel context/runtime shutdown (i.e., route > interrupted -> exception suppressed -> offset committed) > # BatchCommitConsumerTask activations are unbalanced during periods of low > activity, meaning: > ## await() (:165) will timeout for active BatchCommitConsumerTask(s) when > other consumer threads are binding on it.hasNext() (:145) (blocking call, > despite no @throws) > ## Any, previously-activated await()'ing thread will (a) get a > TimeoutExeception, (b) loop, and (c) get a BrokenBarrierException on the next > await() call and (d) exit > ## Process will repeat until (a) all consumer stream threads have exited, (b) > leaving consumer dead > ## Aggravated if process() (:148) blocks (e.g., for delay/redelivery on the > route) > # An ExecutorService is obtained from Camel to handle KafkaStreams with # of > threads set to the consumerStreams param (:77). Since the # of KafkaStreams > actually created is (consumersCount * consumerStreams) and executor runnables > are indefinite loops, a random selection of streams will not be serviced if > consumersCount>1. > Source code URL: > - > https://github.com/apache/camel/blob/master/components/camel-kafka/src/main/java/org/apache/camel/component/kafka/KafkaConsumer.java > We've troubleshot this extensively and reimplemented the KafkaConsumer class > with params added to KafkaConfiguration to address these concerns and are > happy to submit these back to the community, if interested. -- 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
[
https://issues.apache.org/jira/browse/CAMEL-9123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736616#comment-14736616
]
Varun commented on CAMEL-9123:
--
{code}
http://localhost:9090/sample-rest-svc/sampleservices";
serviceClass="com.service.ClientServiceImpl"
loggingFeatureEnabled="true">
http://camel.apache.org/schema/spring";>
True
{code}
> 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] [Created] (CAMEL-9123) Camel is not invoking JAX-RS Client (jax-rs) providers" readFrom" method while returing the response back to the CXF server
Varun created CAMEL-9123: Summary: 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-9121) activemq-camel pulls in outdated version of commons-pool2
[
https://issues.apache.org/jira/browse/CAMEL-9121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736388#comment-14736388
]
ASF GitHub Bot commented on CAMEL-9121:
---
Github user tdiesler closed the pull request at:
https://github.com/apache/camel/pull/606
> activemq-camel pulls in outdated version of commons-pool2
> -
>
> Key: CAMEL-9121
> URL: https://issues.apache.org/jira/browse/CAMEL-9121
> Project: Camel
> Issue Type: Bug
> Components: camel-jms
>Reporter: Thomas Diesler
>Assignee: Andrea Cosentino
> Fix For: 2.16.0
>
>
> wildfly-camel generates
> {code:xml}
>
>
>
>
>
>
>
>
> {code}
> although camel defines 2.4.2. This leads to
> {code}
> type org.apache.commons.pool2.impl.DefaultEvictionPolicy
> at
> org.apache.commons.pool2.impl.BaseGenericObjectPool.setEvictionPolicyClassName(BaseGenericObjectPool.java:607)
> at
> org.apache.commons.pool2.impl.GenericKeyedObjectPool.setConfig(GenericKeyedObjectPool.java:257)
> at
> org.apache.commons.pool2.impl.GenericKeyedObjectPool.(GenericKeyedObjectPool.java:111)
> at
> org.apache.commons.pool2.impl.GenericKeyedObjectPool.(GenericKeyedObjectPool.java:86)
> at
> org.apache.activemq.jms.pool.PooledConnectionFactory.initConnectionsPool(PooledConnectionFactory.java:89)
> at
> org.apache.activemq.jms.pool.PooledConnectionFactory.getConnectionsPool(PooledConnectionFactory.java:496)
> at
> org.apache.activemq.jms.pool.PooledConnectionFactory.createConnection(PooledConnectionFactory.java:224)
> at
> org.apache.activemq.jms.pool.PooledConnectionFactory.createConnection(PooledConnectionFactory.java:209)
> at
> org.springframework.jms.support.JmsAccessor.createConnection(JmsAccessor.java:180)
> at
> org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:483)
> at
> org.apache.camel.component.jms.JmsConfiguration$CamelJmsTemplate.send(JmsConfiguration.java:243)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
