portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ate Douma (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Commented: (JS2-742) SessionNavigationalState with merge portal parameters doesn't work
Date Mon, 02 Jul 2007 21:04:05 GMT

    [ https://issues.apache.org/jira/browse/JS2-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509668

Ate Douma commented on JS2-742:

I think I might know what your problem could be: content caching perhaps?
Changing or providing portal parameters won't trigger cache invalidation of your portlets,
I guess portal parameters cannot reliable be used together with content caching (probably
one of the main reasons why the JSR-168 doesn't support/allow this...) 

> SessionNavigationalState with merge portal parameters doesn't work
> ------------------------------------------------------------------
>                 Key: JS2-742
>                 URL: https://issues.apache.org/jira/browse/JS2-742
>             Project: Jetspeed 2
>          Issue Type: Bug
>    Affects Versions: 2.1.1
>            Reporter: Ethan Adams
>            Assignee: Ate Douma
> I lose all portlet parameters when using SessionNavigationalState with the "merge portal
parameters" feature.
> merge.portal.parameters.with.portlet.parameters=true
> merge.portal.parameters.before.portlet.parameters=true
> Works fine with SessionFullNavigationalState , except for the fact it's storing render
parameters in session.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

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

View raw message