[jira] Resolved: (OWB-412) Allow container specific extensions to WebConfigurationListener access to the lifecycle

["Joe Bergmark (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OWB-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joe Bergmark resolved OWB-412.
------------------------------

    Fix Version/s: 1.0.0-alpha-2
                       (was: 1.0.0-alpha-3)
       Resolution: Fixed

> Allow container specific extensions to WebConfigurationListener access to the lifecycle
> ---------------------------------------------------------------------------------------
>
>                 Key: OWB-412
>                 URL: https://issues.apache.org/jira/browse/OWB-412
>             Project: OpenWebBeans
>          Issue Type: Improvement
>          Components: Java EE Integration
>    Affects Versions: 1.0.0-alpha-1
>            Reporter: Joe Bergmark
>            Assignee: Joe Bergmark
>            Priority: Minor
>             Fix For: 1.0.0-alpha-2
>
>
> If the lifecycle field of WebConfigurationListener was protected rather than private, any container specific extensions could access it as well.  It seems pretty natural for this class to be extended in a full EE environment where the container may wish to automatically register other parts of OWB (such as the EL Resolver, View Handler, etc) so each application does not need to define these.
> If no one has any objections I will make this small change.

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