portals-jetspeed-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ethan Adams" <ethanjad...@gmail.com>
Subject Re: SessionNavigationalState doesn't work as it did in 2.0
Date Fri, 21 Jul 2006 12:05:17 GMT
Nevermind.  It works.  I swear I tested and checked config several times.


On 7/20/06, David Sean Taylor <david@bluesunrise.com> 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: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message