I don't completely understand what you're trying to do. If you want a bean that
retains its value between page hits, why not simply identify whether
page hitsrefers to a conversation or the entire session than scope your SFSB accordingly? There's no need to weave it in and out of components to preserve it further.
In the above scenario when I come back to a method in SetListDragDropBean why wouldn't userInfo already be created and have the values from the previous invocation? Since userInfo is a Stateful bean I assumed it would.
It should if the bean is properly scoped. By default, an SFSB is bound to the conversation. What I guess is that in your case the conversation ends before the second invocation so the
previous invocationhappened in a different conversation. Check the boundaries of the conversation.
That's another thing that confuses me. I understand having to scope a component if JSF or another front end would have to access it, but for one EJB to access another that shouldn't be the case correct? I should just be able to inject it with @EJB or the SEAM @In / @Out and voila!
I did try the scoping anyway, but that did not work. I tried @Scope(ScopeType.SESSION)
Thanks for your input.