Actually I think it will be able to get into 2.1 for sure. I've already got the go ahead from Ryan Lubke to submit a patch for Mojarra, so if you guys are on board, too, then I think it's easy to get added :)
It's so useful, I'm really excited to see it supported. I'll be in touch as I work on patching Mojarra. Let me know how it goes with MyFaces, and we can keep each other informed of any issues we run in to. Thanks! --Lincoln On Tue, Mar 9, 2010 at 2:48 PM, Jakob Korherr (JIRA) <[email protected] > wrote: > > [ > https://issues.apache.org/jira/browse/MYFACES-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843263#action_12843263] > > Jakob Korherr commented on MYFACES-2590: > ---------------------------------------- > > Hmm OK. This is actually not bad :) > > I personally really like CDI. I think it's a very great technique and it > spares you lots of boilerplate code. > > Unfortunately, this will by no means get into the JSF 2.0 spec, I think. > Maybe in JSF 2.NEXT but who knows.. However, I'll take a look at this, > because it just seems right and it's a nice feature! > > > Web Container injection support should be provided for additional > lifecycle artifacts (not just managed beans) > > > -------------------------------------------------------------------------------------------------------------- > > > > Key: MYFACES-2590 > > URL: https://issues.apache.org/jira/browse/MYFACES-2590 > > Project: MyFaces Core > > Issue Type: Improvement > > Components: JSR-314 > > Environment: ALL > > Reporter: Lincoln Baxter III > > > > JSF implementations should treat the following framework components as > JEE > > components, and pass them through the default > WebInjectionProvider.inject() > > method part of any instantiation process. E.g: Whether or not the > framework is > > instantiating the object for it's use, or the user is asking the > framework for a > > new instance. > > The benefit: This means that any container provided injection points > would > > automatically be available in the following artifacts: > > * ManagedBean > > * PhaseListener > > * SystemEventListener > > * Converter > > * Validator > > * ... more? > > For extension writers: > > Support for native container-injection for all artifacts defined in > > section 11.4.6 of the JSR-314 spec. > > ■ ActionListener > > ■ ApplicationFactory > > ■ FacesContextFactory > > ■ LifecycleFactory > > ■ NavigationHandler > > ■ PropertyResolver > > ■ RenderKit > > ■ RenderKitFactory > > ■ ResourceHandler > > ■ StateManager > > ■ VariableResolver > > ■ ViewHandler > > There is a related SPEC issue, Mojarra enhancement, and GlassFish bug > also involved in getting this > > standardized across the board: > > > https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=763 > > https://glassfish.dev.java.net/issues/show_bug.cgi?id=11655 > > https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=1578 > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > > -- Lincoln Baxter, III http://ocpsoft.com http://scrumshark.com "Keep it Simple"
