Yeah. There was some reason why this "vague" approach to ordering was used (I
think it came down from "on high". We can try to rework it :-)
-> issue tracker...
On 18 Oct 2011, at 22:34, Rick Hightower wrote:
Is section 5.5.2 trying to say this:
•CDI ensures:
–All fields are injected (of superclasses and current class) before initializer methods
are called
–Injected fields include Java EE resource dependencies
–@PostConstruct are called after initializers
–Java EE: servlet init() method after initializers
It says....
The container must ensure that:
• Initializer methods declared by a class X in the type hierarchy of the bean are called
after all injected fields declared by X or by superclasses of X have been initialized, and
after all Java EE component environment resource dependencies declared by X or by
superclasses of X have been injected.
• Any @PostConstruct callback declared by a class X in the type hierarchy of the bean is
called after all initializer meth- ods declared by X or by superclasses of X have been
called, after all injected fields declared by X or by superclasses of X have been
initialized, and after all Java EE component environment resource dependencies declared by
X or by su- perclasses of X have been injected.
• Any servlet init() method is called after all initializer methods have been called, all
injected fields have been initial- ized and all Java EE component environment resource
dependencies have been injected.
--
Rick Hightower
(415) 968-9037
Profile
_______________________________________________
cdi-dev mailing list
cdi-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/cdi-dev