Yes it will cause start up issues for applications which define transient normal scoped injections, however these Apps currently have runtime issues after dezieralization of passivatable scoped bean.

Trading an easily fixable start-up issue for a hard to reproduce runtime issue seems like a good trade off to me.

Stephan
 




On Tue, 19 Jul 2016 at 12:12 Emily Jiang <EMIJIANG@uk.ibm.com> wrote:
If we define an error, we will introduce a backward compatibility issue. Some app will stop starting. Will this cause a big problem? If this is not a concern, +1 on defining a DefinitionError on this case: ERROR - when normal scoped injects are marked transient. and a warning on WARNING - when non-normal scoped injects are marked transient.

Many thanks,
Emily
===========================
Emily Jiang
WebSphere Application Server, CDI Development Lead
 
MP 211, DE3A20, Winchester, Hampshire, England, SO21 2JN
Phone:  +44 (0)1962 816278  Internal: 246278

Email: emijiang@uk.ibm.com
Lotus Notes: Emily Jiang/UK/IBM@IBMGB



From:        Stephan Knitelius <stephan@knitelius.com>
To:        cdi-dev <cdi-dev@lists.jboss.org>,
Date:        19/07/2016 08:26
Subject:        [cdi-dev] CDI-616 Injection point declared as transient is not        useful
Sent by:        cdi-dev-bounces@lists.jboss.org



Hi,

I frequently encounter injections marked transient in client projects. I really think it would be of great help if we where to define Error/Warning when injection fields are marked transient. 

As Mark pointed out there may be a valid use cases for non normal-scoped bean injections to be made transient. 

My suggestion is: