Please pull down the latest sources from CVS and try it again. If it's still a problem, please log a Bugzilla bug. Thanks!
Best regards, Mark Orciuch - [EMAIL PROTECTED] Jakarta Jetspeed - Enterprise Portal in Java http://jakarta.apache.org/jetspeed/ > -----Original Message----- > From: Holger Dewes [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 14, 2003 3:23 AM > To: [EMAIL PROTECTED] > Subject: Problems with portlet parameter customization (bug?) > > > Hello, > > I have a problem with portlet parameter customization. When a user logs > in, and a portlet parameter is set to a value (let's call it value A) > that does not equal the standard value from the registry (let's call > that value B), and it is set to value B, then afterwards the customizer > shows not value B (the current value) but value A (the value it had when > logging in). So basically, when changing a parameter value to the > registry value, the customizer still shows the old, non-registry value. > However, in the PSML, the values are correct. > > I did some debugging, and it seems that when setting a value equal to > the registry value, it is removed from the user's PSML (this happens in > CustomizeAction.doUpdate()). However, in > CustomizeAction.buildNormalContext(), if the current value cannot be > found in the portlet instance (which is, I suppose, the value from the > user's PSML), it uses instead > Portlet.getPortletConfig().getInitParameter(). I can only guess that > that is the value as it was when the portlet was initialized, i.e. when > the user has logged in. But this does _not_ represent the current value. > > So my question really is: bug or feature? > > Cheers > -- > Holger Dewes > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
