Hi Camel developers,
I'd like to propose an enhancement on handling data types of Camel message
contents. To start a smooth discussion I implemented the idea first:
https://github.com/igarashitm/camel/tree/contract-based-type-awareness
And these testcases demonstrates the declarative transforme
The Apache Jenkins build system has built Camel.trunk.notest (build #2875)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/2875/
to view the results.
Hi
Yeah that is a better name
On Thu, Sep 15, 2016 at 6:08 PM, Vitalii Tymchyshyn wrote:
> How about seThreadedAsyncMode(boolean), defailt true?
>
> I will also do checkstyle till EOW.
>
> Best regards, Vitalii Tymchyshyn
>
> Чт, 15 вер. 2016 05:08 користувач Claus Ibsen пише:
>
>> Hi
>>
>> I d
How about seThreadedAsyncMode(boolean), defailt true?
I will also do checkstyle till EOW.
Best regards, Vitalii Tymchyshyn
Чт, 15 вер. 2016 05:08 користувач Claus Ibsen пише:
> Hi
>
> I do wonder if we can come up with a better name for the setter/getter
> of synchronous on ProducerTemplate.
>
Github user hqstevenson closed the pull request at:
https://github.com/apache/camel/pull/1172
---
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
Hi
I do wonder if we can come up with a better name for the setter/getter
of synchronous on ProducerTemplate.
Otherwise great work. The Java 8 API makes the code easier when you
can compose the futures with the thenApply.
Just a note that we must/should ensure that existing Camel users can
take
Github user Fabryprog closed the pull request at:
https://github.com/apache/camel/pull/1177
---
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 e
