[
https://issues.apache.org/jira/browse/TOMEE-2448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Louis MONTEIRO reassigned TOMEE-2448:
------------------------------------------
Assignee: Doychin
> When non CDI app(JSF managed bean) is deployed after CDI app in the same
> thread, any request to non CDI app fails if it uses managed beans in JSF
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TOMEE-2448
> URL: https://issues.apache.org/jira/browse/TOMEE-2448
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
> Affects Versions: 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.1.0, 7.1, 8.0.0-M1
> Reporter: Doychin
> Assignee: Doychin
> Priority: Minor
>
> A change introduced in
> [commit|https://github.com/apache/tomee/commit/74b3cffae81620b81492c03d32c2bec69e37a149]
> breaks the proper restoration of null WebBeansContext.
> That problem is visible when you run all arquillian-tomee-jms-tests.
> JMSInjectionTest fails because during deployment valid WebBeansContext is
> left in the holder thread local variable. That results in creation of
> InjectableBeanManager in OwbCDI class.
> If there is no WebBeansContext an exception is thrown and such bean manager
> is never created.
> Because the container now has valid bean manager some of the libraries think
> that this app supports CDI and try to lookup some resources that were never
> initialized and all requests to this app will fail.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
