We are working on a portlet that display's any Turbine screen. We have a
workable solution now but I have a few questions.
*) when looking at the portlets already coded as examples, many extend
AbstractPortlet, but then redefine all the methods defined for them in
AbstractPortlet exactly the same. Is this left over code not cleaned up or is
there a reason?
*) The PortletConfig data member stored in a portlet, is this the same as the
one passed to init()? Should we save this portlet config object via a call to
setPortletConfig(pc) in our implementation of the init() method? For example,
CocoonPortlet, doesn't even use the PortletConfig passed.
*) The portlet-markup in defaultPortlets.xml lets you define a url for each
portlet. A combination of classname and url are used as a key in the
PortletCache. If you don't define a url, you can only have one portlet
defined for a given class type. Is this correct behavior? Do I have to use
the url in some fashion when implementing my portlets?
*) I understand why you would have a portlet not cacheable. But if I
implement my getContent() method to by dynamic ( ie: not just returning the
contents of a data member that is filled in during the init ) I still gain the
benefit of the object existing in the cache which saves some time on object
construction, and the dynamic behavior I want. Is this the OK? It seems
confusing, but maybe that is just because of the current set of portlets I was
using as examples.
jb
Jeffrey D. Brekke
mailto:[EMAIL PROTECTED]
http://sites.netscape.net/ekkerbj/homepage
____________________________________________________________________
Get your own FREE, personal Netscape WebMail account today at
http://webmail.netscape.com.
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
