myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Marinschek (JIRA)" <>
Subject [jira] Commented: (MYFACES-1761) Handling PostConstruct annotations - wrong order
Date Fri, 09 Nov 2007 12:13:50 GMT


Martin Marinschek commented on MYFACES-1761:

@Paul: I think we should do the same as the RI does (especially, as what the RI does is a
lot more inline with what a user would expect). 

We need to be compliant not only to the spec wording, but also to the meaning, and the meaning
is interpreted by what the RI does (we can certainly behave different if compatiblity is not
at stake and if we do things better for the user, but not worse). So this is indeed a bug!



> Handling PostConstruct annotations - wrong order
> ------------------------------------------------
>                 Key: MYFACES-1761
>                 URL:
>             Project: MyFaces Core
>          Issue Type: Bug
>    Affects Versions:  1.2.0, 1.2.1-SNAPSHOT
>            Reporter: Bernhard Huemer
>             Fix For: 1.2.1-SNAPSHOT
>         Attachments: MyFaces-1761.patch,
> 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
). 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".

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

View raw message