[GitHub] camel pull request: [CAMEL-8748] DozerBeanMapper cannot instantiat...

Github user tdiesler closed the pull request at: https://github.com/apache/camel/pull/570 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: To CXF experts: Setting of SOAP headers via the Camel Header org.apache.cxf.headers.Header.list for CXF data format PAYLOAD

Hi Aki, there will be no change to the old behavior. Suppose you have the following scenario: A SOAP client sends to a CAMEL CXF consumer and this consumer just forwards the message to a Camel CXF provider which calls a receiver SOAP server. If the SOAP client sends a SAP Header then this header

[GitHub] camel pull request: [CAMEL-8748] DozerBeanMapper cannot instantiat...

GitHub user tdiesler opened a pull request: https://github.com/apache/camel/pull/570 [CAMEL-8748] DozerBeanMapper cannot instantiate DozerThreadContextCla… …ssLoader You can merge this pull request into a Git repository by running: $ git pull

Re: To CXF experts: Setting of SOAP headers via the Camel Header org.apache.cxf.headers.Header.list for CXF data format PAYLOAD

Hi Franz, but the headers were transferred when you had the CXFPayload message directly transferred from one end to the other, no? In other words, that was the case when the scenario is really doing nothing at all with the payload. But in a scenario where something between modifies the payload

[GitHub] camel pull request: [CAMEL-9026] ClassNotFoundException: kafka.ser...

GitHub user tdiesler opened a pull request: https://github.com/apache/camel/pull/571 [CAMEL-9026] ClassNotFoundException: kafka.serializer.StringEncoder https://issues.apache.org/jira/browse/CAMEL-9026 You can merge this pull request into a Git repository by running: $ git

[GitHub] camel pull request: CAMEL-9021: camel-sip: change dependency to or...

GitHub user dpocock opened a pull request: https://github.com/apache/camel/pull/572 CAMEL-9021: camel-sip: change dependency to org.opentelecoms.sip / sip-api-1.2 You can merge this pull request into a Git repository by running: $ git pull https://github.com/dpocock/camel

Re: To CXF experts: Setting of SOAP headers via the Camel Header org.apache.cxf.headers.Header.list for CXF data format PAYLOAD

Hi, Franz and I had an offline discussion about this and came to a conclusion that we introduce this behavior as default from camel 2.16. Although this change may likely introduce a regression to some CXF to CXF Payload scenarios using WS extensions, an option to avoid this issue such as

Re: Installing camel-cxf 2.15.2 feature leads to two versions of ServiceMix Stax-API bundles installed

So maybe the camel-core can use the 2.4.0 version? https://github.com/apache/camel/blob/master/parent/pom.xml#L430 On Thu, Jul 23, 2015 at 6:53 PM, Aki Yoshida elak...@gmail.com wrote: I am wondering if there is a way to avoid this awkward situation. When you install camel-cxf 2.15.2 feature

Re: Camel-extras old guava?

Maybe try it out yourself and provide a patch to the camel extra project. Not sure what guava version neo4j needs On Wed, Jul 22, 2015 at 10:01 PM, Daniel Pocock dan...@pocock.pro wrote: Camel-extras has servicemix.bundles.guava-version11.0.2_2/servicemix.bundles.guava-version and it is

Camel.trunk.notest - Build # 2458 - Fixed

The Apache Jenkins build system has built Camel.trunk.notest (build #2458) Status: Fixed Check console output at https://builds.apache.org/job/Camel.trunk.notest/2458/ to view the results.