Created: (PLUTO-435) PortletSession attributes aren null when using Spring instead of Generic

PortletSession attributes aren null when using Spring
instead of Generic Portlet
------------------------------------------------------------
--------------------

                 Key: PLUTO-435
                 URL: https
://issues.apache.org/jira/browse/PLUTO-435
             Project: Pluto
          Issue Type: Bug
    Affects Versions: 1.1.4
         Environment: Jetty 6.1.5
Maven 2.0.4
Pluto 1.1.4
Eclipse 3.2.2
Sun JVM - 1.5
            Reporter: Michal Capo


When I use Spring Portlet support for developing portlets I
get got this problem:

(handleAction)
request.getPortletSession().setAttribute("a",
"a", PortletSession.APPLICATION_SCOPE);
(handleRender in the same portlet)
String a =
request.getPortletSession().getAttribute("a",
PortletSession.APPLICATION_SCOPE);
(variable 'a' is null)

I have attached a little test portal. You can run it by
following this steps:
1. unzip this file
2. run 'mvn eclipse:eclipse' (or your other favorit IDE)
3. run/debug file
'src/main/java/org/apache/pluto/test/test1/TestPortal.java'
(within Eclipse)
4. open you favorite browser and go to 'htt
p://localhost:8080/test1/test-portal/index.jsp'
OK I know this is not simply... but you can debug portlets
if you want

Problem:
- click on the first 'click me' link -> everything is ok
- now click on the second one 'click me' -> oops (problem
should appeare here, but is ok)
- restart TestPortal
- click on the second 'click me' link and you got exception

I thought this is spring problem, so I reported this to http://opensource.atlassian.com/projects/sp
ring/browse/SPR-3905?page=com.atlassian.jira.plugin.system.i
ssuetabpanels:all-tabpanel, but it seams like to be
container (pluto) problem not problem of spring portlet
support.

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

     [ https://issues.apache.org/jira/browse/PLUTO-435?page=com.at
lassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michal Capo updated PLUTO-435:
------------------------------

    Attachment: test1.zip

Maven project with testing portal

> PortletSession attributes aren null when using Spring
instead of Generic Portlet
>
------------------------------------------------------------
--------------------
>
>                 Key: PLUTO-435
>                 URL: https
://issues.apache.org/jira/browse/PLUTO-435
>             Project: Pluto
>          Issue Type: Bug
>    Affects Versions: 1.1.4
>         Environment: Jetty 6.1.5
> Maven 2.0.4
> Pluto 1.1.4
> Eclipse 3.2.2
> Sun JVM - 1.5
>            Reporter: Michal Capo
>         Attachments: test1.zip
>
>
> When I use Spring Portlet support for developing
portlets I get got this problem:
> (handleAction)
> request.getPortletSession().setAttribute("a",
"a", PortletSession.APPLICATION_SCOPE);
> (handleRender in the same portlet)
> String a =
request.getPortletSession().getAttribute("a",
PortletSession.APPLICATION_SCOPE);
> (variable 'a' is null)
> I have attached a little test portal. You can run it by
following this steps:
> 1. unzip this file
> 2. run 'mvn eclipse:eclipse' (or your other favorit
IDE)
> 3. run/debug file
'src/main/java/org/apache/pluto/test/test1/TestPortal.java'
(within Eclipse)
> 4. open you favorite browser and go to 'htt
p://localhost:8080/test1/test-portal/index.jsp'
> OK I know this is not simply... but you can debug
portlets if you want
> Problem:
> - click on the first 'click me' link -> everything
is ok
> - now click on the second one 'click me' -> oops
(problem should appeare here, but is ok)
> - restart TestPortal
> - click on the second 'click me' link and you got
exception
> I thought this is spring problem, so I reported this to
http://opensource.atlassian.com/projects/sp
ring/browse/SPR-3905?page=com.atlassian.jira.plugin.system.i
ssuetabpanels:all-tabpanel, but it seams like to be
container (pluto) problem not problem of spring portlet
support.

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

    [ https://issues.apache.org/jira/browse/P
LUTO-435?page=com.atlassian.jira.plugin.system.issuetabpanel
s:comment-tabpanel#action_12530538 ] 

Elliot Metsger commented on PLUTO-435:
--------------------------------------

I added some comments on http://opensource.atlassian.com/projects/spring/
browse/SPR-3905.

> PortletSession attributes aren null when using Spring
instead of Generic Portlet
>
------------------------------------------------------------
--------------------
>
>                 Key: PLUTO-435
>                 URL: https
://issues.apache.org/jira/browse/PLUTO-435
>             Project: Pluto
>          Issue Type: Bug
>    Affects Versions: 1.1.4
>         Environment: Jetty 6.1.5
> Maven 2.0.4
> Pluto 1.1.4
> Eclipse 3.2.2
> Sun JVM - 1.5
>            Reporter: Michal Capo
>         Attachments: test1.zip
>
>
> When I use Spring Portlet support for developing
portlets I get got this problem:
> (handleAction)
> request.getPortletSession().setAttribute("a",
"a", PortletSession.APPLICATION_SCOPE);
> (handleRender in the same portlet)
> String a =
request.getPortletSession().getAttribute("a",
PortletSession.APPLICATION_SCOPE);
> (variable 'a' is null)
> I have attached a little test portal. You can run it by
following this steps:
> 1. unzip this file
> 2. run 'mvn eclipse:eclipse' (or your other favorit
IDE)
> 3. run/debug file
'src/main/java/org/apache/pluto/test/test1/TestPortal.java'
(within Eclipse)
> 4. open you favorite browser and go to 'htt
p://localhost:8080/test1/test-portal/index.jsp'
> OK I know this is not simply... but you can debug
portlets if you want
> Problem:
> - click on the first 'click me' link -> everything
is ok
> - now click on the second one 'click me' -> oops
(problem should appeare here, but is ok)
> - restart TestPortal
> - click on the second 'click me' link and you got
exception
> I thought this is spring problem, so I reported this to
http://opensource.atlassian.com/projects/sp
ring/browse/SPR-3905?page=com.atlassian.jira.plugin.system.i
ssuetabpanels:all-tabpanel, but it seams like to be
container (pluto) problem not problem of spring portlet
support.

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