You can also install the aries-blueprint-spring feature which should provide support for the spring namespaces.
Le mer. 10 oct. 2018 à 14:07, Jean-Baptiste Onofré <[email protected]> a écrit : > Hi > > It's because your are using spring-dm which is deprecated and works only > with spring up to 4. > > So you have to add the spring-legacy features repo and then you will have > the spring-dm feature. > > Regards > JB > Le 10 oct. 2018, à 15:04, "Miroslav Beranič" <[email protected]> > a écrit: >> >> Hi all, >> >> I've read some messages in this mailing list ( last I found was in August >> 2018 ), but I think, I have something different scenario. >> >> So, up until today ( when I was doing clean environment setup ) I was >> able to use define Spring Beans using XML ( as I am porting application, >> this is like top feature ), but now - out of the blue, I've started to get >> errors on deployment: >> >> 12:13:12.912 INFO [pool-33-thread-1] Generated blueprint for bundle >> framework.service/5.0.1.SNAPSHOT at >> /path/to/assemblies/apache-karaf/target/assembly/data/tmp/blueprint-spring-extender1831035315356717600.xml >> 12:13:12.917 INFO [pool-33-thread-1] Bundle >> framework.service/5.0.1.SNAPSHOT is waiting for namespace handlers [ >> http://www.springframework.org/schema/osgi] >> >> 12:13:12.895 INFO [features-3-thread-1] >> org.apache.aries.blueprint.spring.extender/0.4.0 >> 12:13:12.935 WARN [Blueprint Extender: 1] No URL is defined for schema >> http://www.springframework.org/schema/osgi. This schema will not be >> validated >> 12:13:12.969 ERROR [Blueprint Extender: 1] Unable to start blueprint >> container for bundle framework.service/5.0.1.SNAPSHOT >> org.osgi.service.blueprint.container.ComponentDefinitionException: >> Unsupported node namespace: >> at >> org.apache.aries.blueprint.parser.Parser.getNamespaceHandler(Parser.java:1386) >> ~[111:org.apache.aries.blueprint.core:1.9.0] >> at >> org.apache.aries.blueprint.parser.Parser.getNamespaceHandler(Parser.java:1374) >> ~[111:org.apache.aries.blueprint.core:1.9.0] >> at >> org.apache.aries.blueprint.parser.Parser.decorateCustomNode(Parser.java:1361) >> ~[111:org.apache.aries.blueprint.core:1.9.0] >> at >> org.apache.aries.blueprint.parser.Parser.handleCustomAttributes(Parser.java:1340) >> ~[111:org.apache.aries.blueprint.core:1.9.0] >> at >> org.apache.aries.blueprint.parser.Parser.loadComponents(Parser.java:403) >> ~[111:org.apache.aries.blueprint.core:1.9.0] >> at org.apache.aries.blueprint.parser.Parser.populate(Parser.java:331) >> ~[111:org.apache.aries.blueprint.core:1.9.0] >> at >> org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:351) >> [111:org.apache.aries.blueprint.core:1.9.0] >> at >> org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:278) >> [111:org.apache.aries.blueprint.core:1.9.0] >> at >> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) >> [?:?] >> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?] >> at >> org.apache.aries.blueprint.container.ExecutorServiceWrapper.run(ExecutorServiceWrapper.java:106) >> [111:org.apache.aries.blueprint.core:1.9.0] >> at >> org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:45) >> [111:org.apache.aries.blueprint.core:1.9.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:1149) >> [?:?] >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) >> [?:?] >> at java.lang.Thread.run(Thread.java:748) [?:?] >> >> So, has something changed about Spring ( Spring DM ) from Karaf's point? >> I went over GIT commits ( for Karaf 4.2.2, last few weeks ), but did not >> find anything regarding Spring. I am using Spring 4.3.x ( from Karaf >> features ). >> >> I have spring-beans.xml inside /META-INF/spring/ folder, and I used >> http://www.springframework.org/schema/osgi namespace to "import" >> osgi:reference -- and this all worked like a charm. >> >> Now I get this error and no way to find any solution. I "kind of" gave up >> ( as I read JB's comments - why not use ( only ) Blueprint ), so I gave it >> a try. But than I was starting getting even more strange errors, >> for example Blueprint failed to set property defined in parent class, or >> create instance that takes Map as input into class constructor - as I >> failed to find matching property descriptor or class constructor. >> >> Than I went back to original question ... what has changed, that >> http://www.springframework.org/schema/osgi has stopped working ( as far >> as I know, spring-dm is even older ( based on the mailing messages I've >> read ) ), >> so I've uses aries-blueprint-spring. >> >> What am I missing? >> >> Kind Regards, >> Miroslav >> >> -- ------------------------ Guillaume Nodet
