portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raphaƫl Luta <raphael.l...@networks.groupvu.com>
Subject Re: [Bug 5688] - Clicking "Close" on portlet means portlet is lost for good
Date Fri, 11 Jan 2002 08:21:33 GMT
Chris Kimpton wrote:

> Hi,
> I am getting some wierd behaviour with this...
> I have added some debug info the jetspeed.vm control to print out the
> portlet position and its parents names and descriptions.
> When running on linux (build 1.3.0, J2RE 1.3.0 IBM build
> cx130-20010626 (JIT enabled: jitc)) and windows (1.3.1_01) with
> jdk1.3, the parent information seems to be wrong, eg on the home page
> - there are 2 "Jetspeed" portlets, one on the "Home Page" tab and one
> on the "Dynamic" tab.
> Both of these are reporting the "Dynamic" tab as the parent to
> themselves...
> To debug this, I loaded jetspeed and tomcat 3.3m4 (which I was using
> above) into visual age - but then it worked!
> I guess its probably some obscure bug in the jdk or jetspeed - anyone
> seen anything like this before?

Hmmm... weird :/

Do you have portlet caching activated ? If yes, then there's probably a

non thread-safe operation in this code that may generate such behavior; if
you don't use the cache then I'm not sure what may cause this since portlets
are always instanciated...

In your debug output, can you check if the 2 portlets are the same or if they
are 2 different instances ?

Raphael Luta - raphael.luta@networks.groupvu.com
Professional Services Manager
Vivendi Universal Networks - Paris

To unsubscribe, e-mail:   <mailto:jetspeed-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:jetspeed-dev-help@jakarta.apache.org>

View raw message