[ANNOUNCEMENT] Apache Camel Quarkus 1.1.0 Released

2020-09-13 Thread James Netherton
The Camel community announces the immediate availability of Apache
Camel Quarkus 1.1.0.

The artifacts are published and ready for you to download either from
the Apache mirrors or from maven central. For more info please visit
the project GitHub repository[1].

Many thanks to all who made this release possible.

Regards,

James

[1] https://github.com/apache/camel-quarkus


Re: Camel-websocket-jsr356 help?

2020-10-29 Thread James Netherton
Maybe try with Camel 3.x if you can because there are a few fixes for
that component that are not present in Camel 2.x.

--
James


On Thu, 29 Oct 2020 at 08:27, jesse moseman  wrote:
>
> I'm trying to use the camel-websocket-jsr356 package but when I try to host
> a websocket via websocket-jsr356://test I get a null pointer exception in
> the consumer for the empty context in there.
> here's the stack trace.
> Caused by: java.lang.NullPointerException: null
> at
> org.apache.camel.websocket.jsr356.JSR356Consumer.doStart(JSR356Consumer.java:72)
> ~[camel-websocket-jsr356-2.24.1.jar:2.24.1]
> at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:72)
> ~[camel-core-2.24.1.jar:2.24.1]
> at
> org.apache.camel.impl.DefaultCamelContext.startService(DefaultCamelContext.java:3709)
> ~[camel-core-2.24.1.jar:2.24.1]
> at
> org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRouteConsumers(DefaultCamelContext.java:4027)
> ~[camel-core-2.24.1.jar:2.24.1]
> at
> org.apache.camel.impl.DefaultCamelContext.doStartRouteConsumers(DefaultCamelContext.java:3962)
> ~[camel-core-2.24.1.jar:2.24.1]
> at
> org.apache.camel.impl.DefaultCamelContext.safelyStartRouteServices(DefaultCamelContext.java:3882)
> ~[camel-core-2.24.1.jar:2.24.1]
> at
> org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRoutes(DefaultCamelContext.java:3646)
> ~[camel-core-2.24.1.jar:2.24.1]
> at
> org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:3489)
> ~[camel-core-2.24.1.jar:2.24.1]
> at
> org.apache.camel.impl.DefaultCamelContext$4.call(DefaultCamelContext.java:3248)
> ~[camel-core-2.24.1.jar:2.24.1]
> at
> org.apache.camel.impl.DefaultCamelContext$4.call(DefaultCamelContext.java:3244)
> ~[camel-core-2.24.1.jar:2.24.1]
> at
> org.apache.camel.impl.DefaultCamelContext.doWithDefinedClassLoader(DefaultCamelContext.java:3267)
> ~[camel-core-2.24.1.jar:2.24.1]
> at
> org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:3244)
> ~[camel-core-2.24.1.jar:2.24.1]
> at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:72)
> ~[camel-core-2.24.1.jar:2.24.1]
> at
> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:3160)
> ~[camel-core-2.24.1.jar:2.24.1]
> at
> org.apache.camel.spring.SpringCamelContext.start(SpringCamelContext.java:133)
> ~[camel-spring-2.24.1.jar:2.24.1]
> Jesse Moseman
> Phone: 402-609-0890 <(402)%20609-0890>
> jmosema...@gmail.com


Re: How to declare a datasource in Camel Quarkus JDBC?

2020-11-30 Thread James Netherton
Take a look at the camel-quarkus JDBC extension integration test:

https://github.com/apache/camel-quarkus/tree/master/integration-tests/jdbc

You can use Quarkus properties to define the datasource in
application.properties:

https://github.com/apache/camel-quarkus/blob/master/integration-tests/jdbc/src/main/resources/application.properties#L21-L23

Then you can refer to the datasource name in your endpoint URI:

https://github.com/apache/camel-quarkus/blob/master/integration-tests/jdbc/src/main/java/org/apache/camel/quarkus/component/jdbc/CamelResource.java#L71

--
James


On Mon, 30 Nov 2020 at 14:01, Mikael Andersson Wigander
 wrote:
>
> How do I declare and inject a datasource for Camel JDBC using Quarkus?
>
> /M


Re: Trace steps in the route with open tracing

2021-07-07 Thread James Netherton
I think it can work if you pass the active span initiated by Camel to the
bean methods. For example:

public class Bean1 {
@Traced
public void methodA(Span span) {
// Do something
}
}

Then in the Camel route:

from("direct:start)
  .process(e -> {
OpenTracingSpanAdapter adapter = (OpenTracingSpanAdapter)
ActiveSpanManager.getSpan(exchange);
Span span = adapter.getOpenTracingSpan();
bean1.methodA(span);
  });

That should be enough for the OpenTracing CDI interceptor to pick up the
propagated span and use it as the parent.

There's probably a more elegant way of achieving this and maybe we can do
some changes in Camel / Camel Quarkus to make it simpler in future, but I'd
have to research it more.

--
James

On Tue, 6 Jul 2021 at 13:59, Dennis Holunder  wrote:

> Hello,
>
> I have some @ApplicationScoped and @Traced Beans which methods are
> called from the camel route (camel-quarkus). The traces are sent to
> jaeger, but they don't have a common parent span. How can I start a
> span for an exchange, so that all subsequent calls to the beans would
> have the same parent span?
>
> In the example I'd want to achieve the trace containing two spans
> (methodA, methodB)
>
> from("direct:start)
> .split()
>   .process(start stracing)
>   .process(e -> bean1.methodA)
>   .process(e -> bean2.methodB)
>.end()
>
>
>
> Thanks!
>


Re: Simple not working with Quarkus

2022-01-27 Thread James Netherton
> Caused by: org.apache.camel.NoSuchLanguageException: No language could be
found for: bean

You need to add a dependency on camel-quarkus-bean.

--
James

On Thu, 27 Jan 2022 at 09:34, Ajmera, Hemang C
 wrote:

> Hi
>.simple is not working with quarkus version 2.6.3 which uses camel
> version 3.14.0.
>
> I have included camel-quarkus-core in pom.xml.
>
> I am getting below error. Kindly let me know if I am missing anything.
>
> 2022-01-27 12:38:33,463 ERROR [io.qua.dep.dev.IsolatedDevModeMain]
> (Timer-0) Failed to start quarkus: java.lang.RuntimeException:
> java.lang.RuntimeException: Failed to start quarkus
> at
> io.quarkus.dev.appstate.ApplicationStateNotification.waitForApplicationStart(ApplicationStateNotification.java:51)
> at
> io.quarkus.runner.bootstrap.StartupActionImpl.runMainClass(StartupActionImpl.java:122)
> at io.quarkus.deployment.dev
> .IsolatedDevModeMain.restartApp(IsolatedDevModeMain.java:233)
> at io.quarkus.deployment.dev
> .IsolatedDevModeMain.restartCallback(IsolatedDevModeMain.java:214)
> at io.quarkus.deployment.dev
> .RuntimeUpdatesProcessor.doScan(RuntimeUpdatesProcessor.java:516)
> at io.quarkus.deployment.dev
> .RuntimeUpdatesProcessor.doScan(RuntimeUpdatesProcessor.java:417)
> at
> org.apache.camel.quarkus.core.devmode.CamelHotReplacementSetup$1.run(CamelHotReplacementSetup.java:36)
> at java.base/java.util.TimerThread.mainLoop(Timer.java:566)
> at java.base/java.util.TimerThread.run(Timer.java:516)
> Caused by: java.lang.RuntimeException: Failed to start quarkus
> at io.quarkus.runner.ApplicationImpl.doStart(Unknown Source)
> at io.quarkus.runtime.Application.start(Application.java:101)
> at
> io.quarkus.runtime.ApplicationLifecycleManager.run(ApplicationLifecycleManager.java:104)
> at io.quarkus.runtime.Quarkus.run(Quarkus.java:67)
> at io.quarkus.runtime.Quarkus.run(Quarkus.java:41)
> at io.quarkus.runtime.Quarkus.run(Quarkus.java:120)
> at io.quarkus.runner.GeneratedMain.main(Unknown Source)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:568)
> at
> io.quarkus.runner.bootstrap.StartupActionImpl$1.run(StartupActionImpl.java:103)
> at java.base/java.lang.Thread.run(Thread.java:833)
> Caused by: java.lang.RuntimeException: java.lang.RuntimeException:
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> route4 at: >>>
> Choice[[When[simple{${exchangeProperty[CamelJdbcRowCount]>0}} ->
> [SetHeader[CamelHttpResponseCode, constant{204}],
> SetBody[org.apache.camel.builder.ExpressionClause@790a50e5
> Otherwise[[SetHeader[CamelHttpResponseCode,
> org.apache.camel.builder.ExpressionClause@139fa961],
> SetBody[org.apache.camel.builder.ExpressionClause@72b159dc <<< in
> route: Route(route4)[From[rest:put:/{service_id}/{key_data}] -> [Se...
> because of No language could be found for: bean
> at
> org.apache.camel.quarkus.core.CamelBootstrapRecorder.start(CamelBootstrapRecorder.java:47)
> at
> io.quarkus.deployment.steps.CamelBootstrapProcessor$boot173480958.deploy_0(Unknown
> Source)
> at
> io.quarkus.deployment.steps.CamelBootstrapProcessor$boot173480958.deploy(Unknown
> Source)
> ... 13 more
> Caused by: java.lang.RuntimeException:
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> route4 at: >>>
> Choice[[When[simple{${exchangeProperty[CamelJdbcRowCount]>0}} ->
> [SetHeader[CamelHttpResponseCode, constant{204}],
> SetBody[org.apache.camel.builder.ExpressionClause@790a50e5
> Otherwise[[SetHeader[CamelHttpResponseCode,
> org.apache.camel.builder.ExpressionClause@139fa961],
> SetBody[org.apache.camel.builder.ExpressionClause@72b159dc <<< in
> route: Route(route4)[From[rest:put:/{service_id}/{key_data}] -> [Se...
> because of No language could be found for: bean
> at
> org.apache.camel.quarkus.main.CamelMainRuntime.start(CamelMainRuntime.java:65)
> at
> org.apache.camel.quarkus.core.CamelBootstrapRecorder.start(CamelBootstrapRecorder.java:45)
> ... 15 more
> Caused by: org.apache.camel.FailedToCreateRouteException: Failed to create
> route route4 at: >>>
> Choice[[When[simple{${exchangeProperty[CamelJdbcRowCount]>0}} ->
> [SetHeader[CamelHttpResponseCode, constant{204}],
> SetBody[org.apache.camel.builder.ExpressionClause@790a50e5
> Otherwise[[SetHeader[CamelHttpResponseCode,
> org.apache.camel.builder.ExpressionClause@139fa961],
> SetBody[org.apache.camel.builder.ExpressionClause@72b159dc <<< in
> route: Route(route4)[From[rest:put:/{service_id}/{key_data}] -> [Se...
> beca

Re: Using reactive datasource in Camel Quarkus?

2023-03-16 Thread James Netherton
Hi,

I don't think it is possible.

The SQL component expects a JDBC datasource, so you'll need to add the
appropriate Quarkus JDBC driver extension + configuration.

I think you should be able to keep most of the datasource configuration the
same as the reactive DS config and add the JDBC specific bits like
quarkus.datasource.jdbc.url etc.

--
James

On Wed, 15 Mar 2023 at 14:50, Mikael Andersson Wigander
 wrote:

> I have an application where I'd like to combine Quarkus Reactive Database
> client and also using Camel SQL component to query same PostgreSQL database.
>
> I can't find any documentation where it states how I should define my
> datasource(s).
>
> Normally with only JDBC it works using the "default" datasource but in
> this case I mix JDBC and Reactive interfaces and turning of JDBC is not
> working
>
> quarkus.datasource.jdbc = false
>
> I have also tried to Inject AgroalDatasource and use that as the pointer
> to SQL component but it doesn't work.
>
> It seems that Camel is hard-wired using a JDBC connection but if I define
> it I will break my Reactive connection it seems.
>
> "Caused by: io.quarkus.runtime.configuration.ConfigurationException:
> Unable to find a JDBC driver corresponding to the database kind
> 'postgresql' for the default datasource. Either provide a suitable JDBC
> driver extension, define the driver manually, or disable the JDBC
> datasource by adding 'quarkus.datasource.jdbc=false' to your configuration
> if you don't need it."
>
> Any clues?
> M


Re: Using reactive datasource in Camel Quarkus?

2023-03-17 Thread James Netherton
Is this what you are trying to achieve?

https://github.com/jamesnetherton/sql-reactive-imperitive

On Fri, 17 Mar 2023 at 09:50, Mikael Andersson Wigander
 wrote:

> Well it seems impossible to have both JDBC and Reactive datasources in
> Quarkus simultaneously when using Camel, when both sources connect to the
> same database.
>
> Even with different DS in the properties file declared it will not work.
>
>
> /M
>
>
> --- Original Message ---
> On Thursday, March 16th, 2023 at 08:46, James Netherton <
> jamesnether...@gmail.com> wrote:
>
>
> > Hi,
> >
> > I don't think it is possible.
> >
> > The SQL component expects a JDBC datasource, so you'll need to add the
> > appropriate Quarkus JDBC driver extension + configuration.
> >
> > I think you should be able to keep most of the datasource configuration
> the
> > same as the reactive DS config and add the JDBC specific bits like
> > quarkus.datasource.jdbc.url etc.
> >
> > --
> > James
> >
> > On Wed, 15 Mar 2023 at 14:50, Mikael Andersson Wigander
> > mikael.andersson.wigan...@pm.me.invalid wrote:
> >
> > > I have an application where I'd like to combine Quarkus Reactive
> Database
> > > client and also using Camel SQL component to query same PostgreSQL
> database.
> > >
> > > I can't find any documentation where it states how I should define my
> > > datasource(s).
> > >
> > > Normally with only JDBC it works using the "default" datasource but in
> > > this case I mix JDBC and Reactive interfaces and turning of JDBC is not
> > > working
> > >
> > > quarkus.datasource.jdbc = false
> > >
> > > I have also tried to Inject AgroalDatasource and use that as the
> pointer
> > > to SQL component but it doesn't work.
> > >
> > > It seems that Camel is hard-wired using a JDBC connection but if I
> define
> > > it I will break my Reactive connection it seems.
> > >
> > > "Caused by: io.quarkus.runtime.configuration.ConfigurationException:
> > > Unable to find a JDBC driver corresponding to the database kind
> > > 'postgresql' for the default datasource. Either provide a suitable JDBC
> > > driver extension, define the driver manually, or disable the JDBC
> > > datasource by adding 'quarkus.datasource.jdbc=false' to your
> configuration
> > > if you don't need it."
> > >
> > > Any clues?
> > > M
>


Re: JQ: Function strftime/1 does not exist

2023-04-18 Thread James Netherton
Hi,

Have you added jackson-jq-extra to the application classpath?

--
James

On Mon, 17 Apr 2023 at 16:32, Mikael Koskinen  wrote:

> Hi,
>
> When using the following JQ expression:
>
> now | strftime("%Y-%d-%m")
>
> I get the following error:
>
>   CaughtExceptionType: org.apache.camel.RuntimeCamelException
> CaughtExceptionMessage:
> net.thisptr.jackson.jq.exception.JsonQueryException: Function
> strftime/1 does not exist  StackTrace:
> org.apache.camel.RuntimeCamelException:
> net.thisptr.jackson.jq.exception.JsonQueryException: Function
> strftime/1 does not exist
> at
> org.apache.camel.language.jq.JqExpression.evaluate(JqExpression.java:198)
> at
> org.apache.camel.support.ExpressionAdapter.evaluate(ExpressionAdapter.java:45)
>
> I checked the following project (which I think Camel uses?)
> https://github.com/eiiches/jackson-jq and based on the documentation,
> I think it should support strftime:
>
>
> https://github.com/eiiches/jackson-jq/blob/ad9dba1eb618640cf8c72634a5ee99c04ddc8e5b/README.md?plain=1#L530
>
> Also tested in this format but same issue:
>
> strftime("-MM-dd")
>
> Here's a link to jqplayground which shows how the function should work:
>
> https://jqplay.org/s/tl0HuDi71wF
>
> Best regards,
> Mikael
>


Re: JQ: Function strftime/1 does not exist

2023-04-18 Thread James Netherton
I created a ticket for it:

https://issues.apache.org/jira/browse/CAMEL-19276

--
James

On Tue, 18 Apr 2023 at 12:57, Claus Ibsen  wrote:

> Hi
>
> Maybe we should include that -extra out of the box in camel-jq
>
> On Tue, Apr 18, 2023 at 1:02 PM James Netherton 
> wrote:
>
> > Hi,
> >
> > Have you added jackson-jq-extra to the application classpath?
> >
> > --
> > James
> >
> > On Mon, 17 Apr 2023 at 16:32, Mikael Koskinen 
> wrote:
> >
> > > Hi,
> > >
> > > When using the following JQ expression:
> > >
> > > now | strftime("%Y-%d-%m")
> > >
> > > I get the following error:
> > >
> > >   CaughtExceptionType: org.apache.camel.RuntimeCamelException
> > > CaughtExceptionMessage:
> > > net.thisptr.jackson.jq.exception.JsonQueryException: Function
> > > strftime/1 does not exist  StackTrace:
> > > org.apache.camel.RuntimeCamelException:
> > > net.thisptr.jackson.jq.exception.JsonQueryException: Function
> > > strftime/1 does not exist
> > > at
> > >
> org.apache.camel.language.jq.JqExpression.evaluate(JqExpression.java:198)
> > > at
> > >
> >
> org.apache.camel.support.ExpressionAdapter.evaluate(ExpressionAdapter.java:45)
> > >
> > > I checked the following project (which I think Camel uses?)
> > > https://github.com/eiiches/jackson-jq and based on the documentation,
> > > I think it should support strftime:
> > >
> > >
> > >
> >
> https://github.com/eiiches/jackson-jq/blob/ad9dba1eb618640cf8c72634a5ee99c04ddc8e5b/README.md?plain=1#L530
> > >
> > > Also tested in this format but same issue:
> > >
> > > strftime("-MM-dd")
> > >
> > > Here's a link to jqplayground which shows how the function should work:
> > >
> > > https://jqplay.org/s/tl0HuDi71wF
> > >
> > > Best regards,
> > > Mikael
> > >
> >
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>


Re: Svar: Re: Unable to get Openapi/swagger in Camel Quarkus

2024-04-11 Thread James Netherton
Hi,

By default, there is no direct integration with quarkus-smallrye-openapi.
If you want your Camel REST services to be published under /q/openapi,
there is a configuration property to enable this:

quarkus.camel.openapi.expose.enabled=true

There's more information here:

https://camel.apache.org/camel-quarkus/3.8.x/reference/extensions/openapi-java.html#extensions-openapi-java-usage

Alternatively, the OpenAPI spec can be resolved as per normal under
/openapi.json or /openapi.yaml:

https://camel.apache.org/components/4.4.x/others/openapi-java.html#_json_or_yaml

--
James

On Wed, 10 Apr 2024 at 10:11, Mikael Andersson Wigander
 wrote:

> Hi and thanks but the result is the same
>
> /M
>
> Den 9 apr. 2024 kl 15:53, Claudio Miranda <[clau...@claudius.com.br
> ](mailto:Den 9 apr. 2024 kl 15:53, Claudio Miranda < skrev:
>
> > Em ter., 9 de abr. de 2024 às 13:50, Mikael Andersson Wigander
> >  escreveu:
> >>
> >> I have a Quarkus Camel application which exposes a REST interface.
> >> I have followed the process of adding the dependencies and created the
> definition but I can not get anything in the Quarkus Swagger UI.
> >
> > you can get this example
> > https://github.com/apache/camel-quarkus-examples/tree/main/rest-json
> >
> > and add the dependencies
> > org.apache.camel.quarkus:camel-quarkus-openapi-java
> > io.quarkus:quarkus-smallrye-openapi
> >
> > and curl localhost:8080/q/openapi
> >
> > Then you can adjust your project to the example
> >
> > --
> > Claudio Miranda
> >
> > clau...@claudius.com.br
> > http://www.claudius.com.br


Re: Camel Quarkus 3.10.0/4.4.5 missing extension?

2024-05-04 Thread James Netherton
Hi,

There is no extension for camel-micrometer-prometheus. You can use
camel-quarkus-micrometer and add an additional dependency for
quarkus-micrometer-registry-prometheus.


io.quarkus
quarkus-micrometer-registry-prometheus


Then all of your metrics will be available on the /q/metrics endpoint.
There's more information here:

https://camel.apache.org/camel-quarkus/next/reference/extensions/micrometer.html#extensions-micrometer-usage

https://quarkus.io/guides/telemetry-micrometer

--
James


On Sat, 4 May 2024 at 17:17, Mikael Andersson Wigander
 wrote:

> Hi
>
> After upgrading my application to Quarkus 3.10.0 with camel 4.4.5 it won’t
> start because it complains about an extension not present in class path:
>
> camel-micrometer-prometheus.
>
> We use Metrics with Micrometer and Prometheus and don’t know what to do
> now.
>
> Can’t find any migration guide covers this, only name changes to tags.
>
> Please advise!
>
> /M


Re: Svar: Re: Camel Quarkus 3.10.0/4.4.5 missing extension?

2024-05-04 Thread James Netherton
If you're setting camel.metrics.enabled = true. Try removing it. Your
metrics should still get published without it.

On Sat, 4 May 2024 at 18:29, Mikael Andersson Wigander
 wrote:

> Yes but that’s the thing.
>
> I have them both.
>
> /M
>
> Den 4 maj 2024 kl 19:02, James Netherton <[jamesnether...@gmail.com
> ](mailto:Den 4 maj 2024 kl 19:02, James Netherton < skrev:
>
> > Hi,
> >
> > There is no extension for camel-micrometer-prometheus. You can use
> > camel-quarkus-micrometer and add an additional dependency for
> > quarkus-micrometer-registry-prometheus.
> >
> > 
> > io.quarkus
> > quarkus-micrometer-registry-prometheus
> > 
> >
> > Then all of your metrics will be available on the /q/metrics endpoint.
> > There's more information here:
> >
> >
> https://camel.apache.org/camel-quarkus/next/reference/extensions/micrometer.html#extensions-micrometer-usage
> >
> > https://quarkus.io/guides/telemetry-micrometer
> >
> > --
> > James
> >
> > On Sat, 4 May 2024 at 17:17, Mikael Andersson Wigander
> >  wrote:
> >
> >> Hi
> >>
> >> After upgrading my application to Quarkus 3.10.0 with camel 4.4.5 it
> won’t
> >> start because it complains about an extension not present in class path:
> >>
> >> camel-micrometer-prometheus.
> >>
> >> We use Metrics with Micrometer and Prometheus and don’t know what to do
> >> now.
> >>
> >> Can’t find any migration guide covers this, only name changes to tags.
> >>
> >> Please advise!
> >>
> >> /M


Camel Hystrix behaviour when circuit is open

2016-10-25 Thread James Netherton
Hi all,

I've been experimenting with camel-hystrix and wanted to check what the
expected (or correct) behaviour should be when the Hystrix circuit is open.

Looking at HystrixProcessorCommand.getFallback(), the fallback command is
only ever run if a prior exception was encountered. However, when the
circuit is in the open state, I'd expect a 'short-circuit' and the default
action would be to just invoke the fallback command (if configured).

I'm basing my assumptions on the Hystrix docs:

https://github.com/Netflix/Hystrix/wiki/How-it-Works

Is this a bug? Or am i misunderstanding how it should work in Camel?

--
James


WildFly-Camel-4.0.0 released

2016-04-04 Thread James Netherton
Dear Friends,

I’m happy to announce the release of wildfly-camel-4.0.0


WildFly-Camel 4.0.0 provides Camel-2.17 integration with WildFly-10.0.

This is a major upgrade release with a number of exiting features. Most
noteworthy, we now provide Camel integration for WildFly-Swarm and support
the creation of CXF WebService and Rest consumer endpoints through the
Camel API on the Undertow subsystem.

Additional components in the supported set are:

   - camel-braintree
   


Component upgrades include

   - Camel-2.17.0
   - WildFly-10.0.0.Final

In addition to that, we also resolved a number of other features, tasks and
bugfixes

.

For details please see the 4.0.0 Milestone

.

Enjoy

--
James