[cdi-dev] Looking for Feedback on PR #291

John D. Ament john.d.ament at gmail.com
Tue May 31 08:47:51 EDT 2016


Mark,

*) We can enhance the docs.  It should be clear, when looking at the
javadocs, that its intended for the current thread and cannot be started
more than once.

John

On Tue, May 31, 2016 at 2:51 AM Mark Struberg <struberg at yahoo.de> wrote:

> Quick feedback:
>
> *) 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 thread?
>
> But it’s a start! Thanks for getting the ball rolling.
>
> LieGrue,
> strub
>
>
> > Am 26.05.2016 um 12:42 schrieb John D. Ament <john.d.ament at gmail.com>:
> >
> > All,
> >
> > 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.
> >
> > https://github.com/cdi-spec/cdi/pull/291
> >
> >
> > John
> > _______________________________________________
> > cdi-dev mailing list
> > cdi-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/cdi-dev
> >
> > 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.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160531/699be7d6/attachment.html 


More information about the cdi-dev mailing list