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 "Ate Douma (JIRA)" <ji...@apache.org> on 2008/10/21 00:36:44 UTC

[jira] Commented: (PLUTO-516) Pluto's PorletSessionImpl#setAttribute sometimes sets var into APPLICATION_SCOPE without explanation

    [ https://issues.apache.org/jira/browse/PLUTO-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641193#action_12641193 ] 

Ate Douma commented on PLUTO-516:
---------------------------------

I agree this seems to be bug in the current Pluto implementation of the portlet api.
I've traced the origin of code in question back to PLUTO-263 and specifically the third patch attached to that issue.

Will investigate further and see if we can fix this one quickly

> Pluto's PorletSessionImpl#setAttribute sometimes sets var into APPLICATION_SCOPE without explanation
> ----------------------------------------------------------------------------------------------------
>
>                 Key: PLUTO-516
>                 URL: https://issues.apache.org/jira/browse/PLUTO-516
>             Project: Pluto
>          Issue Type: Bug
>          Components: portlet container
>            Reporter: Antony Stubbs
>            Assignee: Ate Douma
>             Fix For: 2.0.0
>
>
> as per the confusions around:
> https://issues.apache.org/jira/browse/PB-84
> and:
> http://www.nabble.com/StringIndexOutOfBoundsException-on-apache-bridges-td20055052.html#a20079383
> PorletSessionImpl#setAttribute will sometimes store attributes into APPLICATION_SCOPE, going against the portlet spec. There is also no explanation in the source code as to why.
> Please add explanation or correct the behavior.

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