Thanks for this advice!
I want to try to "upgrade" my Camel plant to take advantage of this fact, but
I'm wondering about the version conditions set in the ServiceMix feature
manifests. They specify specific versions of Camel, e.g.
<feature name="camel-nmr" version="4.4.0-fuse-00-43" resolver="(obr)">
<feature version="2.7.1-fuse-00-43">camel</feature>
etc.
and so forth.
Is it possible for me to load Camel 2.8 and Velocity support therefor without
disrupting ServiceMix's machinery?
Can I simply install the appropriate newer bundles alongside their older
counterparts and alter the pom.xml of my route-bundle to force it to resolve
against the newer versions?
Thanks again!
---
A. Soroka
Online Library Environment
the University of Virginia Library
On Jul 29, 2011, at 2:45 AM, Claus Ibsen wrote:
> Hi
>
> Velocity loading template files from the classpath should work with
> Camel 2.8 in OSGi blueprint.
>
> Its listed in the release notes
> http://camel.apache.org/camel-280-release.html
>
> On Thu, Jul 28, 2011 at 11:44 PM, <[email protected]> wrote:
>> I'm trying to use Velocity in a Blueprint-deployed Camel (v
>> 2.7.1-fuse-00-43) route in SMX 4.4 (from Fusesource), without success. I'm
>> getting ResourceLoader problems like this (full stack traces, etc. available
>> if desired):
>>
>> After reaching:
>>
>> <to uri="velocity:velocity/sparql/getcontentmodels.vm"/>
>>
>> I see the thread properly load the resource into the content cache and then
>> start the Velocity engine with "properties{ class.resource.loader.class=
>> org.apache.camel.component.velocity.CamelVelocityClasspathResourceLoader,
>> resource.loader=file, class, class.resource.loader.description=Camel
>> Velocity Classpath Resource Loader," etc.
>>
>> only to fail with
>>
>> ...
>> org.apache.velocity.exception.VelocityException: Problem instantiating the
>> template loader:
>> org.apache.camel.component.velocity.CamelVelocityClasspathResourceLoader.
>> ...
>> Caused by: java.lang.ClassNotFoundException:
>> org.apache.camel.component.velocity.CamelVelocityClasspathResourceLoader not
>> found by org.apache.servicemix.bundles.velocity
>> ...
>>
>> I've noticed this:
>>
>> http://camel.apache.org/camel-29-jmx-and-reducing-spring-dependency.html
>>
>> which leads me to think that I may be trying do something that can't
>> currently be done, because the Camel Velocity component is still tied to
>> Spring resource loading. Is it best for me to migrate back to Spring XML and
>> wait for Camel+Blueprint to advance a bit, or is there some way around this,
>> or am I just being thick?
>>
>> Also, thanks very much to the whole ServiceMix community for a fantastic
>> product! This is the first time (after several months exploring and
>> developing workflows with ServiceMix that I suspect I may have run into an
>> actual limitation in the product, which really impresses me enormously.
>>
>> ---
>> A. Soroka
>> Online Library Environment
>> the University of Virginia Library
>>
>>
>>
>>
>>
>
>
>
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email: [email protected]
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/
