Don't forget that JSF entails more than just managed beans. It also included event listeners, phase listeners (and perhaps others I'm not thinking of).

JSF is really been such a problem child in this respect. Is there something we can push for in the JSF spec to make this type of integration easier? For instance, I don't believe that listeners in JSF are managed, but perhaps they should be (support @PostConstruct, @PreDestory and resource injection...hence that would include 299 injections as well).

-Dan

On Mon, Jul 20, 2009 at 11:53 AM, Pete Muir <pmuir@redhat.com> wrote:
Hi Kabir, Jason,

As I mentioned, 299 requires that we inject any "Java EE components
classes supporting injection" with 299 dependencies:

* Servlet - servlets, servlet filters, event listeners
* JSP tag handlers, tag library event listeners
* JSF scoped managed beans
* JAX-WS service endpoints, handlers
* EJB beans, interceptors
* Java EE  platform main class (static)
* login callback handler

Ales and I propose we do this via enabling 299 injection into MC
supported component models where possible.

Some (e.g. JSF) won't work, and will need other integration...

How far are all of these from being MC enabled?

How do we want to create JIRA issues for these to be done?



Note, I'm still missing the impl for this, but the API is something
like:

// for each class supporting injection

InjectionTarget it = beanManager.createInjectionTarget(type);

// for each instance requiring injection

it.inject(instance, beanManager.createCreationalContext(null));

// postconstruct hook

it.postConstruct(instance);

it.preDestroy(instance);
_______________________________________________
webbeans-dev mailing list
webbeans-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/webbeans-dev



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

http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://in.relation.to/Bloggers/Dan