*) activate might be ambiguous. There is actually a ’start’ and a ‚activate on this very
thread‘. Think about @SessionScoped or @ConversationScoped. Not every new thread will
start a new Context. Multiple threads might re-use the very same one. Now you need a way
to explicitlely say which ’Session’ (or Map) you like to attach to
*) @ActivateRequestScope et al. Interesting idea but I fear it wont work out. Let’s stick
with the @SessionScoped example: _which_ Session should get created/attached for the very
But it’s a start! Thanks for getting the ball rolling.
Am 26.05.2016 um 12:42 schrieb John D. Ament
As mentioned during Tuesday's meeting, I'm looking for more feedback on PR #291 -
the context control APIs. I think the current version is pretty snazy, and thanks
especially to Martin for his input on it thus far. I'm looking for more input though,
especially from the OWB team (Mark Struberg??) on whether its realistic or not.
cdi-dev mailing list
Note that for all code provided on this list, the provider licenses the code under the
Apache License, Version 2 (http://www.apache.org/licenses/LICENSE-2.0.html
). For all other
ideas provided on this list, the provider waives all patent and other intellectual
property rights inherent in such information.