The Apache Jenkins build system has built Camel.trunk.notest (build #2908)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/2908/
to view the results.
Hi,
On 10/17/2016 03:32 PM, Siano, Stephan wrote:
Hi,
I am not sure if I really understand the concept behind this. Is there any text
about the general ideas behind these changes?
Good question, here is the original proposal my colleague made. "1) Extend the
DSL" is what I implemented.
http
Github user Fabryprog closed the pull request at:
https://github.com/apache/camel/pull/1211
---
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
Hi Claus,
OK, I will create a JIRA task for it and start working. As these are seven
components to extend (and test), it might take a little time...
Best regards
Stephan
-Original Message-
From: Claus Ibsen [mailto:claus.ib...@gmail.com]
Sent: Montag, 17. Oktober 2016 12:28
To: dev
Su
Hi
Yeah that would work. The only downside is that camel-http-common has
a dependency on the servlet API which not all the HTTP components are
using. However its just one extra JAR on the classpath.
On Mon, Oct 17, 2016 at 10:58 AM, Siano, Stephan wrote:
> Hi Claus,
>
> Having the interface (an
Hi Claus,
Having the interface (and implementations) in camel-http-common makes sense to
me. This means that all the components below would have a dependency to
camel-http-common. Does this make sense?
I would implement the support for cookies in the producer endpoints for
camel-ahc
camel-cxf
c
Hi
I dont think cookie belongs in camel-core, and a better place is
likely something like camel-http-common.
And there are other http client components such as camel-nett4-http,
camel-jetty, camel-undertow as well. And then for REST based there is
camel-restlet and maybe camel-spark-rest.
And for
