Paul, I was more less interpreting "autocreate.portlets" as "pre-load portlets into portlet cache at startup". When I call the EntryInstantiator.process, lots of threads get created and none of the portlets load successfully. In Instantiator.java, if you uncomment line 139 (JetspeedDiskCache.getInstance().getEntry( url, true )) and comment out line 141-143, it starts working. However, this does not really load portlets but rather loads URLs for the portlets.
I think that I'll just stick to iterating thru registry entries and calling PortletFactory.getPortlet for each entry. I just need to find a place to put that code so it gets executed at startup (scheduled job?). Thanks for sharing the information on portlets caching though. This may be related to another one of my posts (http://www.mail-archive.com/[email protected]/msg02608.html) . I hope that you document your findings :) Best regards, Mark C. Orciuch Next Generation Solutions, Ltd. Voice: 219-365-0691 e-Mail: [EMAIL PROTECTED] web: http://www.ngsltd.com -----Original Message----- From: Paul Spencer [mailto:[EMAIL PROTECTED]] Sent: Friday, December 28, 2001 2:58 PM To: Jetspeed Users List Subject: Re: Automatic portlet creation Mark, Mark Orciuch wrote: > I am looking into implementing functionality to automatically preload all > portlets at portal startup. I noticed existing property > "autocreate.portlets". After examining the source code, I concluded that > this setting is not used in the context that I'm looking for. I also found What is the "context" you are "looking for"? > class org.apache.jetspeed.daemon.impl.util.feeddaemon.EntryInstantiator > which appears to be doing what I'm searching for. This class does not seem > to be invoked from anywhere and is perhaps unfinished (?). I believe this is used by "feeds" defined in JR.p > > I'm wondering if anyone is aware of the state of this class and what would > be the proper way of using it. Any suggestions on implementing portlet > preload functionality would also be welcome. Thank you in advance. > > Best regards, > > Mark C. Orciuch > I am will be working on the caching in Jetspeed. In the process of determining how the caching currently works, I found the portlets which are determined to be "local" are only in cache for 30 minutes. Remote portlets the utilize DiskCaching have their content cached in the <jetspeed_home>/WEB-INF/cache directory. Paul Spencer -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
