[jira] Commented: (PLUTO-435) PortletSession attributes aren null when using Spring instead of Generic Portlet

["Elliot Metsger (JIRA)" <ji...@apache.org>]

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

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

Michael can you pull down a new release candidate for me and see if this issue is fixed for you - 1.1.5 hasn't been released (it is being voted on now).  You can download the test build from http://people.apache.org/builds/portals-pluto/.  the container-bin distro is probably what you want - the 1.1.5 bin should be a drop-in replacement for the 1.1.4 binaries.

> 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
>            Assignee: Elliot Metsger
>         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 'http://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/spring/browse/SPR-3905?page=com.atlassian.jira.plugin.system.issuetabpanels: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.