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

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

Re: New Apache Camel Logo

Hi Just a heads up that we have a designer working on some ideas. He posted on twitter https://twitter.com/elioqoshi/status/786965653546729472 And you can find his work at github, where you can also comment directly https://github.com/opensourcedesign/jobs/issues/108 And surely also here in

Re: Enhance ObjectHelper's after/before/between

I've logged two JIRA: - https://issues.apache.org/jira/browse/CAMEL-10389 --> Move some function to Stringhelper (target 2.19) - https://issues.apache.org/jira/browse/CAMEL-10390 --> Enhance before/after/between (target 2.18.1) --- Luca Burgazzoli On Fri, Oct 14, 2016 at 2:38 PM, Antonin

CAMEL-9606 - unsafe transaction synchronization in camel-sjms

Hi, I'm looking into this one and found that camel-sjms is using individual JMS sessions for each endpoints. https://issues.apache.org/jira/browse/CAMEL-9606 As I commented, it causes inconsistency if the process is terminated in the middle of processing those synchronizations, so it doesn't

[GitHub] camel pull request #1212: CAMEL-10387 - Return null if the byte array contai...

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

Re: CAMEL-9606 - unsafe transaction synchronization in camel-sjms

+1 :-) Thanks! -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix Committer Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Friday, October 14, 2016 3:51 PM, Tomohisa Igarashi

Re: CAMEL-9606 - unsafe transaction synchronization in camel-sjms

Hi Yeah that sounds like a good idea. We love contributions On Fri, Oct 14, 2016 at 3:51 PM, Tomohisa Igarashi wrote: > Hi, > > I'm looking into this one and found that camel-sjms is using individual JMS > sessions for each endpoints. >

[GitHub] camel pull request #1210: Camel 10386 simple language nullsafe expression fa...

Github user dmitriyC300 closed the pull request at: https://github.com/apache/camel/pull/1210 --- 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 #1209: CAMEL-10385: springtypeconverter return null on li...

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

Re: Enhance ObjectHelper's after/before/between

> On 14 Oct 2016, at 14:35, Luca Burgazzoli wrote: > > An option would be to move before/after/between in StringHelper and > wrapping them in ObjectHelper with @Deprecated annotation, the > proposed new methods should go straight to StringHelper. I didn’t dare to propose

Re: Enhance ObjectHelper's after/before/between

An option would be to move before/after/between in StringHelper and wrapping them in ObjectHelper with @Deprecated annotation, the proposed new methods should go straight to StringHelper. --- Luca Burgazzoli On Fri, Oct 14, 2016 at 2:25 PM, Antonin Stefanutti wrote: > Hi

Re: Enhance ObjectHelper's after/before/between

Hi Luca, Make sense to me. As I refactored Camel CDI with Java 8 in Camel 2.18.0, I found using Optional as return type of internal util methods quite useful in term of client conciseness / readability compared to null handling. I’m wondering whether that should be added to StringHelper

Enhance ObjectHelper's after/before/between

Hello, I've sometime had the need to find a string after a separator, lookup an object based on the result value and then use it to process something, like: String after = ObjectHelper.after(key, ":"); if (after != null) { MyStuff s = cache.get(after) if (s != null) {

[GitHub] camel pull request #1212: CAMEL-10387 - Return null if the byte array contai...

GitHub user guillaumeterral opened a pull request: https://github.com/apache/camel/pull/1212 CAMEL-10387 - Return null if the byte array contains only 0x0 values You can merge this pull request into a Git repository by running: $ git pull

[GitHub] camel pull request #1211: Camel 10327, New Apache drill component

GitHub user Fabryprog opened a pull request: https://github.com/apache/camel/pull/1211 Camel 10327, New Apache drill component https://issues.apache.org/jira/browse/CAMEL-10327 You can merge this pull request into a Git repository by running: $ git pull