GitHub user igarashitm opened a pull request:
https://github.com/apache/camel/pull/1497
CAMEL-10908 Introduce DataTypeAware interface and let MessageSupport â¦
â¦implement it
This also solves CAMEL-10890
This is a follow up of the discussion here:
https://gith
The Apache Jenkins build system has built Camel.trunk.notest.java9 (build #17)
Status: Still Failing
Check console output at
https://builds.apache.org/job/Camel.trunk.notest.java9/17/ to view the results.
OK thanks, sounds like a plan - yep, as this has been same 10 years, changing
this in 2.x would break backward compatibility, so it's fair enough to keep as
is and revisit for 3.0 :)
https://issues.apache.org/jira/browse/CAMEL-10910
Thanks,
Tomo
On 02/28/2017 11:58 PM, Claus Ibsen wrote:
Hi
Hi
This is the behavior of 2.x and the EIPs and routing engine is
optimized / doing this.
We have already done too many changes IMHO in 2.19.x and should not do
more changes for the sake of a change.
Camel 3.0 allows to revisit the routing engine and exchange copy stuff
that happens.
You are we
Hi,
I noticed that if eventDrivenProcessors contains only one processor, IN message
is not copied to OUT even when exchange pattern is InOut while it does if it
contains multiple processors.
eventDrivenProcessors are wrapped with Pipeline here when initiating a camel
route here:
https://githu
Hi
I logged a ticket
https://issues.apache.org/jira/browse/CAMEL-10909
On Wed, Feb 22, 2017 at 9:51 AM, Claus Ibsen wrote:
> Hi
>
> 99% of Camel users are using Java / Java8 / XML DSLs. And they are all
> up to date and aligned.
>
> We have camel-groovy with a little Camel DSL that adds a bit of
Github user igarashitm closed the pull request at:
https://github.com/apache/camel/pull/1492
---
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
No we should not, its just that the adoc should have a row to indicate
if its query or path parameter.
Or we can render the ascii docs with two tables, one for path
parameters and another for query.
To change the render see the camel maven tooling
https://github.com/apache/camel/blob/master/to
Hello,
today I noticed that there is a little difference between the
documentation we are making as asciidoc and the confluence one i.e.:
for the camel-http4 component, the asciidoc one lists httpUri among
the endpoint options whereas the confluence one doesn't.
I think confluence doc is correct
Github user johnpoth closed the pull request at:
https://github.com/apache/camel/pull/1496
---
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 en
Hi
The post is now on the website
http://camel.apache.org/2017/02/28/new-apache-camel-logo-open-for-proposals.html
On Mon, Feb 27, 2017 at 11:06 AM, Claus Ibsen wrote:
> Hi
>
> Okay so I suggest to post this on the front page and mailing lists.
>
> Any comments?
>
>
>
> New Apache Camel Logo - O
GitHub user johnpoth opened a pull request:
https://github.com/apache/camel/pull/1496
CAMEL-10141 skip camel-jibx build on java 9 as well
https://issues.apache.org/jira/browse/CAMEL-10141
We are skipping camel-jibx on JAVA 8 and it's failing on JAVA 9:
```
[ERRO
12 matches
Mail list logo
