Re: Camel on Karaf looking to resolve http://camel.apache.org/schema/spring/v${camel.schema.version}

Bug number for the discussed problem with camel-spring 2.18.x installed artefacts is https://issues.apache.org/jira/browse/CAMEL-11009 if anyone wants to follow it. On Mon, Mar 13, 2017 at 10:25 PM, Niels Bertram wrote: > Makes sense what you are saying. I just installed

CXF 3.1.8 in karaf 4.1.1 ?

As the tile specifies the CXF version is going to be updated in Karaf 4.1.1 ? I've stumbled upon the bug described in https://issues.apache.org/jira/browse/CXF-6740 which needs an updated version of cxf. Also embedded swagger ui (http://cxf.apache.org/docs/swagger2feature.html Automatic UI

Re: [Cellar] Load balancer setup

For what I understand it fails when trying to register the webconsole servlets for the second time (node1's were registered succesfully, node2 fails), the error is "alias already in use" . To solve that I thought I could try registering node2 webconsole servlets (/gogo, /features, etc) with

Jetty client

I'm curious if anybody is using the Jetty HTTP client from Karaf (v 4.0.8) successfully. I would like to move from using Apache to Jetty but I get a runtime NPE from Jetty. I tried it with both the 9.3.16 and 9.4.2 versions of the client with the exact same results. The following Jetty

JacksonJsonProvider not working with CXF Blueprint

Hi there, I tried to configure a simple CXF JAXRS service and use Jackson as the JSON provider. I did follow the CXF user documentation to configure the Jackson provider but it is ignored and default jettison does the work. I use the exact configuration without any issues in a plain Spring

Re: Camel on Karaf looking to resolve http://camel.apache.org/schema/spring/v${camel.schema.version}

Makes sense what you are saying. I just installed camel 2.18.2 components and by the looks of it, it is a packaging failure in camel-spring. 1. install camel feature on Karaf 4.0.8 (also tested 4.1.0): feature:repo-add camel 2.18.2 feature:install camel 2. install some route that uses blueprint

Re: Fwd: Gemini Blueprint on Karaf 4.0.8

Ohh! I saw that but i tought the shell-compat bundle was mandatory, works like a charm now. Thank you! -- View this message in context: http://karaf.922171.n3.nabble.com/Fwd-Gemini-Blueprint-on-Karaf-4-0-8-tp4049837p4049838.html Sent from the Karaf - User mailing list archive at Nabble.com.

Fwd: Gemini Blueprint on Karaf 4.0.8

As you can see, most bundles are refreshed because of shell.core being refreshed, which in turn is caused by the following: org.apache.karaf.shell.core/4.0.8 (Should be wired to: org.eclipse.gemini.blueprint.extender/2.0.0.RELEASE (through [org.apache.karaf.shell.console/4.0.8]

Re: Gemini Blueprint on Karaf 4.0.8

Hello! Here is the simulation: Adding features: gemini-blueprint/[2.0.0.RELEASE,2.0.0.RELEASE] Changes to perform: Region: root Bundles to install: mvn:org.apache.karaf.deployer/org.apache.karaf.deployer.spring/4.0.8

Re: Camel on Karaf looking to resolve http://camel.apache.org/schema/spring/v${camel.schema.version}

IIRC, camel blueprint translated the xml in the camel-spring namespace to be able to leverage jaxb, but clearly a property should have been replaced by the actual camel version. Can you explain exactly which bundles / features you installed (with versions) and the blueprint xml you use ?

Re: Gemini Blueprint on Karaf 4.0.8

Can you run the installation using: feature:install --simulate --verbose gemini-blueprint This should give more information about the exact reason why the bundles are refreshed. 2017-03-12 21:12 GMT+01:00 Ygor Castor : > Since Spring DM is long dead and it's quite a