Portal URLs are often very complicated; however, it is possible to setup entry points in portals that follow simple patterns.

Each portal container can contain multiple portals. Within a given portal, windows are organized into pages, with a page being a collection of windows associated to a name:

Before reading the following sections, be familiar with how to define pages and portal. Refer to Section 6.4.1, “Defining a new Portal Page” for details.

The default portal is used when no portal is specified. How selection is done:

Each portal can have multiple pages, with each portal having a default page. When a portal is selected, a page must be used, and all windows in that page are rendered. The page selection mechanism is as follows:

/portal/default/page-name renders the page-name page.

The CMSPortlet delivers content transparently, without modifying the displayed URL. It is desirable to display binary content, such as GIF, JPEG, PDF, ZIP, and so on, outside of the confines of the portal. For example, /content/default/images/jboss_logo.gif displays the jboss_logo.gif file outside of the portal.

To display content outside of the portal, the portal interprets any path beginning with /content as a request for CMS content. As long as the <mime-type> is not text/html, or text/text, and the path to the content begins with /content, the content is rendered independently, outside of the portal.