[OWB-412] Allow container specific extensions to WebConfigurationListener access to the lifecycle

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.0.0-alpha-1
• Fix Version/s: 1.0.0-alpha-2
• Component/s: Java EE Integration
• Assignee: Joseph E Bergmark
• Reporter: Joseph E Bergmark
• Created: 21/Jul/10 15:42
• Updated: 07/Sep/10 09:56
• Resolved: 23/Jul/10 21:14

Description

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.