I'm glad to hear it works for some things - at least that suggests it's just something I'm doing wrong!
I've been debugging further and found that my jar is being picked up by the classloader (along with all the others). When the ResolverUtil iterates over the URL enumeration, the enumeration skips my jar (and various others) so I presume there's some sort of filtering going on there - but I haven't worked out what yet. The packages vs <package> thing is fine - the correct package name is being passed into the code. Are there any subtle requirements on the jar used (something in the manifest for instance?) which might be causing it to be filtered out? I'll keep bashing away at it for now - but I'm running out of ideas! Thanks, -Dominic James.Strachan wrote: > > > It should work! :) > > So I just did a test to check this really does work. Here's what I did. > > * copied the camel-example-spring.jar into the activemq/lib directory > (in the binary distro of 5.x). > * editied the conf/activemq.xml to look like this... > > <camelContext id="camel" > xmlns="http://activemq.apache.org/camel/schema/spring";> > <package>org.apache.camel.example</package> > </camelContext> > > Then I started ActiveMQ and it just worked (I saw the queue > "test.MyQueue" in the web console - then when I sent a message via the > web console the camel processing log message appeared in the console). > > I wonder - if the change you hit is the change from the "packages" > attribute in camel 1.0 to the 0-many <package> elements in Camel 1.1? > > I've just added a little warning to the 1.1 download page in case thats > it... > http://cwiki.apache.org/CAMEL/camel-110-release.html > > also I've patched the activemq.xml in trunk with comments to show the > new syntax etc. > > -- > James > ------- > http://macstrac.blogspot.com/ > > -- View this message in context: http://www.nabble.com/CAMEL-and-ActiveMQ5---Integration-tf4140859s22882.html#a12143844 Sent from the Camel - Users mailing list archive at Nabble.com.
