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 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 and camel blueprint schema
>
> Looking at http://search.maven.org/remotecontent?filepath=org/
> apache/camel/camel-spring/2.18.2/camel-spring-2.18.2.jar
>
> I can see that file /META-INF/spring.schemas shows following:
>
> #
> # Licensed to the Apache Software Foundation (ASF) under one or more
> # contributor license agreements. See the NOTICE file distributed with
> ...
> http\://camel.apache.org/schema/spring=camel-spring.xsd
> http\://camel.apache.org/schema/spring/v${camel.schema.
> version}=camel-spring-v${camel.schema.version}.xsd
>
>
> Its actually broken in all 2.18.x releases but ok in 2.17.x and 2.16.x
>
> I'll file a bug with Camel. Thanks for your thoughts.
>
>
> On Mon, Mar 13, 2017 at 7:43 PM, Guillaume Nodet
> wrote:
>
>> 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 ?
>>
>> 2017-03-12 14:14 GMT+01:00 Niels Bertram :
>>
>>> Hi there,
>>>
>>> I am trying to implement a very basic CXF / Camel REST service. And
>>> despite best efforts I am getting below stacktrace when installing by
>>> bundle.
>>>
>>> Disturbing part is, I did not ask for spring, I want a plain blueprint
>>> instance.
>>>
>>> Anyone has seen this before?
>>>
>>>
>>> 2017-03-12 23:00:39,527 | WARN | pool-32-thread-2 |
>>> NamespaceHandlerRegistryImpl | 12 - org.apache.aries.blueprint.core
>>> - 1.7.1 | Error registering NamespaceHandler
>>> java.lang.IllegalArgumentException: Illegal character in path at index
>>> 40: http://camel.apache.org/schema/spring/v${camel.schema.version}
>>> at java.net.URI.create(URI.java:852) [?:?]
>>> at org.apache.aries.blueprint.namespace.NamespaceHandlerRegistr
>>> yImpl.getNamespaces(NamespaceHandlerRegistryImpl.java:203)
>>> [12:org.apache.aries.blueprint.core:1.7.1]
>>> at org.apache.aries.blueprint.namespace.NamespaceHandlerRegistr
>>> yImpl.registerHandler(NamespaceHandlerRegistryImpl.java:157)
>>> [12:org.apache.aries.blueprint.core:1.7.1]
>>> at org.apache.aries.blueprint.namespace.NamespaceHandlerRegistr
>>> yImpl.addingService(NamespaceHandlerRegistryImpl.java:121)
>>> [12:org.apache.aries.blueprint.core:1.7.1]
>>> at
>>> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:941)
>>> [?:?]
>>> at
>>> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:870)
>>> [?:?]
>>> at
>>> org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
>>> [?:?]
>>> at
>>> org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229)
>>> [?:?]
>>> at
>>> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:901)
>>> [?:?]
>>> at org.apache.felix.framework.EventDispatcher.invokeServiceList
>>> enerCallback(EventDispatcher.java:990) [?:?]
>>> at
>>> org.apache.felix.framework.EventDispatcher.fireEventImmediately(EventDispatcher.java:838)
>>> [?:?]
>>> at
>>> org.apache.felix.framework.EventDispatcher.fireServiceEvent(EventDispatcher.java:545)
>>> [?:?]
>>> at
>>> org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4557)
>>> [?:?]
>>> at org.apache.felix.framework.Felix.registerService(Felix.java:3549)
>>> [?:?]
>>> at
>>> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:348)
>>> [?:?]
>>> at
>>> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:355)
>>> [?:?]
>>> at
>>> org.apache.aries.blueprint.spring.SpringExtension.start(SpringExtension.java:78)
>>> [202:org.apache.aries.blueprint.spring:0.2.0]
>>> at
>>> org.apache.felix.utils.extender.AbstractExtender$1.run(AbstractExtender.java:265)
>>> [202:org.apache.aries.blueprint.spring:0.2.0]
>>> at
>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>>> [?:?]
>>> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>>> [?:?]
>>> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFu
>>> tureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:?]
>>> a
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 Activation section) works in osgi only on 3.1.8 and up (I'm not completely sure if I have understood how it will work but that's what is in the documentation)... Best Regards, -- View this message in context: http://karaf.922171.n3.nabble.com/CXF-3-1-8-in-karaf-4-1-1-tp4049844.html Sent from the Karaf - User mailing list archive at Nabble.com.
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 different alias, but then, reading ServerModel
code, I realized that if I do that it will also fail throwing the error:
throw new ServletException("servlet already registered with a different
alias");
I don't know what else to try, any idea?
Thanks
--
View this message in context:
http://karaf.922171.n3.nabble.com/Cellar-Load-balancer-setup-tp4049717p4049843.html
Sent from the Karaf - User mailing list archive at Nabble.com.
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 bundles were required. Jetty-client-9.3.16v... Jetty-http-9.3.16v... Jetty-io-9.3.16v... Jetty-util-9.3.16v... Scott Leschke
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 context (slightly adapted for different xml names obviously). Adding the skip.default.json.provider.registration=true property to the does seem to do little difference. I created a quick start demo of the issue: https://github.com/bertramn/cxf-jackson-osgi-blueprint-issue I also noticed that when I create and configure a and try to reference this on the the blueprint will fail with a can't resolve id error. Did anyone came across those issues? Cheers, Niels
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 and camel blueprint schema
Looking at
http://search.maven.org/remotecontent?filepath=org/apache/camel/camel-spring/2.18.2/camel-spring-2.18.2.jar
I can see that file /META-INF/spring.schemas shows following:
#
# Licensed to the Apache Software Foundation (ASF) under one or more
# contributor license agreements. See the NOTICE file distributed with
...
http\://camel.apache.org/schema/spring=camel-spring.xsd
http\://
camel.apache.org/schema/spring/v${camel.schema.version}=camel-spring-v${camel.schema.version}.xsd
Its actually broken in all 2.18.x releases but ok in 2.17.x and 2.16.x
I'll file a bug with Camel. Thanks for your thoughts.
On Mon, Mar 13, 2017 at 7:43 PM, Guillaume Nodet wrote:
> 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 ?
>
> 2017-03-12 14:14 GMT+01:00 Niels Bertram :
>
>> Hi there,
>>
>> I am trying to implement a very basic CXF / Camel REST service. And
>> despite best efforts I am getting below stacktrace when installing by
>> bundle.
>>
>> Disturbing part is, I did not ask for spring, I want a plain blueprint
>> instance.
>>
>> Anyone has seen this before?
>>
>>
>> 2017-03-12 23:00:39,527 | WARN | pool-32-thread-2 |
>> NamespaceHandlerRegistryImpl | 12 - org.apache.aries.blueprint.core
>> - 1.7.1 | Error registering NamespaceHandler
>> java.lang.IllegalArgumentException: Illegal character in path at index
>> 40: http://camel.apache.org/schema/spring/v${camel.schema.version}
>> at java.net.URI.create(URI.java:852) [?:?]
>> at org.apache.aries.blueprint.namespace.NamespaceHandlerRegistr
>> yImpl.getNamespaces(NamespaceHandlerRegistryImpl.java:203)
>> [12:org.apache.aries.blueprint.core:1.7.1]
>> at org.apache.aries.blueprint.namespace.NamespaceHandlerRegistr
>> yImpl.registerHandler(NamespaceHandlerRegistryImpl.java:157)
>> [12:org.apache.aries.blueprint.core:1.7.1]
>> at org.apache.aries.blueprint.namespace.NamespaceHandlerRegistr
>> yImpl.addingService(NamespaceHandlerRegistryImpl.java:121)
>> [12:org.apache.aries.blueprint.core:1.7.1]
>> at
>> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:941)
>> [?:?]
>> at
>> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:870)
>> [?:?]
>> at
>> org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
>> [?:?]
>> at
>> org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229)
>> [?:?]
>> at
>> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:901)
>> [?:?]
>> at org.apache.felix.framework.EventDispatcher.invokeServiceList
>> enerCallback(EventDispatcher.java:990) [?:?]
>> at
>> org.apache.felix.framework.EventDispatcher.fireEventImmediately(EventDispatcher.java:838)
>> [?:?]
>> at
>> org.apache.felix.framework.EventDispatcher.fireServiceEvent(EventDispatcher.java:545)
>> [?:?]
>> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4557)
>> [?:?]
>> at org.apache.felix.framework.Felix.registerService(Felix.java:3549)
>> [?:?]
>> at
>> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:348)
>> [?:?]
>> at
>> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:355)
>> [?:?]
>> at
>> org.apache.aries.blueprint.spring.SpringExtension.start(SpringExtension.java:78)
>> [202:org.apache.aries.blueprint.spring:0.2.0]
>> at
>> org.apache.felix.utils.extender.AbstractExtender$1.run(AbstractExtender.java:265)
>> [202:org.apache.aries.blueprint.spring:0.2.0]
>> at
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>> [?:?]
>> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
>> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFu
>> tureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:?]
>> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFu
>> tureTask.run(ScheduledThreadPoolExecutor.java:293) [?:?]
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>> [?:?]
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>> [?:?]
>> at java.lang.Thread.run(Thread.java:745) [?:?]
>> Caused by: java.net.URISyntaxException: Illegal character in path at
>> index 40: ht
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] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.osgi.service.blueprint)( version>=1.0.0)(!(version>=2.0.0)))")) I suppose you have aries blueprint already installed, but the feature installer has decided that the shell.console bundle should be wired to the api from gemini instead. The shell.console bundle is not mandatory, but installed through the shell-compat feature which aims to support commands written for older versions of karaf. 2017-03-13 12:33 GMT+01:00 : > 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 > mvn:org.apache.servicemix.bundles/org.apache.servicemix.bund > les.aopalliance/1.0_6 > mvn:org.apache.servicemix.bundles/org.apache.servicemix.bund > les.spring-aop/4.2.9.RELEASE_1 > mvn:org.apache.servicemix.bundles/org.apache.servicemix.bund > les.spring-beans/4.2.9.RELEASE_1 > mvn:org.apache.servicemix.bundles/org.apache.servicemix.bund > les.spring-context/4.2.9.RELEASE_1 > mvn:org.apache.servicemix.bundles/org.apache.servicemix.bund > les.spring-context-support/4.2.9.RELEASE_1 > mvn:org.apache.servicemix.bundles/org.apache.servicemix.bund > les.spring-core/4.2.9.RELEASE_1 > mvn:org.apache.servicemix.bundles/org.apache.servicemix.bund > les.spring-expression/4.2.9.RELEASE_1 > mvn:org.eclipse.gemini.blueprint/gemini-blueprint-core/2.0.0.RELEASE > mvn:org.eclipse.gemini.blueprint/gemini-blueprint-extender/ > 2.0.0.RELEASE > mvn:org.eclipse.gemini.blueprint/gemini-blueprint-io/2.0.0.RELEASE > Bundles to refresh: > org.apache.aries.blueprint.cm/1.0.9 (Should be wired to: > org.eclipse.gemini.blueprint.extender/2.0.0.RELEASE (through [ > org.apache.aries.blueprint.cm/1.0.9] osgi.wiring.package; > filter:="(&(osgi.wiring.package=org.osgi.service. > blueprint)(version>=1.0.0)(!(version>=2.0.0)))")) > org.apache.karaf.bundle.blueprintstate/4.0.8 (Wired to > org.apache.karaf.bundle.core/4.0.8 which is being refreshed) > org.apache.karaf.bundle.core/4.0.8 (Wired to > org.apache.karaf.shell.core/4.0.8 which is being refreshed) > org.apache.karaf.config.core/4.0.8 (Wired to > org.apache.karaf.shell.core/4.0.8 which is being refreshed) > org.apache.karaf.deployer.kar/4.0.8 (Wired to > org.apache.karaf.kar.core/4.0.8 which is being refreshed) > org.apache.karaf.diagnostic.core/4.0.8 (Wired to > org.apache.karaf.shell.core/4.0.8 which is being refreshed) > org.apache.karaf.features.command/4.0.8 (Wired to > org.apache.karaf.shell.core/4.0.8 which is being refreshed) > org.apache.karaf.instance.core/4.0.8 (Wired to > org.apache.karaf.features.command/4.0.8 which is being refreshed) > org.apache.karaf.jaas.blueprint.config/4.0.8 (Should be wired to: > org.eclipse.gemini.blueprint.extender/2.0.0.RELEASE (through > [org.apache.karaf.jaas.blueprint.config/4.0.8] osgi.wiring.package; > filter:="(&(osgi.wiring.package > =org.osgi.service.blueprint)(version>=1.0.0)(!(version>=2.0.0)))")) > org.apache.karaf.jaas.command/4.0.8 (Wired to > org.apache.karaf.shell.core/4.0.8 which is being refreshed) > org.apache.karaf.kar.core/4.0.8 (Wired to > org.apache.karaf.features.command/4.0.8 which is being refreshed) > org.apache.karaf.log.core/4.0.8 (Wired to > org.apache.karaf.shell.core/4.0.8 which is being refreshed) > org.apache.karaf.package.core/4.0.8 (Wired to > org.apache.karaf.shell.core/4.0.8 which is being refreshed) > org.apache.karaf.service.core/4.0.8 (Wired to > org.apache.karaf.shell.core/4.0.8 which is being refreshed) > org.apache.karaf.shell.commands/4.0.8 (Wired to > org.apache.karaf.shell.core/4.0.8 which is being refreshed) > org.apache.karaf.shell.console/4.0.8 (Wired to > org.apache.karaf.shell.core/4.0.8 which is being refreshed) > 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] osgi.wiring.package; > filter:="(&(osgi.wiring.package=org.osgi.service.b > lueprint)(version>=1.0.0)(!(version>=2.0.0)))")) > org.apache.karaf.shell.ssh/4.0.8 (Wired to > org.apache.karaf.shell.core/4.0.8 which is being refreshed) > org.apache.karaf.system.core/4.0.8 (Wired to > org.apache.karaf.shell.core/4.0.8 which is being refreshed) > > > > > 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 l
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 mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.aopalliance/1.0_6 mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-aop/4.2.9.RELEASE_1 mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-beans/4.2.9.RELEASE_1 mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-context/4.2.9.RELEASE_1 mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-context-support/4.2.9.RELEASE_1 mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-core/4.2.9.RELEASE_1 mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-expression/4.2.9.RELEASE_1 mvn:org.eclipse.gemini.blueprint/gemini-blueprint-core/2.0.0.RELEASE mvn:org.eclipse.gemini.blueprint/gemini-blueprint-extender/2.0.0.RELEASE mvn:org.eclipse.gemini.blueprint/gemini-blueprint-io/2.0.0.RELEASE Bundles to refresh: org.apache.aries.blueprint.cm/1.0.9 (Should be wired to: org.eclipse.gemini.blueprint.extender/2.0.0.RELEASE (through [org.apache.aries.blueprint.cm/1.0.9] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.osgi.service. blueprint)(version>=1.0.0)(!(version>=2.0.0)))")) org.apache.karaf.bundle.blueprintstate/4.0.8 (Wired to org.apache.karaf.bundle.core/4.0.8 which is being refreshed) org.apache.karaf.bundle.core/4.0.8 (Wired to org.apache.karaf.shell.core/4.0.8 which is being refreshed) org.apache.karaf.config.core/4.0.8 (Wired to org.apache.karaf.shell.core/4.0.8 which is being refreshed) org.apache.karaf.deployer.kar/4.0.8 (Wired to org.apache.karaf.kar.core/4.0.8 which is being refreshed) org.apache.karaf.diagnostic.core/4.0.8 (Wired to org.apache.karaf.shell.core/4.0.8 which is being refreshed) org.apache.karaf.features.command/4.0.8 (Wired to org.apache.karaf.shell.core/4.0.8 which is being refreshed) org.apache.karaf.instance.core/4.0.8 (Wired to org.apache.karaf.features.command/4.0.8 which is being refreshed) org.apache.karaf.jaas.blueprint.config/4.0.8 (Should be wired to: org.eclipse.gemini.blueprint.extender/2.0.0.RELEASE (through [org.apache.karaf.jaas.blueprint.config/4.0.8] osgi.wiring.package; filter:="(&(osgi.wiring.package =org.osgi.service.blueprint)(version>=1.0.0)(!(version>=2.0.0)))")) org.apache.karaf.jaas.command/4.0.8 (Wired to org.apache.karaf.shell.core/4.0.8 which is being refreshed) org.apache.karaf.kar.core/4.0.8 (Wired to org.apache.karaf.features.command/4.0.8 which is being refreshed) org.apache.karaf.log.core/4.0.8 (Wired to org.apache.karaf.shell.core/4.0.8 which is being refreshed) org.apache.karaf.package.core/4.0.8 (Wired to org.apache.karaf.shell.core/4.0.8 which is being refreshed) org.apache.karaf.service.core/4.0.8 (Wired to org.apache.karaf.shell.core/4.0.8 which is being refreshed) org.apache.karaf.shell.commands/4.0.8 (Wired to org.apache.karaf.shell.core/4.0.8 which is being refreshed) org.apache.karaf.shell.console/4.0.8 (Wired to org.apache.karaf.shell.core/4.0.8 which is being refreshed) 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] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.osgi.service.b lueprint)(version>=1.0.0)(!(version>=2.0.0)))")) org.apache.karaf.shell.ssh/4.0.8 (Wired to org.apache.karaf.shell.core/4.0.8 which is being refreshed) org.apache.karaf.system.core/4.0.8 (Wired to org.apache.karaf.shell.core/4.0.8 which is being refreshed) -- View this message in context: http://karaf.922171.n3.nabble.com/Gemini-Blueprint-on-Karaf-4-0-8-tp4049831p4049835.html Sent from the Karaf - User mailing list archive at Nabble.com.
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 ?
2017-03-12 14:14 GMT+01:00 Niels Bertram :
> Hi there,
>
> I am trying to implement a very basic CXF / Camel REST service. And
> despite best efforts I am getting below stacktrace when installing by
> bundle.
>
> Disturbing part is, I did not ask for spring, I want a plain blueprint
> instance.
>
> Anyone has seen this before?
>
>
> 2017-03-12 23:00:39,527 | WARN | pool-32-thread-2 |
> NamespaceHandlerRegistryImpl | 12 - org.apache.aries.blueprint.core -
> 1.7.1 | Error registering NamespaceHandler
> java.lang.IllegalArgumentException: Illegal character in path at index
> 40: http://camel.apache.org/schema/spring/v${camel.schema.version}
> at java.net.URI.create(URI.java:852) [?:?]
> at org.apache.aries.blueprint.namespace.
> NamespaceHandlerRegistryImpl.getNamespaces(NamespaceHandlerRegistryImpl.java:203)
> [12:org.apache.aries.blueprint.core:1.7.1]
> at org.apache.aries.blueprint.namespace.
> NamespaceHandlerRegistryImpl.registerHandler(NamespaceHandlerRegistryImpl.java:157)
> [12:org.apache.aries.blueprint.core:1.7.1]
> at org.apache.aries.blueprint.namespace.
> NamespaceHandlerRegistryImpl.addingService(NamespaceHandlerRegistryImpl.java:121)
> [12:org.apache.aries.blueprint.core:1.7.1]
> at
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:941)
> [?:?]
> at
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:870)
> [?:?]
> at
> org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
> [?:?]
> at
> org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229)
> [?:?]
> at org.osgi.util.tracker.ServiceTracker$Tracked.
> serviceChanged(ServiceTracker.java:901) [?:?]
> at org.apache.felix.framework.EventDispatcher.
> invokeServiceListenerCallback(EventDispatcher.java:990) [?:?]
> at org.apache.felix.framework.EventDispatcher.
> fireEventImmediately(EventDispatcher.java:838) [?:?]
> at
> org.apache.felix.framework.EventDispatcher.fireServiceEvent(EventDispatcher.java:545)
> [?:?]
> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4557)
> [?:?]
> at org.apache.felix.framework.Felix.registerService(Felix.java:3549)
> [?:?]
> at
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:348)
> [?:?]
> at
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:355)
> [?:?]
> at
> org.apache.aries.blueprint.spring.SpringExtension.start(SpringExtension.java:78)
> [202:org.apache.aries.blueprint.spring:0.2.0]
> at
> org.apache.felix.utils.extender.AbstractExtender$1.run(AbstractExtender.java:265)
> [202:org.apache.aries.blueprint.spring:0.2.0]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [?:?]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> at java.util.concurrent.ScheduledThreadPoolExecutor$
> ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:?]
> at java.util.concurrent.ScheduledThreadPoolExecutor$
> ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:?]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [?:?]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [?:?]
> at java.lang.Thread.run(Thread.java:745) [?:?]
> Caused by: java.net.URISyntaxException: Illegal character in path at index
> 40: http://camel.apache.org/schema/spring/v${camel.schema.version}
> at java.net.URI$Parser.fail(URI.java:2848) ~[?:?]
> at java.net.URI$Parser.checkChars(URI.java:3021) ~[?:?]
> at java.net.URI$Parser.parseHierarchical(URI.java:3105) ~[?:?]
> at java.net.URI$Parser.parse(URI.java:3053) ~[?:?]
> at java.net.URI.(URI.java:588) ~[?:?]
> at java.net.URI.create(URI.java:850) ~[?:?]
> ... 24 more
>
--
Guillaume Nodet
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 buggy way to wire spring on > a OSGi context i've decided to give Gemini a chance, since it's actively > developed, first of all i've updated the feature to: > > http://pastebin.com/4sAzyxGg > > And it seems to work ok, but with one problem, when i install any feature > the whole container goes awry, refreshing even core bundles, here is the > log: > > http://pastebin.com/t8h2FTpt > > I've had the same problem before with Fragment bundles, i've created a > Liquibase Extension fragment, and everytime that fragment got refreshed the > whole container became a mess. > > Right now, to "solve" the problem i'm using a feature:install/uninstall -r > , which disables feature bundles auto-refresh, and refreshing manualy using > bundle:refresh, doing that there is no problem, and i'm able to use gemini > and the fragments. > > I'm not sure this is a normal behavior, can anyone confirm? > -- Guillaume Nodet
