You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Michael Freedman (JIRA)" <de...@myfaces.apache.org> on 2009/12/11 21:56:18 UTC

[jira] Resolved: (PORTLETBRIDGE-101) GenericFacesPortlet uses the wrong name for the bridge class initialization parameter according to the spec

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

Michael Freedman resolved PORTLETBRIDGE-101.
--------------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0
                   1.0.0
         Assignee: Michael Freedman

Changed to corrct name.

> GenericFacesPortlet uses the wrong name for the bridge class initialization parameter according to the spec
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: PORTLETBRIDGE-101
>                 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-101
>             Project: MyFaces Portlet Bridge
>          Issue Type: Bug
>          Components: API
>    Affects Versions: 1.0.0-beta
>            Reporter: Alistair Wilson
>            Assignee: Michael Freedman
>            Priority: Minor
>             Fix For: 1.0.0, 2.0.0
>
>
> The spec for Portlet Bridge 1.0 states in section 4.1:
> "To provide flexibility, the GenericFacesPortlet recognizes the following application initialization parameters:
> javax.portlet.faces.BridgeClassName 
>  
> BridgeClassName specifies the name of the bridge class the GenericFacesPortlet uses to instantiate bridge instances for all portlets in this web application."
> The current version of the code uses the initialization parameter named:
> javax.portlet.faces.BridgeImplClass

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