myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rudy De Busscher (JIRA)" <>
Subject [jira] Resolved: (EXTVAL-110) Allow Extval Custom Java ExtValModuleConfig objects in Bean jars (CDI)
Date Tue, 27 Jul 2010 10:34:16 GMT


Rudy De Busscher resolved EXTVAL-110.

    Fix Version/s: 1.2.4-SNAPSHOT
       Resolution: Fixed

> Allow Extval Custom Java ExtValModuleConfig objects in Bean jars (CDI)
> ----------------------------------------------------------------------
>                 Key: EXTVAL-110
>                 URL:
>             Project: MyFaces Extensions Validator
>          Issue Type: Improvement
>          Components: Core, Property Validation, Trinidad Support
>    Affects Versions: 1.2.4-SNAPSHOT, 2.0.4-SNAPSHOT, 1.1.4-SNAPSHOT
>            Reporter: Rudy De Busscher
>            Priority: Minor
>             Fix For: 1.2.4-SNAPSHOT, 2.0.4-SNAPSHOT, 1.1.4-SNAPSHOT
> 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) 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message