[
https://issues.jboss.org/browse/CDI-626?page=com.atlassian.jira.plugin.sy...
]
Martin Kouba commented on CDI-626:
----------------------------------
I believe that both {{CDIProvider.getCDI()}} and {{CDI.getBeanManager()}} should throw an
{{IllegalStateException}}. But then a user would have no easy way to determine whether a
CDI container is running or not (except for catching the exception).
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
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)