- Every portal page must have a uniqueName defined by the administrator
Use your own uniqueName instead of the automatically generated one.
- Portal page uniqueNames will follow the java package naming conventions
For example, the uniqueName of the home page would be :
com.yash.portal.home
the uniqueName of the 'Home >About Us' page would be
com.yash.portal.home.aboutUs
the uniqueName of the 'Home > About Us > Leadership team' would be
com.yash.portal.home.aboutUs.Business Leadership
- Using this name convention, we can reserve special suffixes for particuliar processing the .hidden suffix will be used for pages that should not appear in the navigation menus. We can then code the Theme so as to filter out of the navigation menus, all pages whose uniquename ends with the .hidden suffix
- All custom coded WAR files will be prefixed by the Company Name.
For example YASH_ContentPortlet.war
This helps when updating portlet applications from the admin console, as you can quickly find the company's own portlets by using 'Title starts with' Filter
Monday, December 15, 2008
Naming convention for Websphere Portal Resources
Last week I came across an article on Websphere portal wiki which gives some idea on portal naming convention. In my past portal projects I have seen that usually project team do not give a due importance to this little thing which can be very handy. Following are the few points for your quick reference.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment