> What are the symptoms of your problems ?

The fact that I haven't learned to spell yet ;).

Seriously, I had "ref" portlet that wasn't picking up any of the parent information 
like, template, action, classname, etc.  I ends up I must have has a trailing space in 
the parent attribute.  Everything appears to be working fine now.

However, the one thing that concerns me is that when registry gets marshaled back into 
the xreg, the classname gets written to the "ref" portlet.  Where as before, it was 
not defined and was relying on the parent's classname.  The same thing was happening 
before we fixed the skin aggregation problems.  I may take a look at the code, and see 
if I can find the cause.


*===================================*
* Scott T Weaver������������������� *
* Jakarta Jetspeed Portal Project�� *
* [EMAIL PROTECTED] *
*===================================*
� 


> -----Original Message-----
> From: Luta, Raphael (VUN) [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 28, 2003 4:59 AM
> To: 'Jetspeed Developers List'
> Subject: RE: Parent information not being referenced in "ref" type portlet
> s
> 
> 
> De : Weaver, Scott [mailto:[EMAIL PROTECTED]
> >
> > Okay, I am nuts and blind.  Lot's of parent references in the
> > service, must be something else that is causing my problems.
> >
> 
> What are the symptoms of your problems ?
> 
> --
> Rapha�l Luta - [EMAIL PROTECTED]
> Jakarta Jetspeed - Enterprise Portal in Java
> http://jakarta.apache.org/jetspeed/
> 
> **********************************************
> Vivendi Universal - HTTP://www.vivendiUniversal.com:
> The information transmitted is intended only for the person or entity
> to which it is addressed and may contain confidential and/or privileged
> material of Vivendi Universal which is for the exclusive use of the
> individual designated above as the recipient. Any review, retransmission,
> dissemination or other use of, or taking of any action in reliance upon,
> this information by persons or entities other than the intended recipient
> is prohibited. If you received this in error, please contact immediately
> the sender by returning e-mail and delete the material from any computer.
> If you are not the specified recipient, you are hereby notified that all
> disclosure, reproduction, distribution or action taken on the basis of
> this
> message is prohibited.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to