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 2010/02/17 19:06:28 UTC

[jira] Resolved: (PORTLETBRIDGE-121) Exception thrown if PRP bean associated with PRP mapping doesn't exist

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

Michael Freedman resolved PORTLETBRIDGE-121.
--------------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0

BridgeImpl.processIncomingPublicRenderParameters extended its try/catch block to include the code that gets the value from the EL expression.  Likewise processOutgoingPublicRenderparameters was also updated.

> Exception thrown if PRP bean associated with PRP mapping doesn't exist
> ----------------------------------------------------------------------
>
>                 Key: PORTLETBRIDGE-121
>                 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-121
>             Project: MyFaces Portlet Bridge
>          Issue Type: Bug
>    Affects Versions: 2.0.0-alpha
>            Reporter: Michael Freedman
>            Assignee: Michael Freedman
>             Fix For: 2.0.0
>
>
> If you have a PRP mapping with an EL statement to a backing bean and this backing bean doesn't exist a exception is thrown.  One reason this occurs is if you have a generic mapping for a PRP (i.e. not qualified to a specific portlet).  If your portlet says it supports this PRP but  the corresponding mapped EL/backing bean doesn't exist (for this portlet) an exception is thrown.  Other situations are simplify mistyped EL expressions.

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