Spring bean scope as the class of the bean its autowired - spring

Question

I have spring bean called Executor I need this executor to be Injected in two classes one is session scoped and the other is singleton, So I use #Autowired annotation to inject it in both, it works very fine, But for the session bean the executor is only one for all sessions, and I understand this is how it should work.
How can I make the executor take the scope of the bean its injected into ? now all I could do is use two different classes for each.
And I cant realy understand the effect of setting the attribute scoped-proxy in
<context-component-scan /> to targetClass.
EDIT
Here is my try out for prototype scope:
suppose this is my session soped bean
#Component
#Scope("session")
public class WebExecutor(){
#Autowired
private ExecutorService executor;
#Async
public void startCalc(){
executor.start("now");
}
}
And this is my ExecutorService class
#Component
#Scope("prototype")
public class ExecutorService{
private int progress;
public void start(String when){
//do some stuff and increment the progress
}
//getter and setter for progress
}
I also have another component with default singleton scope which autowires the executor as well, so the executor can't be session scoped.
So now I have one class needed to have the scope of the bean it is being autowired in, So I tried the prototype scope.
How this should work in the Web versions is like this
You click a link that begins the execution which calls the method start of the WebExecutor
Then I get the progress from the ExecutorService using the WebParser and pass it back to the user to report the progress.
This was working great before prototype but the ExecutorService was one for all sessions,
so the I used prototype but now the progress is always 0, and when I debugged the Executor I found that it was incrementing but apprentally the WebExecutor could not see the increment.

Answer 1

U can use prototype scope. Then it will inject new instance of Executor when the Bean is constructed. So Executor starts its lifecycle when the bean is created.
scoped-proxy=target-class creates CGLIB wrapper around your bean. So other beans holds reference only to this wrapper, and the right bean with right scope is dynamically injected into this wrapper.
i.e. you don't hold very old expired request scoped bean in your session scoped bean, probably injected when the session was created . Instead new bean for current request is injected every time new request is created. This way you can access beans whith shorter life from beans with longer life i.e. your request scoped bean from your session scoped bean.