I've seen lots of problems when using spring-dm, some of them do not have any clean solution *at all*, especially when using custom namespace handlers such as camel. That's why I've been advocating for using blueprint instead, which works way better.
Camel support for blueprint is much better since 2.6 and 2.7 will bring another set of improvements, so if that's an option, i'd switch to blueprint. Else, well, you can always try to put some Thread.sleep at some very fined tuned location in order to make sure the camel namespace handler is ready and that all camel components are available. On Wed, Mar 9, 2011 at 15:51, Michael Prieß <mailingliste...@googlemail.com> wrote: > Hi all, > > i like to deploy camel-routes and features inside the deploy directory. > > A deployment look like the following: > > - a feature.xml which contain bundles like Apache Camel, Spring with a start > level definition. > - and many xml camel-routes which contain configurations for my components. > > Now i have the problem that my camel-routes have the same start level like > the features. > > Have anyone a good idea how to resolve the problem? > > Regards, > > Michael Priess > > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
