Camel Velocity component should not require you to import
CamelVelocityClasspathResourceLoader
----------------------------------------------------------------------------------------------
Key: CAMEL-4587
URL: https://issues.apache.org/jira/browse/CAMEL-4587
Project: Camel
Issue Type: Improvement
Components: camel-velocity
Affects Versions: 2.8.2, 2.8.1, 2.8.0
Reporter: Willem Jiang
Assignee: Willem Jiang
Fix For: 2.8.3, 2.9.0
While trying out a Camel demo that uses velocity, I discovered a change of
behaviour in the velocity component in Camel 2.8.0. I am using velocity in a
Camel route defined in Spring XML. When I deploy the route into the OSGi
container, velocity complains that it cannot find the
CamelVelocityClasspathResourceLoader class. I can fix this by importing the
class into my bundle.
I just checked the code of camel-velocity, as we introduced the
CamelVelocityClasspathResourceLoader which should be loaded from the TCCL to
load the resource by using camel context resolver.
That could explain why you need to add the import package of
"org.apache.camel.component.velocity".
We can fix it by resetting a custom TCCL which knows how to load the
CamelVelocityClasspathResourceLoader when calling the
velocityEngine.init(properties).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
