[jbosstools-issues] [JBoss JIRA] Issue Comment Edited: (JBIDE-9401) No beans eligible for injection warning for Converstaion

[ https://issues.jboss.org/browse/JBIDE-9401?page=com.atlassian.jira.plugin... ] Alexey Kazakov edited comment on JBIDE-9401 at 7/25/11 7:41 PM: ---------------------------------------------------------------- This bean is available for injection in JBT if you have weld jars in the project classpath since there is org.jboss.weld.context.conversation.ConversationImpl bean which implements javax.enterprise.context.Conversation But we should provide bean a built-in bean with bean type Conversation, scope @RequestScoped, and qualifier @Default, named javax.enterprise.context.conversation regardless of project classpath and CDI implementation used in the project. See JSR-299: {quote} 6.7.5. The Conversation interface The container provides a built-in bean with bean type Conversation, scope @RequestScoped, and qualifier @Default, named javax.enterprise.context.conversation. {quote} was (Author: akazakov): This bean is available for injection in JBT if you have weld jars in the project classpath since there is org.jboss.weld.context.conversation.ConversationImpl bean which implements javax.enterprise.context.Conversation But we should provide bean a built-in bean with bean type Conversation, scope @RequestScoped, and qualifier @Default, named javax.enterprise.context.conversation regardless of project classpath and CDI implementation used in the project. See JSR-299: 6.7.5. The Conversation interface The container provides a built-in bean with bean type Conversation, scope @RequestScoped, and qualifier @Default, named javax.enterprise.context.conversation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira