[ https://issues.jboss.org/browse/WELD-814?page=com.atlassian.jira.plugin.s... ] John Ament updated WELD-814: ---------------------------- Workaround Description: Use method level producers for resources. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/WELD-814?page=com.atlassian.jira.plugin.s... ] Pete Muir closed WELD-814. -------------------------- Resolution: Rejected This is spec defined behavior. From 3.5 "The container is not required to support resources with scope other than @Dependent. Portable applications should not define resources with any scope other than @Dependent." -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/WELD-814?page=com.atlassian.jira.plugin.s... ] Pete Muir commented on WELD-814: -------------------------------- The key difference between the two approaches above is that in resource producer field you are, in essence, "aliasing" that resource as a CDI bean with a specified qualifier and type. CDI is responsible for managing the lifecycle, and the only lifecycle that generally makes sense is dependent scoped. In the case of a resource injection + producer method, you are injecting a resource and taking control of it's lifecycle yourself via the producer method that exposes it. IOW in the second case you are taking responsibility for the lifecycle of the resource instance and thus can choose whatever scope you want. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira