You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Jakob Korherr (JIRA)" <de...@myfaces.apache.org> on 2010/03/08 21:45:27 UTC

[jira] Commented: (MYFACES-2590) Web Container injection support should be provided for additional lifecycle artifacts (not just managed beans)

    [ https://issues.apache.org/jira/browse/MYFACES-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842811#action_12842811 ] 

Jakob Korherr commented on MYFACES-2590:
----------------------------------------

Can you explain this a little further please, Lincoln? For example what use cases do you see in this?

> 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.