You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Tuomas Kiviaho (JIRA)" <ji...@apache.org> on 2007/05/21 12:43:16 UTC

[jira] Created: (PLUTO-369) Inconsistency in PortletRequest attribute handling

Inconsistency in PortletRequest attribute handling
--------------------------------------------------

                 Key: PLUTO-369
                 URL: https://issues.apache.org/jira/browse/PLUTO-369
             Project: Pluto
          Issue Type: Bug
          Components: portlet container
            Reporter: Tuomas Kiviaho


PortletRequest handling of attributes with reserved prefix ('java' or 'javax') is not consistent between getAttribute and getAttributeNames. Former returns values for reserved attributes while latter doesn't iterate over them. I can't find reference from spec which restricts reserved attributes from being iterated over. 

This is annoying when framework on top of the api obscures request attribute semantics. Hence attributes like "javax.portlet.faces.defaultViewId" have to be used with extreme caution.

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


[jira] Resolved: (PLUTO-369) Inconsistency in PortletRequest attribute handling

Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PLUTO-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Craig Doremus resolved PLUTO-369.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 1.1.4
                   1.2.0

Fixed in PortletRequestImpl in SVN trunk revision 553851 and pluto-1.1.x revision 553855

> Inconsistency in PortletRequest attribute handling
> --------------------------------------------------
>
>                 Key: PLUTO-369
>                 URL: https://issues.apache.org/jira/browse/PLUTO-369
>             Project: Pluto
>          Issue Type: Bug
>          Components: portlet container
>            Reporter: Tuomas Kiviaho
>            Assignee: Craig Doremus
>             Fix For: 1.2.0, 1.1.4
>
>
> PortletRequest handling of attributes with reserved prefix ('java' or 'javax') is not consistent between getAttribute and getAttributeNames. Former returns values for reserved attributes while latter doesn't iterate over them. I can't find reference from spec which restricts reserved attributes from being iterated over. 
> This is annoying when framework on top of the api obscures request attribute semantics. Hence attributes like "javax.portlet.faces.defaultViewId" have to be used with extreme caution.

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


[jira] Closed: (PLUTO-369) Inconsistency in PortletRequest attribute handling

Posted by "Elliot Metsger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PLUTO-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Elliot Metsger closed PLUTO-369.
--------------------------------


> Inconsistency in PortletRequest attribute handling
> --------------------------------------------------
>
>                 Key: PLUTO-369
>                 URL: https://issues.apache.org/jira/browse/PLUTO-369
>             Project: Pluto
>          Issue Type: Bug
>          Components: portlet container
>            Reporter: Tuomas Kiviaho
>            Assignee: Craig Doremus
>             Fix For: 1.2.0, 1.1.4
>
>
> PortletRequest handling of attributes with reserved prefix ('java' or 'javax') is not consistent between getAttribute and getAttributeNames. Former returns values for reserved attributes while latter doesn't iterate over them. I can't find reference from spec which restricts reserved attributes from being iterated over. 
> This is annoying when framework on top of the api obscures request attribute semantics. Hence attributes like "javax.portlet.faces.defaultViewId" have to be used with extreme caution.

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


[jira] Assigned: (PLUTO-369) Inconsistency in PortletRequest attribute handling

Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PLUTO-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Craig Doremus reassigned PLUTO-369:
-----------------------------------

    Assignee: Craig Doremus

> Inconsistency in PortletRequest attribute handling
> --------------------------------------------------
>
>                 Key: PLUTO-369
>                 URL: https://issues.apache.org/jira/browse/PLUTO-369
>             Project: Pluto
>          Issue Type: Bug
>          Components: portlet container
>            Reporter: Tuomas Kiviaho
>            Assignee: Craig Doremus
>
> PortletRequest handling of attributes with reserved prefix ('java' or 'javax') is not consistent between getAttribute and getAttributeNames. Former returns values for reserved attributes while latter doesn't iterate over them. I can't find reference from spec which restricts reserved attributes from being iterated over. 
> This is annoying when framework on top of the api obscures request attribute semantics. Hence attributes like "javax.portlet.faces.defaultViewId" have to be used with extreme caution.

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