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 bu...@apache.org on 2003/11/03 17:53:15 UTC
DO NOT REPLY [Bug 21063] -
[PATCH] setAttribute does not work with no-cache option for dbpsml.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21063>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21063
[PATCH] setAttribute does not work with no-cache option for dbpsml.
------- Additional Comments From apernoud@sopragroup.com 2003-11-03 16:53 -------
Quoting Arul
----
Here is an easy way to recreate this problem: Turn off db psml caching and
start the portal engine. Minimize one of the portlets. After the page
refreshes, minimize a different portlet. When the page refreshes again, you
will see that the portlet minimized first will now be in normal state.
----
I've done that hundreds of time, and so my users may have, I dont use psml
caching, and never noticed such a bug. I've just tried to reproduce it, without
success.
If this is happening with portlets of your own, I would say that their
description (xreg file) isn't good (for example using reference to an instance,
or stuff like that).
If this is happening with standards portlets of jetspeed, they may be messed up
(I don't use them), could you tell which one are affected ?
This needs more informations, I don't think this is jetspeed related.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org