Hi Willem,
thanks for reply. Sorry, I was wrong with regards to the archetype.
I used camel-archetype-spring to build the (test) project. And I ran the
application with the 'mvn camel:run' command using this (predefined) entry
in the pom.xml:
<plugin>
<groupId>org.apache.camel</groupId>
<artifactId>camel-maven-plugin</artifactId>
<version>2.10.1</version>
</plugin>
Do you think using the camel-java archetype would make any difference if the
context component is found? It looks like Maven finds the dependency and
it's just not picked up during route construction.
If you think this could be a defect, not just a misconfiguration on my side,
I can try further investigation. Anyways, for now I am using the 'vm'
component. Does the same tricks...
Thanks,
Robert
Willem.Jiang wrote
> Hi,
>
> It looks like you are using camel spring Main to load the camel
> application context.
> I'm not sure why your mvn project have the dependency of
> camel-archetype-spring:jar:1.0-SNAPSHOT.
> --
> Willem Jiang
>
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Web: http://www.fusesource.com | http://www.redhat.com
> Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
> (English)
> http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese)
> Twitter: willemjiang
> Weibo: willemjiang
>
>
>
> On Thursday, October 18, 2012 at 8:54 PM, Robert wrote:
>
>> Hi,
>>
>> camel can't find the context component [1] in my application. My
>> application
>> is based on the Camel java maven archetype. I am declaring the
>> camel-context
>> maven dependency. What am I doing wrong?
>>
> [...]
--
View this message in context:
http://camel.465427.n5.nabble.com/Context-component-not-found-tp5721236p5721244.html
Sent from the Camel - Users mailing list archive at Nabble.com.
