By default spring creates all beans as singletons. So you should
normally not create the ProcessorProducer class yourself but rather let
spring inject into the class that needs it.
Is there a special reason why the singleton case is bad for you?
Greetings
Christian
Am 05.08.2010 11:39, schrieb unixployd:
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?
--
----
http://www.liquid-reality.de
