[TOMEE-2448] 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

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.1.0, 7.1, 8.0.0-M1
• Fix Version/s: 8.0.0-M2
• Component/s: TomEE Core Server
• Assignee: Doychin Bondzhev
• Reporter: Doychin Bondzhev
• Created: 05/Jan/19 12:47
• Updated: 07/Jan/19 19:50
• Resolved: 07/Jan/19 19:50

Description

A change introduced in commit 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.