You can maybe have a depens-on attribute on the <bean> to the <camelContext>. This will tell Spring to create the bean after CamelContext has been started.
On Thu, Aug 5, 2010 at 11:39 AM, unixployd <[email protected]> wrote: > > The problem here is connected with Spring itself. I seems that spring creates > one singleton of ProcessorProducer in his context, but when I try to create > new instance in the route Spring doesn't handle this and instance is > creating without any injection. > Why I think so? When I wrote this class as singleton returning only one > instance of it every time everything is ok, because when spring correctly > injects everything and creates it in his context I can work with Producer > successfully. > Can it be? > -- > View this message in context: > http://camel.465427.n5.nabble.com/Spring-does-not-handle-Produce-tp2264524p2265086.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
