Major Description
Velocity templates can contain a macro which includes another template. And that template is loaded from the classpath.
However with OSGi its not so easy to have this working as its VelocityEngine that loads that resource. And its classloader do not have imports to any end users packages where his/hers .vm template files reside.
So if possible maybe the SMX bundle of Velocity can have a dynamic import. So we have a chance of loading those template files using #macro
For example you may have a .vm file in org/apache/camel/itest/osgi/velocity/example.vm which includes another .vm file from the classpath.
#parse("org/apache/camel/itest/osgi/velocity/header.vm")
<hello>${headers.cheese}</hello>
When #parse is executed its VelocityEngine that takes over and load that resource. And this its a different classloader tree we end up taking.