portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 5688] - Clicking "Close" on portlet means portlet is lost for good
Date Mon, 07 Jan 2002 14:49:46 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5688>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5688

Clicking "Close" on portlet means portlet is lost for good





------- Additional Comments From kimptoc_mail@yahoo.com  2002-01-07 06:49 -------
My refined proposed changes are:

Portlet/BasePortletSet/AbstractPortlet - add getUniqueId
[unique id could be generated internally by incrementing a static variable on 
Portlet class - only needs to be unique in the JVM, but since portlets are 
generated from Entry's it seems that the changes need to ripple down to them.  
Thus I plan to use the Turbine unique id service to get unique ids for entries]

PSMLDocument/BasePSMLDocument - add getEntryByUniqueId method

PortletFactory/PortletFactoryService/JetspeedPortletFactoryService - add 
getPortletByUniqueId method.  

Registry and related classes - add getPortletByUniqueId method.  

Close[and other relevant actions] - switch to using the 
PortletFactory.getByUniqueId methods which will then calls the 
Registry/PSMLDocument related uniqueId methods.

--
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