|
|
The Groupware Portlets cause conflict in a portal project when also including the WLP OOTB Collaboration Portlets facets.
The Groupware Portlets do not run properly when included in a portal project that also includes the OOTB Collaboration Portlets. The OOTB Collaboration Portlets are included with WLP and provide API and Portlets facets available in Workshop for WebLogic Platform to add to your portal project. If you include these Collaboration Portlets facets and the Groupware Portlets in your project, the Groupware Portlets will be unable to connect to the groupware system (Exchange or Domino) due to a conflict of classes.
|
Repeating meetings are incorrectly created in invitee's calendars.
In the portlet, schedule a repeating meeting in user A's calendar, invite user B. Open user B's mail in the portlet. Accept the new meeting request that originated from user A's account. Open user A's calendar in the portlet for day where the new meeting is supposed to take place. Notice that the new item in user B's calendar is:
A regular appointment and is not a meeting The invitee list is not showing in this calendar item The organizer of the meeting is not listed If the meeting invitation from user A's mailbox was for an All-Day type of meeting, the meeting that is created in user B's calendar is not an All-Day type of meeting but rather a regular non-All-Day appointment
Platform: Microsoft Exchange via WebLogic Exchange Service
|
Searching in Mail Produces incorrect search result list.
Description: If a search is performed in the "Search" area of the "Mail" feature of the portlet, it is possible that not all matching mail messages will be found.
Platform: Microsoft Exchange via WebLogic Exchange Service
|
After a certain number of session creations, the service may reject requests for new sessions.
Description: In the event that such a scenario occurs, an exception such as "com.compoze.collab.StubBackendException: Could not access a particular user mailbox. The error is -2147221219 (hex=0x8004011d)".
This exception will be caught by the portlet error handling mechanism.
Platform: Microsoft Exchange via WebLogic Exchange Service
Workaround: Restart the WebLogic Exchange Service
|
After updating the portlet version, it is important to synchronize update the WebLogic Exchange Service Version.
Description: When installing a newer version of the Portlets, you might possibly upgrade the underlying WebLogic Exchange Service. It is important to be sure to also upgrade the WebLogic Exchange Service so the Portlet code is in sync with the Service code.
If the two versions do not match, update the Service to the WebLogic Exchange Service version provided with the portlet release which has just been installed into the portal application.
Platform: Microsoft Exchange via WebLogic Exchange Service
|
Secure port (HTTPS) in standalone page flows does not work
Description: Page Flows that are deployed standalone in a portal application cannot use a {url:securePort} token defined in url-template-config.xml. In this context, a `standalone' page flow means one that is deployed in a portal project, is accessed directly, but is not aggregated in a portal page. The {url:securePort} token works only when a page flow is aggregated in a portal page. A standalone page flow in a portal cannot use:
https://{url:domain}:{url:securePort}/{url:path}?{url:queryString}
url:securePort
Workaround: Hard code the ports in url-template-config.xml, instead of using the token {url:securePort}. Refer to
http://e-docs.bea.com/workshop/docs81/relnotes/relnotes.html.
|
Portlet preference being reset after server is restarted
Description: Add the following code to your netui-config.xml file:
<customization>
<enable>true</enable>
<propagate-preferences-on-deploy propagate-to-instances="false"/>
</customization>
This can also occur if the portal server is not shut down gracefully.
|
Address Book/Contacts prefix and suffix not i18n
Description: When Adding/Editing a Contact, the types and order of name titles (Mr., Mrs., etc.) and Name suffix (I, II, II etc.) are not culturally appropriate way for French, German, or Japanese. Name order is not locale-sensitive in Contacts. Address order is not locale-sensitive in the Address book. Contacts are not sorted in a culturally appropriate way for French, German, or Japanese.
|
Clicking on a page before it is fully loaded can cause an error
Description: If user clicks on a page before it has finished loading, a NullPointerException can be produced in the portlet.
Workaround: Instruct users to wait until page has fully loaded before clicking elsewhere in the portlet.
|
Using the back button in the Browser can lead to an error
Description: Clicking the "Back" button in the browser can lead to an "Action not found" error in the Groupware Portlets. The error may appear after clicking the back button. If the previous page successfully loads in the browser, links or buttons may also produce the "Action not found" error. If the action that is requested to be executed after the "Back" button was clicked existed in a parent or nested pageflow, and does not exist in the current page flow, the error will be produced.
Workaround: Use navigation controls (e,g. buttons, links) provided in the portlet to navigate through out the product. Instruct users to avoid using the browser "back" button.
|
Messages that contain BASEHREF tags in message body may cause HTML to display incorrectly
Description: Messages which contain BASEHREF tags in bodies may cause HTML to display incorrectly.
|
When multiple portlet instances are shown, switching accounts and then clicking an item in a portlet instance that has not refreshed can cause an error
Description: With separate portlets configured in mini-views, switching accounts then accessing items in other portlets can cause errors.
|
Japanese accented characters can cause an error in spell checker
Description: When a Japanese or accented character is encountered the spell check stops and the dialog displays in English "An error has occurred".
|
Some popup windows may be smaller than the information being displayed when using Netscape or Mozilla
Description: When using Netscape or Mozilla, the size of the popup may not be large enough to accommodate for the HTML that has been generated into the popup window.
|
Messages that contain long strings in the body or subject may cause the portlet page to become wide when message is read
Description: Some messages which contain very long strings in the body or subject may cause the portlet page to become very wide when the message is displayed in "Read Message" mode. For example, a long, uninterrupted string (for example, aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa) will cause the portal page to be very wide.
|
