You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Ethan Adams (JIRA)" <je...@portals.apache.org> on 2006/07/20 21:43:13 UTC
[jira] Created: (JS2-561) SessionNavigationalState is storing
render parameters in session
SessionNavigationalState is storing render parameters in session
----------------------------------------------------------------
Key: JS2-561
URL: http://issues.apache.org/jira/browse/JS2-561
Project: Jetspeed 2
Issue Type: Bug
Affects Versions: 2.1-dev
Environment: Java 1.5, Oracle, Tomcat .5.5.17
Reporter: Ethan Adams
Changed NavigationalState implementation from org.apache.jetspeed.container.state.impl.SessionFullNavigationalState to org.apache.jetspeed.container.state.impl.SessionNavigationalState, but the render parameters are still stored in session. This used to work as expected in 2.0 final. ie. only portletwindow state (window state and portlet mode) are saved in the session, parameters are encoded on the url.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Closed: (JS2-561) SessionNavigationalState is storing render
parameters in session
Posted by "David Sean Taylor (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-561?page=all ]
David Sean Taylor closed JS2-561.
---------------------------------
Resolution: Fixed
closed per reporter's request
> SessionNavigationalState is storing render parameters in session
> ----------------------------------------------------------------
>
> Key: JS2-561
> URL: http://issues.apache.org/jira/browse/JS2-561
> Project: Jetspeed 2
> Issue Type: Bug
> Affects Versions: 2.1-dev
> Environment: Java 1.5, Oracle, Tomcat .5.5.17
> Reporter: Ethan Adams
>
> Changed NavigationalState implementation from org.apache.jetspeed.container.state.impl.SessionFullNavigationalState to org.apache.jetspeed.container.state.impl.SessionNavigationalState, but the render parameters are still stored in session. This used to work as expected in 2.0 final. ie. only portletwindow state (window state and portlet mode) are saved in the session, parameters are encoded on the url.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Commented: (JS2-561) SessionNavigationalState is storing
render parameters in session
Posted by "Ethan Adams (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-561?page=comments#action_12422626 ]
Ethan Adams commented on JS2-561:
---------------------------------
This can be closed. This works as it should. My mistake.
> SessionNavigationalState is storing render parameters in session
> ----------------------------------------------------------------
>
> Key: JS2-561
> URL: http://issues.apache.org/jira/browse/JS2-561
> Project: Jetspeed 2
> Issue Type: Bug
> Affects Versions: 2.1-dev
> Environment: Java 1.5, Oracle, Tomcat .5.5.17
> Reporter: Ethan Adams
>
> Changed NavigationalState implementation from org.apache.jetspeed.container.state.impl.SessionFullNavigationalState to org.apache.jetspeed.container.state.impl.SessionNavigationalState, but the render parameters are still stored in session. This used to work as expected in 2.0 final. ie. only portletwindow state (window state and portlet mode) are saved in the session, parameters are encoded on the url.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org