[ start | index | login ]
start > Development > Java & J2EE > Websphere > Portal > Layout of the portal page

Layout of the portal page

Created by mpecher. Last edited by mpecher, 5 years and 282 days ago. Viewed 1,130 times. #1
[edit] [rdf]
labels
attachments

Layout of the portal page

The portal page is composed of JSPs and statically included JSP fragments (JSPFs) for screens, themes, and skins that are typically created by the Web designer of the portal. These JSPs reside in the corresponding /screens, /themes, /skins directories under :
was_profile_root/installedApps/cellname/wps.ear/wps.war

Within this location, subdirectories for markup, locale, and client types are used to support portal aggregation.

themes

provide the navigation, appearance, and layout of the portal, including colors, fonts, and images outside of the portlet content area (Home screen). screens the area of the portal that typically displays portlets (Home screen), but can also display other content in its place, for example, a login form or error message. Screens are selected from navigation icons in the theme.

skins

represent the border rendering around components, such as row containers, column containers, or portlets. Skins are installed independently from themes. However, the administrator can set a default skin for a theme.

Default.jsp

The starting place for building the portal page is Default.jsp in the /themes directory. The screen and skin are called by the corresponding <portal-core:screenRender/> and <portal-core:pageRender/> tags from the portal-core tag library. The following example is shown to illustrate the underlying code in themes, screens, and skins as they are used in the portal. The code example is followed by an illustration of how this code would render in the portal.
no comments | post comment

Menu:
Java & J2EE
Development
Books

Help:
Help FAQ
Formatting


< May 2012 >
SunMonTueWedThuFriSat
12345
6789101112
13141516171819
20212223242526
2728293031


Logged in Users: (0)
… and a Guest.



Disclaimer: Views and opinions are that of the individual author, and not that of Marand Custom Solutions. This site is an open forum for technical content, and the company accepts no liability for any content or view expressed.