Download Portal Manager API Programmer`s Manual
Transcript
PortalManagerAPIProgrammersManual_en.book Page 143 Wednesday, April 27, 2005 11:01 AM Notes on Programming with the Portal Manager API If the underlying metadata are changed, the content is automatically modified – in the case of a respective implementation – without any need for manual modification. As a result, these navigation elements do not get out of date when objects are deleted, copied, or moved. The Portal Manager API makes dynamic generation of navigation elements possible. For example, the subtopics of a main topic could be automatically output as subheadings in a menu, or sitemaps could give the user an overview of the structure of the website. In both cases, changes in the structure of the website are taken into account without any need to revise the navigation. When navigation elements are dynamically generated by means of the methods of the Portal Manager API, the users’ access rights can be taken into account. Users have only those navigation options for which they have the necessary rights. For example, an anonymous user sees different elements than an authorized user. More far-reaching personalization concepts would filter object information on the basis of attributes in the user profile. Design This section outlines how to design dynamic navigation elements. Proceed as follows: 1. Sketch the layout of the page and consider what HTML elements can be used to implement it. 2. On the basis of this plan, write the JSP code. Consider which parts of the HTML code must be generated dynamically and which beans provide the appropriate methods for obtaining this information. Normally, hyperlinks to WCM objects within a certain topic are offered as a table or list. The number and names of the objects are not known, i.e. the names and/or titles and the URLs of all WCM objects below the selected topic are needed. Portal Manager API – Programmer’s Manual 143