myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Freedman (JIRA)" <...@myfaces.apache.org>
Subject [jira] Commented: (PORTLETBRIDGE-41) EncodeActionURL doesn't encode valid nonFaces targets
Date Thu, 24 Jul 2008 23:05:31 GMT

    [ https://issues.apache.org/jira/browse/PORTLETBRIDGE-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616705#action_12616705
] 

Michael Freedman commented on PORTLETBRIDGE-41:
-----------------------------------------------

This has been fixed in the Portlet 1.0 Bridge codeline but hasn't yet been fixed in the 2.0
codeline hence the bug is left open as a reminder to merge the work.

> 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
>
> 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.


Mime
View raw message