Camel.trunk.notest - Build # 2926 - Still Failing

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

[GitHub] camel pull request #1248: CAMEL-10420: Allow custom changes to the pom.xml f...

Github user nicolaferraro closed the pull request at: https://github.com/apache/camel/pull/1248 --- 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

[GitHub] camel pull request #1246: CAMEL-10394: Resolve components from Camel Context

Github user hqstevenson closed the pull request at: https://github.com/apache/camel/pull/1246 --- 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: how to change default namespace ns1 or ns2 added by Camel to custom namespace

Hi Sandesh, you can achieve custom namespace prefixes by customizing the DataBinding, for instance if you're using JAXB: final JAXBDataBinding jaxb = new JAXBDataBinding(); final Map namespacePrefixes = new HashMap<>(); namespacePrefixes.put("http://example.com/namespace";, "examplePrefix"); jaxb

[GitHub] camel pull request #1248: CAMEL-10420: Allow custom changes to the pom.xml f...

GitHub user nicolaferraro opened a pull request: https://github.com/apache/camel/pull/1248 CAMEL-10420: Allow custom changes to the pom.xml files Looking for a review because it's a bit ugly. The aim is not to get the pom.xml of the starters overwritten at each build, and s

how to change default namespace ns1 or ns2 added by Camel to custom namespace

Hi team, I am looking for a technique which will help me change the default namespace (ns1 or ns2) added by Camel to a custom namespace (ser). Below is our XML. http:///soap/envelope/";> http://";> https://";>

Re: camel-properties enhancements

+1. It will need new documentation too I guess. -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix Committer Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Friday, November 4, 2016 10:06 AM, Claus Ibsen wr

Re: camel-properties enhancements

Sounds fine for inclusion in Camel 2.19 onwards. On Thu, Nov 3, 2016 at 1:30 PM, Luca Burgazzoli wrote: > Hi everyone, > > I've been working on a blueprint based applications for soem weeks and > I had to deal with a number of properties placeholders so I've used > camel-properties and I found so

AW: camel-properties enhancements

Hi Luca, sounds good to me. I use them a lot but only basic stuff. So, I never ran into your issues. Just make sure to update the docs. This is tough stuff without examples (yours are good). Cheers, Thomas. -Ursprüngliche Nachricht- Von: Luca Burgazzoli [mailto:lburgazz...@gmail.com]

[GitHub] camel pull request #1247: Added 'preferredAuthentications' option to camel-j...

Github user asfgit closed the pull request at: https://github.com/apache/camel/pull/1247 --- 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 enab