[cdi-dev] [JBoss JIRA] (CDI-395) Public fields in extensions should not be allowed

Antoine Sabot-Durand (JIRA) issues at jboss.org
Tue Dec 17 08:14:33 EST 2013

     [ https://issues.jboss.org/browse/CDI-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Antoine Sabot-Durand resolved CDI-395.

    Resolution: Rejected

Resolving this could bring more problems (with backward compatibility) that it could solve.
Implementations are encouraged to give a warning when it's detected in the code.
> Public fields in extensions should not be allowed
> -------------------------------------------------
>                 Key: CDI-395
>                 URL: https://issues.jboss.org/browse/CDI-395
>             Project: CDI Specification Issues
>          Issue Type: Clarification
>          Components: Portable Extensions
>    Affects Versions: 1.1.PFD
>            Reporter: Marko Lukša
> Since the container must provide an @ApplicationScoped bean for every extension and since a proxy must be injected into injection points requesting this bean, it should be clear that extensions should not be allowed to have public fields. The spec doesn't specify this explicitly, but it should - like it does for non-dependent managed beans.
> The container should treat this as a definition error, otherwise people may end up accessing these public fields of extensions and getting weird errors.
> See also WELD-1474

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

More information about the cdi-dev mailing list