[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jetspeed-user
Subject:    Re: Automatic portlet creation
From:       Paul Spencer <paulsp () apache ! org>
Date:       2001-12-31 16:58:51
[Download RAW message or body]

Mark,
I had interpreted "autocreate.portlets" the same way.  As I am working 
on the portlet caching, I am refining my understanding of a "portlet" in 
different contexts.  In the context of "pre-loading" the portlet cache, 
which is what you are requesting, the Portlet is defined by the registry 
entry AND the entry in the user's PSML.  The second part makes 
pre-loading tricky when the the portlet content is affected by the user 
and the entry in the user's PSML file.  As an example, the user can 
disable the inclusion of java applets in the portlet JavaWeb by 
customizing the parameter "dont_remove_applet".  In this case their will 
be 2 portlets entries in cache, one with the default value of 
"dont_remove_applet" and the second with the user's update value of 
"dont_remove_applet".

A enhancement would be to add a "_preload_default_content".  Thus if a 
user altered the default portlet configuration, their portlet would NOT 
be pre-loaded.  Portlets that generate user specific content would NOT 
be per-loadable.  If this is a usable enhancement, please add to to 
Bugzilla, http://nagoya.apache.org/bugzilla/.

Paul Spencer

Mark Orciuch wrote:

> 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/jetspeed-user@jakarta.apache.org/msg02608.html)
> . I hope that you document your findings :)
> 
> Best regards,
> 
> Mark C. Orciuch
> Next Generation Solutions, Ltd.
> Voice: 219-365-0691
> e-Mail: mark_orciuch@ngsltd.com
> web: http://www.ngsltd.com
> 
> 
> -----Original Message-----
> From: Paul Spencer [mailto:paulsp@apache.org]
> 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:jetspeed-user-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
> <mailto:jetspeed-user-help@jakarta.apache.org>
> 
> 
> --
> To unsubscribe, e-mail:   <mailto:jetspeed-user-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:jetspeed-user-help@jakarta.apache.org>
> 
> 



--
To unsubscribe, e-mail:   <mailto:jetspeed-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:jetspeed-user-help@jakarta.apache.org>

[prev in list] [next in list] [prev in thread] [next in thread]