sbelt wrote:
>
> I will defer to the feedback from others, but while your waiting, I'll tell
> you the 2 options we found on our Intranet.
>
> Option-1: Add the url to JetspeedResources.properties.
> For example, to add our corporate Schedule, we added:
>
> content.feeds.escheduling.url=http://development.velosmed.com/eschedule1.2/r
> sseventstodayrequest.asp
> content.feeds.escheduling.stylesheet.url=/content/xsl/jpc-full.xsl
> content.feeds.escheduling.title=eScheduling
> content.feeds.escheduling.description=Velos eScheduling
>
> The disadvantage here is - at least in my installation - the cache is
> updated once as Jetspeed is launched.
>
The best way to do it is to create your own internal OCS feed referencing your
intrenal content. and activate the DiskCacheDaemon. The FeedDaemon will retrieve
the feed description, parse it and registers the channels in the portlet registry
(using the URL as the name of the portlet). It will also fetch the actual channels
and put them in disk cache.
The DiskCache if activated will make sure that the content files in cache are
refreshed periodically.
Only caveat, currently the ocs.xsl file used for transforming feeds -> portlet
registry elements only recognize RSS format content (by testing the ocs:format
attribute) but it's very easy to modify it to support other content semantics.
I plan to upgrade this stylesheet to support more formats over the next few
weeks.
(My internal setup currently handles 8 different internal OCS feeds)
--
Rapha�l Luta - [EMAIL PROTECTED]
--
--------------------------------------------------------------
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]
