[EXTVAL-110] Allow Extval Custom Java ExtValModuleConfig objects in Bean jars (CDI)

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.2.4, 2.0.4, 1.1.4
• Fix Version/s: 1.2.4, 2.0.4, 1.1.4
• Component/s: Core, Property Validation, Trinidad Support
• Assignee: Unassigned
• Reporter: Rudy De Busscher
• Created: 27/Jul/10 08:10
• Updated: 27/Nov/10 06:06
• Resolved: 27/Jul/10 10:32

Description

OpenWebBeans initializes all classes in the archives (jars or classes directory) that have a beans.xml file.

But since the ExtValModuleConfig classes have all the following line
private static ExtValContext extValContext = ExtValContext.getContext();

The ExtvalContext is initialized during startup of the WebContainer when the project extends this class (cutoms Java ExtValModuleConfig ). In the constructor of the ExtValContext class, we try to access the web.xml initialization parameter through facesContext, which is not yet available.

solution:
Leave the static variable empty and use a method that initializes the variable when first requested. (used by the get() and use() methods)

Issue Links

• is a clone of: EXTVAL-109 Extval Custom Java ExtValModuleConfig and OpenWebBeans -> NPE during startup WebContainer