I'd say b.

Enforcing the correct behavior via API sounds better than a sentence in the spec. And makes it easier to keep implementations and applications compatible.

Werner



On Wed, Aug 3, 2016 at 12:03 PM, <cdi-dev-request@lists.jboss.org> wrote:
Send cdi-dev mailing list submissions to
        cdi-dev@lists.jboss.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.jboss.org/mailman/listinfo/cdi-dev
or, via email, send a message with subject or body 'help' to
        cdi-dev-request@lists.jboss.org

You can reach the person managing the list at
        cdi-dev-owner@lists.jboss.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of cdi-dev digest..."


Today's Topics:

   1. [Vote] for CDI-616 resolution (Antoine Sabot-Durand)
   2. Re: [Vote] for CDI-616 resolution (Emily Jiang)
   3. Re: [Vote] for CDI-616 resolution (Romain Manni-Bucau)
   4. Re: [Vote] for CDI-616 resolution (Matej Novotny)


----------------------------------------------------------------------

Message: 1
Date: Wed, 03 Aug 2016 09:21:04 +0000
From: Antoine Sabot-Durand <antoine@sabot-durand.net>
Subject: [cdi-dev] [Vote] for CDI-616 resolution
To: cdi-dev <cdi-dev@lists.jboss.org>
Message-ID:
        <CABu-YBSE4gAFtaa8jPLkkcOGpPci0Q3T6smneaAtCO0aC+UQcg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi all,

During yesterday(s meeting we discussed how to solve CDI-616 issue.
2 options are possible but we didn't find an agreement, so the best
solution here would be to vote.

Options are:

a) Do nothing about injection in transient fields (todays behaviour) but
add a clarification in the spec saying that using them is not supported.
b) Throw an exception at boot time if a transient field is an injection
point.

To vote, just answer to this mail with the letter of your vote. Vote will
last 72 hrs from the hour of this mail.

Thank you,

Antoine
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160803/16192536/attachment-0001.html

End of cdi-dev Digest, Vol 69, Issue 3
**************************************