[cdi-dev] [JBoss JIRA] (CDI-626) How should CDI.current() and CDI.getBeanManager() behave for non-CDI apps?

[Antoine Sabot-Durand (JIRA)]

    [ https://issues.jboss.org/browse/CDI-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290063#comment-13290063 ] 

Antoine Sabot-Durand edited comment on CDI-626 at 9/7/16 12:49 PM:
-------------------------------------------------------------------

F2F decided to treat CDI.current() as IllegalStateException when CDI is not available. It's the current API behaviour.
Javadoc needs to be clarified on that point.


was (Author: antoinesabot-durand):
F2F decided to treat CDI.current() as IllegalStateException when CDI is not available. It's the current API behaviour. 

> How should CDI.current() and CDI.getBeanManager() behave for non-CDI apps?
> --------------------------------------------------------------------------
>
>                 Key: CDI-626
>                 URL: https://issues.jboss.org/browse/CDI-626
>             Project: CDI Specification Issues
>          Issue Type: Clarification
>            Reporter: Mark Struberg
>            Assignee: Antoine Sabot-Durand
>              Labels: F2F2016
>             Fix For: 2.0 (proposed)
>
>
> We did hit the following situation: 
> A user installs a Spring application WAR file in TomEE. In that case we don't boot the CDI container. But the JSF Container calls CDI.current(). 
> How should CDI.current() behave in that case? Throwing an IllegalStateException, returning null or return a non-functional BeanManager?
> We should also define the behaviour of CDI.getBeanManager while we are at it.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)