Versions Compared

Old Version 1

changes.mady.by.user Claus Ibsen

Saved on

compared with

New Version Current

changes.mady.by.user Christian Schneider

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

Some Camel Components such as Velocity, Freemarker, XSTL XSLT uses Spring Resource API to load resources over the classpath etc. This does not work in OSGi blueprint, etc. Instead we should rely on the Pluggable Class Resolvers provided by Camel that works with OSGi, JBoss and other containers.

...

The Mail and JMS component currently depend on Spring JARs. There is a work in progress patch for the Mail component to be able to run without Spring. The JMS component is however heavily dependent on Spring, as it uses spring-jms. We may in the future consider writing a new light weight JMS component that has less features, but can work without Spring. However this is not the goal for Camel 2.9. If we do our own jms abstraction which might be a good idea then we should put it in a apache commons project as it would also help other projects like cxf.