[jira] Resolved: (PORTLETBRIDGE-16) Path problems in PortletExternalContextImpl.

["Scott O'Bryan (JIRA)" <de...@myfaces.apache.org>]

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

Scott O'Bryan resolved PORTLETBRIDGE-16.
----------------------------------------

    Resolution: Fixed

This has been checked in to the trunk.  Thanks for the patch Mike.

> Path problems in PortletExternalContextImpl.
> --------------------------------------------
>
>                 Key: PORTLETBRIDGE-16
>                 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-16
>             Project: MyFaces Portlet Bridge
>          Issue Type: Bug
>          Components: Impl
>    Affects Versions: 1.0.0-SNAPSHOT
>            Reporter: Michael Freedman
>            Assignee: Scott O'Bryan
>             Fix For: 1.0.0-SNAPSHOT
>
>         Attachments: extctxpath.patch
>
>
> encodeResourceURL currently only creates a context-path relative path when asked to encode a relative path before passing to the portlet container for encoding -- however the portlet API requires this be a fully qualified path (i.e. include the ContextPath).
> isAbsoluteURL doesn't properly test if the url is absolute or not -- What it needs to do is only return true if the url starts with a valid scheme.  I.e. the characters before the : don't contain any of the URI reserved characters.  for example "javascript:;" currently claims it isn't "absolute" when it should be marked as it is.

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