You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@myfaces.apache.org by "Thomas Spiegl (JIRA)" <de...@myfaces.apache.org> on 2006/11/09 00:24:54 UTC

[jira] Resolved: (MYFACES-1479) SerialFactory breaks Portlet bridge

     [ http://issues.apache.org/jira/browse/MYFACES-1479?page=all ]

Thomas Spiegl resolved MYFACES-1479.
------------------------------------

    Fix Version/s:     (was: 1.2.0-SNAPSHOT)
       Resolution: Fixed

moved handleSerialFactory from StartupServletContextListener to FacesConfigurator

> SerialFactory breaks Portlet bridge
> -----------------------------------
>
>                 Key: MYFACES-1479
>                 URL: http://issues.apache.org/jira/browse/MYFACES-1479
>             Project: MyFaces Core
>          Issue Type: Bug
>    Affects Versions: 1.1.4
>            Reporter: Stan Silvert
>         Assigned To: Stan Silvert
>            Priority: Blocker
>             Fix For: 1.1.5-SNAPSHOT
>
>
> There is code in StartupServletContextListener that initializes the SerialFactory.  Since portlets don't use the StartupServletContextListener, this never gets initialized and results in a NullPointerException.
> See:
> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=93223
> http://wiki.apache.org/myfaces/PortletSerialFactoryWorkaround
> The handleSerialFactory() method should be in the FacesConfigurator instead of StartupServletContextListener.  You can get the init params via ExternalContext.getInitParameter() instead of ServletContext.getInitParameter().

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira