portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Sean Taylor (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Resolved: (JS2-943) File Portlet cleanup
Date Fri, 27 Mar 2009 23:24:50 GMT

     [ https://issues.apache.org/jira/browse/JS2-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

David Sean Taylor resolved JS2-943.

    Resolution: Fixed

Init Parameters:
 *  useLanguage : boolean, should this portlet use a language fallback algorithm, defaults
to false
 *  useFilesystem : boolean, should we look in the file system or in a webapp relative path,
defaults to false
 *  folder : string, base location of the folder to start searching in, applies to webapp
and filesystem mounts
 *  portalParam : string, the portal parameter passed in containing the name of the file (or
path) to serve up
 * Preferences:
 *   file : string, the name of the file to serve up
 *  Portal provided render attributes:
 *   file : string, the name of the file to serve up. overriding the preference

> File Portlet cleanup
> --------------------
>                 Key: JS2-943
>                 URL: https://issues.apache.org/jira/browse/JS2-943
>             Project: Jetspeed 2
>          Issue Type: Bug
>          Components: Admin Portlets
>    Affects Versions: 2.2
>            Reporter: David Sean Taylor
>            Assignee: David Sean Taylor
>             Fix For: 2.2
> The  File Portlet was long overdue for a rehaul. Now that full Portlet API 2.0 support
is in place, we can make use of 2.0 features in the implementation. Slimmed down the impl
to support the most important cases from users over time such as language support, configurable
storing of content in webapp or file system, and file server pipeline. The file server pipeline
has been decoupled from jetspeed so that a standard portlet request attribute passed on from
the portal can be used to locate a file. This is useful for file server pipelines (like in
Jetspeed) but is not limited to Jetspeed portal or coupled to Jetspeed in any way. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org

View raw message