Re: behaviour: display the last visited page on folder request (PortalSiteSessionContextImpl)

[Randy Watler <wa...@wispertel.net>]

Here is one concrete example:

Say a portal site is arranged with a two tier set of folders/pages with
each tier associated with a separate rows of tabs. So, the top tabs are
associated with folders. The lower tabs, when present, are associated
with pages in the folders.

After lower tabs are used to pick a page, that page should be "sticky"
for that selected top level tab/folder. When ever the top level tab is
used to reselect the top level folder, the same lower tab/page should be
selected: not necessarily the default tab/page. The history mechanism
makes this type of tab memory work.

HTH,

Randy  

On Wed, 2006-03-22 at 19:41 +0100, Joachim Müller wrote:
> Randy, I understand what it does. But what would be a typical usecase
> where such behaviour ist desireable? Is this a common feature in other
> portal systems?
> 
> Joachim
> 
> Randy Watler wrote:
> > It is to return the user back to the same page in a folder that they
> > last visited, (obviously). This works well when the portal folders are
> > arranged topically. One can always get back to the default page via the
> > navigations that are also typically present.
> > 
> > There is another JIRA issue open on the breadcrumbs links to take them
> > back to the folder specified default page. Unfortunately, it too takes
> > the user back to the last referenced page; that certainly is unexpected
> > behavior and needs to be fixed.
> > 
> > Generally speaking, this behavior has been sought after for a long time
> > and there were JIRA issues open on it back to the early days of J2. I do
> > feel that it should be configurable though... best of both worlds!
> > 
> > Randy
> > 
> > On Wed, 2006-03-22 at 09:02 +0100, Joachim Müller wrote:
> >> Hi Randy.
> >>
> >> Just curious, what is the idea of the currently implemented behaviour?
> >>
> >> Joachim
> >>
> >> Randy Watler wrote:
> >>> Joachim,
> >>>
> >>> Obviously, this is by design. Will make this behavior optional via a
> >>> Spring configuration. 
> >>>
> >>> Please enter a JIRA issue and I'll take care of it ASAP.
> >>>
> >>> Thanks for the feedback!
> >>>
> >>> Randy 
> >>>
> >>> On Tue, 2006-03-21 at 16:10 +0100, Joachim Müller wrote:
> >>>> Hi.
> >>>>
> >>>> I've found that in PortalSiteSessionContextImpl line 431 the last
> >>>> displayed page will be used if the request point to an directory only.
> >>>>
> >>>> the following behavior exists (request => displayed page):
> >>>>
> >>>>
> >>>> 1.) portal-name/portal/ => default-page.psml
> >>>>
> >>>> 2.) portal-name/portal/mypage.psml => mypage.psml
> >>>>
> >>>> 3.) portal-name/portal/ => mypage.psml
> >>>>
> >>>> Why is that so? In my case it would make more sense to point to
> >>>> default-page.psml instead of mypage.psml in step 3.
> >>>>
> >>>> Is it possible to change this behaviour via the configuration?
> >>>>
> >>>> Thanks in advance.
> >>>>
> >>>> Joachim
> >>>>
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> >>>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
> >>>>
> >>>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> >>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
> >>>
> >>>
> >>
> > 
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> > For additional commands, e-mail: jetspeed-user-help@portals.apache.org
> > 
> > 
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org