> This is a has been around for a while, nothing new :( Well maybe so, but its new to me, and its easily fixed with a simple check for null.
Regardless checking for null obviously didn't fix the customizer, nor the root of the problem: why is there a portlet named 'PortletSetCustomizer' being passed to the PersistenceService (3 times for the Turbine psml) during customization, and why is it not found in the portlet set? > -----Original Message----- > From: Paul Spencer [mailto:[EMAIL PROTECTED]] > Sent: Saturday, November 24, 2001 6:19 PM > To: Jetspeed Developers List > Subject: Re: customizer broken > > > [Sat Nov 24 12:17:39 PST 2001] -- DEBUG -- Exception while retrieving > attribute _display for portlet PortletSetCustomizer > Exception: java.lang.NullPointerException > Stack Trace follows: > java.lang.NullPointerException > at > org.apache.jetspeed.portal.portlets.AbstractPortlet.getAttribu > te(AbstractPor > > This is a has been around for a while, nothing new :( > > Paul Spencer > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
