portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Sean Taylor" <da...@bluesunrise.com>
Subject RE: customizer broken
Date Mon, 26 Nov 2001 16:51:12 GMT
> It relies on 2 standard registry entry:
> 
> "PortletCustomizer" should be the default portlet parameter 
> customizer.
> "PortletSetCustomizer" should be the default PSML page customizer.

If that isn't already in the documentation, then it should be.

> WHen asked to configure a portlet p (which may be a 
> PortletSet), the JetspeedTool
> applies the following algorithm:
> - does p implements PortletSet ?
>    - yes -> invoke PortletSetCustomizer
>    - no -> does p implement PortletCustomizer
>      - does p implements PortletCustomizer interface:
>        - yes -> p is its own customizer, invoke p
>        - no -> invoke PortletCustomizer
> 
> Hope this helps you understand how customization calls are routed...

Yes it does. Thanks!




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


Mime
View raw message