> 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:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
