[cdi-dev] CDI-30 F2F meeting summary
John D. Ament
john.d.ament at gmail.com
Fri Jun 24 17:35:25 EDT 2016
One of the follow up items was to split CDI-30 into multiple tickets, to
keep focus on just the portions we're working on.
I've created the following follow up tickets:
While I also realize that https://issues.jboss.org/browse/CDI-452 is
critical for this discussion, and may be somewhat related to both of these
My goal is to tackle all of these for EDR2, and will hopefully in coming
On Fri, Jun 24, 2016 at 4:08 PM Antoine Sabot-Durand <
antoine at sabot-durand.net> wrote:
> Hi all,
> Just to sum up the meeting we had today about CDI-30 and John's PR.
> If I forgot something, the attendee (John, Matej and Werner) can of course
> correct or add content.
> While we agreed that this feature is very important, it's obvious that
> each of us has a different way of seeing it.
> To try to get out of the current dead end, the idea was to split the
> problem in 2 goal :
> 1. Provide low level SPI for framework and spec developers to reuse cdi
> built in scope. Roughly it consist of giving the possibility to activate
> and deactivate context programmatically. If it's possible this should be
> done without adding new interface to keep the SPI as simple as possible
> 2. Provide a mean for standard (yet advanced) developers to
> activate/deactivate built-in contexts at will (probably thru interceptors)
> Goal 1 is mandatory for EDR2 while goal 2 is a nice to have.
> John start the work on goal 1 in the coming days.
> For goal 2 it would be nice that each of us think about one or more real
> life use case that this context activation could allow to check if the
> design SPI fits the need.
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> 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...
More information about the cdi-dev