Okay, if I retrieve the entry using the registry, the image shows up, so everything is mapped correctly in Castor. I think the JetspeedPortletInstance may be the root of the problem.
-scott > -----Original Message----- > From: Weaver, Scott [mailto:[EMAIL PROTECTED]] > Sent: Friday, September 27, 2002 10:51 AM > To: 'Jetspeed Developers List' > Subject: Image in meta-info is not being being added the BaseMetaInfo obje > ct > > Anybody notice images are being ignored when the registry is loaded? I > always end up getting "images/dot.gif" which seems to be supplied as > default from o.a.j.util.MetaData object. > > This is an example of <meta-info> in one of my registry entries > ... > <meta-info> > <title>LANSA Portlet Manager</title> > <description>Portlet for managing LANSA for the Web > portlets</description> > <image>images/rk/lansa/lanlogo.gif</image> > </meta-info> > ... > > After some preliminary debugging, I still cannot figure out why this is > happening. It is somewhat baffling since the registry.xml has a binding > for <image> correctly defined in the BaseMetaInfo mapping. I may need to > debug when Jetspeed unmarshals the registry files for the first time. It > might be a Castor issue. > > Anyone have any clues on this one? > > Scott
