Hi DRy,
it can get quite complicated to handle all those jars by hand. I always
use maven to avoid copying jars around. You should try it if you do not
have another
build system. The camel examples are a good starting point. In any case
it is very important to make sure you don´t mix jars from different
versions.
I always check in my eclipse references that all jars that belong to a
bigger project like camel or spring have the same version number. Even
with maven it can easily happen
that you have for example different version of spring jars if you do not
check your configs.
Greetings
Christian
DRy schrieb:
Hi,
I tried to build a small (eclispe) project that shows what happens. To keep
this project as small as possible I do not include the used libs to that
project but use the lib path from a standard camel "installation" (2.1
Snapshot). What should I say ... everything works fine in that project ...
%-| ... (-> Murphys Law)
Maybe the strange behavior in my original project has something to do with
the used libs ... ? We used to use the libs from the ActiveMQ 5.3 release or
5.4 snapshot and replace all camel-*.jar with that ones from the camel 2.1
snapshot. We also add some needed jars (from camel 2.1 snapshot or other
needed projects). We do this, because we start with activemq and than add
some camel functionality.
DRy
