No doubt, I think he's been holding out on us.  :)

Kito Mann wrote:
Busy day, Michael? :-)

On Tue, Dec 9, 2008 at 2:05 PM, Michael Freedman (JIRA) <[email protected] <mailto:[email protected]>> wrote:


        [
    
https://issues.apache.org/jira/browse/PORTLETBRIDGE-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
    ]

    Michael Freedman resolved PORTLETBRIDGE-47.
    -------------------------------------------

          Resolution: Fixed
       Fix Version/s: 2.0.0
                      1.0.0

    bridge has been modified to pass/ really on the PortletContext to
    the FacesContextFactory vs the PortletConfig.

    > BridgeImpl pass PortletConfig instance to FacesContextFactory
    instead PortletContext
    >
    
------------------------------------------------------------------------------------
    >
    >                 Key: PORTLETBRIDGE-47
    >                 URL:
    https://issues.apache.org/jira/browse/PORTLETBRIDGE-47
    >             Project: MyFaces Portlet Bridge
    >          Issue Type: Bug
    >    Affects Versions: 1.0.0-alpha-2
    >            Reporter: Leonardo Uribe
    >            Priority: Critical
    >             Fix For: 1.0.0, 2.0.0
    >
    >
    > On myfaces portlet bridge (for jsf 1.2) do this
    (org.apache.myfaces.portlet.faces.bridge.BridgeImpl line 240):
    >     try
    >     {
    >       // Get the FacesContext instance for this request
    >       context =
> getFacesContextFactory().getFacesContext(mPortletConfig, request,
    response, getLifecycle());
    > It should pass a javax.portlet.PortletContext instance instead,
    because this is the expected var here.

    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.




--
Kito D. Mann -- Author, JavaServer Faces in Action
http://twitter.com/kito99
http://www.virtua.com - JSF/Java EE consulting, training, and mentoring
http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info
+1 203-404-4848 x3




Reply via email to