We have a variety of methods to refresh portlet's content after customizing. Currently, CustomizeAction invokes the customized portlet's init() method to refresh the portlet's content. This seems to work for some portlets, notably the ones which generate their content during init() (RSSPortlet, for example). Portlets which implement their own customizer (for example, HelloVelocity or DatabaseBrowserTest) have the "luxury" of knowing when they were customized. What about portlets which use the default customizer, cache their content and only want to be refreshed when their settings change?
I am trying to come up with a standard approach for notifying a portlet that its settings have changed. One simple approach that comes to mind is to set a special portlet attribute "settings-changed" which would be set in the CustomizeAction. Also, in the proposed new Portlet API, there's mention of the message events which would apply here nicely. I am open to any other suggestions. Thanks in advance for your comments and ideas. Best regards, Mark C. Orciuch Next Generation Solutions, Ltd. e-Mail: [EMAIL PROTECTED] web: http://www.ngsltd.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>