|
|
This section describes the Customization features associated with the Groupware Portlets. The look and feel of the Groupware Portlets can be customized by modifying the Cascading Style Sheet (CSS) Class properties. The behavior of the Groupware Portlets can be customized by modifying the Groupware Listener classes.
The Groupware Portlets reference custom CSS class names that are located in a file named groupware.css. Different versions of this file can exist for each skin in the Portal. Display aspects such as the font, background color, and text position can be easily modified by changing the properties inside the CSS class definitions. The groupware.css file is organized into eight logical groups:
From the Merged Project view in Workshop for WebLogic, the Listener classes are located in the WEB-INF/src/portlets/compoze/groupware/c13n/ directory. A default implementation exists for each Listener class. By modifying these classes, or creating your own implementation, you can change the following:
The AccountListener interface represents an interface for receiving account events. The DefaultAccountListener class represents a default implementation of the AccountListener interface. The DefaultAccountListener uses Oracle’s User Profile capabilities to retrieve and store provider account information. This class can be extended to:
To configure the portlets to use the subclass of the DefaultAccountListener which you have created, alter the DefaultAccountListener.getAccountListener(…) method to return a new instance of your custom AccountListener. Multiple implementations of the AccountListener interface ship with the product to aid you in the creation of your own custom AccountListener implementation.
Use this account listener for connecting to Microsoft Exchange via the WebLogic Exchange Service. See
Chapter 3, “Microsoft Exchange Connectivity.”
|
|
Use this account listener for connecting to Microsoft Exchange via the WebDAV. See
Chapter 3, “Microsoft Exchange Connectivity.”
|
|
Use this account listener for connecting to Lotus Domino via the WebLogic Domino Service. See
Chapter 4, “Lotus Domino Connectivity.”
|
|
Use this account listener for connecting to Microsoft Exchange via the WebLogic Exchange Service. See
Chapter 3, “Microsoft Exchange Connectivity.”This account listener leverages the Oracle login information (username and password) when attempting to connect to the WebLogic Exchange Service.
|
|
Use this account listener for connecting to Microsoft Exchange via the WebDAV. See
Chapter 3, “Microsoft Exchange Connectivity.” This account listener leverages the Oracle login information (username and password) when attempting to connect to Microsoft Exchange.
|
|
Use this account listener for connecting to Microsoft Exchange via the WebDAV using Forms-Based authentication. See
Chapter 3, “Microsoft Exchange Connectivity.”
|
|
Use this account listener for connecting to Lotus Domino via the WebLogic Domino Service. See
Chapter 4, “Lotus Domino Connectivity.” This account listener leverages the Oracle login information (username and password) when attempting to connect to the WebLogic Domino Service.
|
The LogListener interface represents an interface for receiving log events. The DefaultLogListener class represents a default implementation of the LogListener interface. The DefaultLogListener currently does nothing so the log information is sent to the logging mechanism set for the Oracle Portal. This messageReceived() method of this class can be altered to (for example):
The portlet logging mechanism is sensitive to the logging level configured on the host WebLogic Portal. Debug and other messages can be output to the logging targets by altering the Logging Severity Threshold on the server to “INFO”.
The ViewListener interface represents an interface for receiving view events. The DefaultViewListener class represents a default implementation of the ViewListener interface. The DefaultViewListener maximizes every view except those originating from the Home feature. By modifying this file, the Groupware Portlets can be displayed in the Normal mode, Maximized mode, or any combination of the two.
The LocaleUtility class is located under the WEB-INF/src/portlets/compoze/groupware/c13n/ directory. The default list of locals can be modified by altering the list of available locales in the s_supportedLocales. If additional locales are added, be sure to add properties files which correspond to the list of new locales which will be available in the portlet. The list of properties files which should be created is: portlets/compoze/content/groupware_resources_JAVA_LOCALE.properties
| Note: | If you encounter exceptions that include the following text, the properties files you have created are missing properties and should be altered to contain all properties that the default and unmodified groupware_resources.properties file contains. |
|