Hi, Camel JMS component is tightly coupled with Spring JmsTemplate, which is rather bad news. Given that Spring with its classloader hack tries to resolve the namspace handler and fails miserably. It is just not meant for OSGi setup. Even if we try to move to Apache Aries Blueprint we still cannot move away from Spring because of the decisions being taken to tightly couple Spring framework.
Spring is not a mature framework for OSGi but its good for other applications. Is there any effort to de-couple Camel API's from Spring dependencies? Best Regards, Madhav -- When I tell the truth, it is not for the sake of convincing those who do not know it, but for the sake of defending those that do
