On 8/13/07, DominicTulley <[EMAIL PROTECTED]> wrote:
> Since setting up ActiveMQ is so easy, I've tried this with ActiveMQ 5's
> latest build as well now, sadly with the same result.
> There's just no sign of my class getting instantiated or invoked at any
> point.
>
> Any other ideas?

So to include Java routes in the broker in ActiveMQ 5 you'll need to
refer to your parent package name in the  Camel XML...

<camelContext>
  <package>com.acme.whatever</package>
   ...
</camelContext>

Then you'll need to make sure that the jar containing your routes is
in the lib directory.

Incidentally one minor change from Camel 1.0 to 1.1 is that its moved
from an attribute 'packages' to an element 'package' (which you can
include 0..N of them). Maybe thats the thing thats causing your issue?


> Normally my next step would be to step through the startup
> and observe the context loading - but that sounds like a lot of hard work
> and I'm not particularly familiar with any of the tools involved (never mind
> their source code).  I'm assuming that I've just done something daft, but if
> not I guess I'll have to do it the hard way..

FWIW if ever you wanna startup the code for an ActiveMQ broker in an
IDE or something you can use

java -jar run.jar

which basically just sets up the classpath to include all the jars in
the lib directory etc.
-- 
James
-------
http://macstrac.blogspot.com/

Reply via email to