[MYFACES-1761] Handling PostConstruct annotations - wrong order

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.0, 1.2.1-SNAPSHOT
• Fix Version/s: 1.2.7
• Assignee: Leonardo Uribe
• Reporter: Bernhard Huemer
• Created: 06/Nov/07 22:18
• Updated: 12/May/14 15:03
• Resolved: 15/May/09 05:07

Description

The specification states that managed bean methods annotated with @PostConstruct have to be called after the object is initialized and after dependency injection is performed. However, MyFaces calls those methods after the bean instance is created but before dependency injection is performed (for example, see http://www.nabble.com/myfaces-1.2.0-postConstruct-tf4760326.html ). In order to resolve this bug the LifecycleProvider interface has to be changed. Currently there's only one method responsible for creating/initializing a new bean: newInstance(). This design choice implicates that there's no possibility to seperate the steps "creating the bean" and "postconstructing the bean".

Issue Links

• is duplicated by: MYFACES-1246 JSR-252 Issue #119: implementations running in a JSR-250 container have their managed bean methods annotated with @PostConstruct be called after the object is instantiated, and after injection is performed, but before the bean is placed into scope.