Karl, Do you mean you're trying to maintain the state of the view scoped bean in the async request?
John On Tue, Jun 21, 2016 at 8:10 AM Karl Kildén <[email protected]> wrote: > So it is impossible then :-) > > The problem is that several slow things needs to be done from a JSF Bean. I > can't async it because the service the bean calls is @ViewAccessScoped and > stateful. > > I have a Bean that I want to start the thread from the Bean it is not a > problem but when I create a new thread this thread is also disconnected > from my Bean and it fails to look it up... > > Will take me ages to fix this project properly so desperate times calls for > strange hacks :-) > > On 21 June 2016 at 12:39, Thomas Andraschko <[email protected]> > wrote: > > > BeanProvider should work fine with any scope. > > Of course you can't receive a viewscoped bean from another > thread/request. > > > > 2016-06-21 11:52 GMT+02:00 Karl Kildén <[email protected]>: > > > > > I have a RequestScoped Bean that needs to split the workload basically > > and > > > the thread needs to lookup using the Bean that starts the thread so to > > > speak... > > > > > > On 21 June 2016 at 11:24, Karl Kildén <[email protected]> wrote: > > > > > > > Hello! > > > > > > > > If a project made a mistake in the architecture and needs to lookup > JSF > > > > scoped instances from the BeanProvider, is this possible in any way > > > > (however hacky?). > > > > > > > > The problem is that since the request thread is needed to lookup the > > > > instance it does not work from a thread. > > > > > > > > cheers > > > > > > > > > >
