> * getAllowEdit() > * getAllowMaximize() > * isShowTitleBar() > * get/setTitle > * get/setDescription > * get/setImage > * set/getCreationTime > * supportsType
+1 > * init > > This one is trickier... but the fact is that it's misleading because > it makes the developer think that the Jetspeed portlet follows a > "servlet-like" lifecycle. The fact is that init() without caching is > worthless and init() with caching is buggy... so I'd rather remove > it currently and implement other ways to initialize efficiently > expensive resources (Portlet Tools) +1 - also, certain portlets (for example RSSPortlet) initialize their content via init() which makes it difficult to personalize > > Deprecation methodology > ----------------------- > > Since the goal of such a move would be to clean up the implementation > and get rid of unecessary or unusable features, the deprecation needs > to be fast: > > I propose that we move all the affected methods to a LegacyPortlet > interface > Have AbstractPortlet implement this interface. > Change all Jetspeed portlets extend AbstratPortletInstance which would > not extend AbstractPortlet but reimplement Portlet. +1 - I already modified a handful of portlets to extend AbstractInstancePortlet Best regards, Mark C. Orciuch Next Generation Solutions, Ltd. e-Mail: [EMAIL PROTECTED] web: http://www.ngsltd.com -- To unsubscribe, e-mail: <mailto:jetspeed-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:jetspeed-dev-help@;jakarta.apache.org>
