Here it is:

feature:list -i | grep spring

camel-spring                            | 2.13.0                     | x        
 | camel-2.13.0                                                       |
spring-dm                               | 1.2.1                      | x        
 | karaf-2.2.11                                                       | Spring 
DM support
spring-dm                               | 1.2.1                      | x        
 | spring-3.0.1                                                       | Spring 
DM support
spring                                  | 3.2.4.RELEASE              | x        
 | spring-3.0.1                                                       | Spring 
3.2.x support
spring-jdbc                             | 3.2.4.RELEASE              | x        
 | spring-3.0.1                                                       | Spring 
3.2.x JDBC support
spring-jms                              | 3.2.4.RELEASE              | x        
 | spring-3.0.1                                                       | Spring 
3.2.x JMS support
spring-orm                              | 3.2.4.RELEASE              | x        
 | spring-3.0.1                                                       | Spring 
3.2.x ORM support
spring-tx                               | 3.2.4.RELEASE              | x        
 | spring-3.0.1                                                       | Spring 
3.2.x Transaction (TX) support
spring                                  | 4.0.2.RELEASE_1            | x        
 | spring-3.0.1                                                       | Spring 
4.0.x support


bundle:list -t 0 | grep spring
 76 | Active   |  30 | 1.2.1                        | spring-osgi-io
 77 | Active   |  30 | 1.2.1                        | spring-osgi-core
 78 | Active   |  30 | 1.2.1                        | spring-osgi-extender
 79 | Active   |  30 | 1.2.1                        | spring-osgi-annotation
 83 | Active   |  50 | 2.13.0                       | camel-spring
239 | Active   |  30 | 4.0.2.RELEASE_1              | Apache ServiceMix :: 
Bundles :: spring-core
240 | Active   |  30 | 4.0.2.RELEASE_1              | Apache ServiceMix :: 
Bundles :: spring-expression
241 | Active   |  30 | 4.0.2.RELEASE_1              | Apache ServiceMix :: 
Bundles :: spring-beans
242 | Active   |  30 | 4.0.2.RELEASE_1              | Apache ServiceMix :: 
Bundles :: spring-aop
243 | Active   |  30 | 4.0.2.RELEASE_1              | Apache ServiceMix :: 
Bundles :: spring-context
244 | Active   |  30 | 4.0.2.RELEASE_1              | Apache ServiceMix :: 
Bundles :: spring-context-support




-----Original Message-----
From: Jean-Baptiste Onofré [mailto:[email protected]]
Sent: Wednesday, November 25, 2015 12:55 PM
To: [email protected]
Subject: Re: Deploying Camel Route in Karaf

Did you install camel-spring, and spring feature ?

Can you give feature:list -i and bundle:list -t 0 (to see if the spring 
deployer is present) ?

Regards
JB

On 11/25/2015 06:49 PM, pavijit wrote:
> I am trying to deploy a Camel Route written in Spring DSL by copying
> the spring context file in $KARAF_HOME/deploy folder.
>
>
> All the pre-requisites are already deployed. But I get the following error:
>
> *org.springframework.beans.factory.parsing.BeanDefinitionParsingException:
> Configuration problem: Unable to locate Spring NamespaceHandler for
> XML schema namespace*
>
>
> This works fine when the spring context file is within a KAR file.
>
>
>
>
>
>
>
>
>
> --
> View this message in context:
> http://karaf.922171.n3.nabble.com/Deploying-Camel-Route-in-Karaf-tp404
> 3773.html Sent from the Karaf - User mailing list archive at
> Nabble.com.
>

--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
HealthEdge Software, Inc. is the owner of the information contained in this 
communication. The content of this communication is considered company 
confidential and may contain privileged information that is protected under 
various federal and state statutes. Disclosure of privileged information 
without the express written consent of an authorized legal agent of HealthEdge 
is strictly prohibited. Any unauthorized distribution or use of this 
communication, in part or whole, may constitute a criminal act. HealthEdge 
retains the right to pursue criminal and civil remedies in the event of any 
unauthorized disclosure.

Reply via email to