Thanks for all the effort on this guys.
Running from trunk, I now have three beans deployed and am using
<RouteBuilderRef ref="blah" />
in the camel context to get it all registered. I would probably move to
using annotations ultimately but see problem 2 below.
There are a couple of issues still which are not affecting me adversely at
the moment but should be recognised I guess:
1) I still have to define my RuoteBuilder bean after the <camelcontext>
element in activemq.xml, otherwise I get complaints about a broker already
existing. This is easily worked around by getting the xml right but I
presume somewhere there's a singleton not getting joined up properly?
2) This is potentially more serious (and is really a different issue).
With the upgrade to Spring 2.5.1 we have an incompatability with activemq
which still uses 2.0.6. Removing the 2.0.6 jar causes AMQ to fail - and
it's not just that package structure has changed, the servlet in question
really appears to be missing in 2.5.1. If we run with both the 2.0.6 and
2.5.1 jars present it appears to work initially but I can't imagine it's
really stable!
The error is:
java.lang.ClassNotFoundException:
org.springframework.web.servlet.DispatcherServlet
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at
org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:375)
-Dominic
--
View this message in context:
http://www.nabble.com/Configuring-a-Routebuilder-from-activemq.xml-file--tp14923839s22882p15017751.html
Sent from the Camel - Users mailing list archive at Nabble.com.
