Chapter 5. CMS Portlet
Prev |  | Next

## Chapter 5. CMS Portlet

### Roy Russo

`<roy @ jboss dot org>`

## 5.1. Introduction

The CMS Portlet displays content from the file store inside a portlet window, or, in the case of binary content, outside of the portlet window altogether.

### Note

All of your content resides under JBOSS_HOME/server/standard/data/portal/. You should not modify any of the directories/files under there, as it may cause the CMS portlet to not function properly.

## 5.2. Functionalities

The CMS Portlet handles requests in the following order:

1. Request enters the CoreServlet.
2. Servlet parses request, calls for content and determines if content is text or binary.
3. If binary, serve binary content directly from the servlet level.
4. If text/html, pass request along to CMS Portlet where the content is retrieved, links are parsed and content is displayed.

The methodology of serving content outlined above, allows the CMS Portlet some beneficial features, like:

1. Search-engine friendly URLs: http://domain/files/company.html
2. No need to modify existing web page links. links to resources (images, web pages, pdfs, zips) can all be maintained as relative.
3. Serve binaries with simple urls independant of the portal: http://domain/files/products.pdf

## 5.3. Portlet Configuration

List of attributes that can be defined in the portlet.xml file:

1. `rootdir` - Directory where all publicly accessible files are available from.

Remember, the default data for your store is contained in a zip file you should have received with the portal codebase. This should all be present under: JBOSS_HOME\server\standard\data\portal\webdav\store

Prev | Up | Next
Chapter 4. Role Portlet | Home | Chapter 6. AdminCMS Portlet