Nevermind. It works. I swear I tested and checked config several times.
On 7/20/06, David Sean Taylor <[EMAIL PROTECTED]> wrote:
Ethan Adams wrote:
> 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. Anyone run into this?
>
> I'm running the latest 2.1-dev
>
Thats surprising.
If you are sure its a bug, please enter it in jira.
Here is a summary of the available nav states:
Jetspeed currently provides three implementations for encoding and
storing portletwindow state and parameters:
a) fully encoded on the url (like for instance Pluto does):
use class
org.apache.jetspeed.container.state.impl.PathNavigationalState
b) only portletwindow state (window state and portlet mode) are saved in
the session, parameters are encoded on the url:
use class
org.apache.jetspeed.container.state.impl.SessionNavigationalState
c) state and parameters are saved in the session (the default):
use class
org.apache.jetspeed.container.state.impl.SessionFullNavigationalState
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
