Hello,
as discussed in the last meeting, I am starting a community vote.
The rules of this vote are captured on CDI wiki page -
https://github.com/eclipse-ee4j/cdi/wiki#decision-making-processVote Duration
Voting will last until May 17 and both committers and non-committers are allowed to vote, although only committer votes are binding
How to Vote
Just reply to this thread with either +1 or -1.
People voting -1 are encouraged to also provide reasoning and/or suggestions for improvement.
But please try to keep the thread concise for voting.
Topic of the Vote
Incorporating CDI Lite inside CDI specification
Summary
Over the past few months there was a lot of discussion and work done in terms of how CDI Lite should work and how it should be housed inside CDI spec.
This vote is held primarily to ratify that what we have been working on so far makes sense and that we want to move forward in this direction.
The proposal is to split the "Core CDI" specification section and create Lite and Full chapters.
Lite is a subset of all the features standard CDI offers and Full builds on top of Lite.
Lite doesn't include specialization, decorators, conversations, passivation and Portable Extensions.
It also doesn't include the full BeanManager API, only a subset.
CDI SE and EE are then both standing on top of Full - meaning there is no actual change for existing deployments WRT to supported features.
The PR drafting these changes can be seen here[1]. Note that there is a substantial amount of spec text reshuffling in order to clearly define what Lite supports and what it doesn't.
Therefore, Ladislav managed to create the following HTML diff[2] which should be easier to read. Should there be any new diffs created, they will be appended in a comment on the PR[1].
The PR is still work in progress and has some minor changes planned (paragraphs that are to be moved around such as any touching on passivation) and two major TBD parts.
These two are build compatible extension model and bean discovery in Lite. Both are being worked on separately, as you probably noticed.
The former is captured here[3] and for the latter, there is a ongoing survey right now[4].
The aforementioned subset of BeanManager capabilities is captured in this PR[5].
Once decided, the spec text will of course be updated accordingly.
Regards
Matej
__________________________________________________________________________
[1]
https://github.com/eclipse-ee4j/cdi/pull/470[2]
https://ladicek.github.io/cdi-spec/diff4.html[3]
https://github.com/Ladicek/StillDI[4]
https://www.eclipse.org/lists/cdi-dev/msg00353.html[5]
https://github.com/eclipse-ee4j/cdi/pull/471