Simple Content Management Portlet Configuration

Portlet Quickstart

1. Check out the Simple Content Portlet from Jasig Subversion:

$ svn co https://www.ja-sig.org/svn/sandbox/SimpleContentPortlet/trunk SimpleContentPortlet

2. Build the portlet using maven.

$ cd SimpleContentPortlet
$ mvn clean install

3. Deploy the resulting war file using your portal's deployment process.

In uPortal, this step involves calling the portal's deployPortletApp ant task from the command line. From uPortal's top-level directory:

$ ant deployPortletApp -DportletApp=/path/to/SimpleContentPortlet/target/SimpleContentPortlet.war

Configuration Options

jQuery noConflict Behavior

uPortal 3.1+ requires that a portlet import all of the JavaScript libraries it requires, then delete related publicly visible variables. By default, the Simple Content Portlet follows this model.

To use the portlet in an environment which already includes the jQuery library and does not delete it from the public scope, set the portlet preference "includeJQuery" to "false".

HTML Validation and Security

The Simple Content Management portlet uses OWASP's AntiSamy tool to validate and sanitize HTML input. By default, the portlet ships with a configuration that prevents users from entering JavaScript or other potentially dangerous code.

You may modify this default behavior by editing or creating a new policy file. AntiSamy's configuration options are documented in the following locations:

• Choosing a base policy file
• Tailoring the policy file