On Sat, Jul 25, 2009 at 6:26 PM, Norbert Truchsess <norbert.truchsess@t-online.de> wrote:
Am Mittwoch, den 22.07.2009, 21:40 -0700 schrieb Alaxander Smirnov:
> Most of the JSF listener tags supports 'bind' attribute that allows to
> use any JSF beans as  listeners, that could have any scope and where
> injection library could make any necessary work.
> Because narrow listener objects are saved in the components tree, in
> addition to the injection we should also define some addition
> lifecycle methods ( e.g. activate/passivate ), otherwise status of
> injected objects will be unpredictable. I suggest to check only is all
> listener could be defined as binding to the JSF beans.
In respect to status of injected objects I cannot see the need for
additional lifecycle methods (on the listener objects). We should
support @Postconstruct/@Predestroy annotations (for consistency).

But the status of injected Objects should be transparently managed by the
container, not the managed objects.

You mean that JSR-299 should handle the injections, correct?

To sum up, what we are trying to do is get PhaseListeners and SystemEventListeners (for instance observing PreRenderViewEvent) to gain the Java EE injection and life cycle services that the managed beans currently bear. I'm not suggesting that they be managed beans, but that they be Java EE components. This has nothing to do with EL bindings in my opinion.


Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597