ExtensionBean}}s were never added to the {{BeanDeployerEnvironment. Consequently, ExtensionBean.initialize(BeanDeployerEnvironment) was never called and the AbstractBuiltInBean.proxyRequired field was never properly initialized for {{ExtensionBean}}s.
This is now fixed, but the fix may break some applications that declare public fields in extensions. Since injected extensions will now always be proxied, externally accessing their public fields will not return correct values. The CDI spec should probably prevent this by throwing a definition exception when an extension declares a public field - the same as it does with managed beans.
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
Pull request at https://github.com/weld/core/pull/344
ExtensionBean}}s were never added to the {{BeanDeployerEnvironment. Consequently, ExtensionBean.initialize(BeanDeployerEnvironment) was never called and the AbstractBuiltInBean.proxyRequired field was never properly initialized for {{ExtensionBean}}s.
This is now fixed, but the fix may break some applications that declare public fields in extensions. Since injected extensions will now always be proxied, externally accessing their public fields will not return correct values. The CDI spec should probably prevent this by throwing a definition exception when an extension declares a public field - the same as it does with managed beans.