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

Michael Freedman resolved PORTLETBRIDGE-41.
-------------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0
                   1.0.0

As per previous comment. I have now merged this code from the 1.0 code line to 
the 2.0 codeline so bug is fixed in both versions.

> EncodeActionURL doesn't encode valid nonFaces targets
> -----------------------------------------------------
>
>                 Key: PORTLETBRIDGE-41
>                 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-41
>             Project: MyFaces Portlet Bridge
>          Issue Type: Bug
>          Components: Impl
>    Affects Versions: 1.0.0, 2.0.0
>            Reporter: Michael Freedman
>            Assignee: Michael Freedman
>             Fix For: 1.0.0, 2.0.0
>
>
> Faces allows one to construct an action URL (navigation) to a nonFaces 
> target.  However the bridges (ExternalContext) encodeActionURL only 
> recognizes and encodes Faces targets.  What it should do when it encounters a 
> nonFaces target (within the web app) is encode it distinctly from a Faces 
> target as a portlet renderURL.  The bridge on receiving such a render request 
> should recognize the nonFaces target and do an immediate dispatch rather then 
> processing the request through Faces (lifecycle).  

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

Reply via email to