[ https://issues.jboss.org/browse/JBIDE-9401?page=com.atlassian.jira.plugin... ] Alexey Kazakov updated JBIDE-9401: ---------------------------------- Fix Version/s: 3.3.0.M3 Assignee: Viacheslav Kabanovich (was: Alexey Kazakov) Workaround Description: 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} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ 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

[ https://issues.jboss.org/browse/JBIDE-9401?page=com.atlassian.jira.plugin... ] Alexey Kazakov edited comment on JBIDE-9401 at 7/26/11 1:08 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 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: {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} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9401?page=com.atlassian.jira.plugin... ] Alexey Kazakov edited comment on JBIDE-9401 at 7/28/11 2:59 PM: ---------------------------------------------------------------- We should mark an injection point with type Conversation as ambiguous if its project has weld jars in the classpath. was (Author: akazakov): We should mark an injection point as ambiguous if its project has weld jars in the classpath. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9401?page=com.atlassian.jira.plugin... ] Viacheslav Kabanovich commented on JBIDE-9401: ---------------------------------------------- I have re-implemented other built-in beans and removed loading of Weld jars without beans.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9401?page=com.atlassian.jira.plugin... ] Jaroslav Jankovič closed JBIDE-9401. ------------------------------------ verified on JBoss Developer Studio 5.0.0.v201108060131N-H712-M3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira