camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject [HEADS UP] - Reducing spring dependency in Camel components
Date Mon, 08 Aug 2011 08:02:01 GMT


This is just a heads up that this weekend I migrated 11 components to
not depend on Spring JARs any more.

They were using a tiny piece of the Spring Framework, which is the
Resource loading. For example to load a .xsl file in the classpath or
file system. However this does not work out of the box in OSGi
blueprint, and we needed to add hooks into Spring Resource to make
that work. Likewise it doesnt really justify to bring in 8+ Spring
JARs to load a resource from the classpath. We already got this
functionality in camel-core.

Likewise we have end users who are not using Spring, so being able to
use Camel and these components without the need to bring in Spring
JARs is a good thing.

In this process I also moved 2 components from camel-spring to
camel-core, they are XSLT and Test.

That leaves us with 2 components that rely on Spring JARs
- camel-mail
- camel-jms

The former is only using Spring JARs for sending emails. We have a
patch in JIRA contributed by a community member, to send mails without
Spring JARs.

The latter is too depend on Spring JMS and it would only be possible
if we write a new lightweight JMS component, with less bells and
whistles, but simpler and just using the plain JMS API.

Previously we have refactored and ensured that camel-core can run with
JMX without Spring JARs as well. So Camel 2.9 is on a good way with
the goal of becoming less Spring JAR depend.

Claus Ibsen
Twitter: davsclaus, fusenews
Author of Camel in Action:

View raw message