Setup Guide
|
 |
 |
|
 |
 |
This document includes known issues for WebLogic Portlets for Groupware Integration release. This document is subject to change without notice.
This is due to an issue with Page Flows, where form validation is only available (or working) in SP2.
If running in streaming mode, need BEA WebLogic Portal patch patch_CR135264.zip.
EAR fails do deploy on Windows if the application/project/domain path name is too long.
Refer to http://e-docs.bea.com/wlp/docs81/deploy/deploy.html#1003589.
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
The work around for standalone page flows in portals is to 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.
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.
Create a meeting request, enter CJK characters into the description. The invitee who receives the meeting requests sees the body as question-marks. This is due to a CDO limitation.
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.
Description: If user clicks on a page before it has finished loading, a NullPointerException can be produced in the portlet.
Workaround: Before clicking in the Groupware Portlets, wait until the page has fully loaded in the browser.
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: Wait until the Groupware Portlets have finished processing and the page has been fully loaded into the browser.
Description: Messages which contain "BASEHREF" tags in bodies may cause HTML to display incorrectly.
Description: The CompozeGroupware.portlet specifies a "refreshAction". The SP2 version of the portal has a known issue where this action may not be properly excecuted. This issue was resolved with the SP3 version of the portal. Please refer to http://e-docs.bea.com/workshop/docs81/relnotes/relnotes.html, CR174636 for more information. Patches CR129301 and CR174636 to resolve the issue, but installation of the SP3 version of the portal is highly recommended. The refresh action is triggered when the portlet reloads, and is most important if multiple instances of the portlet are deployed on the same desktop. If the refresh action is removed, and the "EDIT" mode of the portlet is enabled, and the user returns to "NORMAL" or "MAXIMIZED" mode of the portlet, the new preferences may not take because the portlet has not refreshed. As a workaround the refresh action (in bold) can be removed from the CompozeGroupware.portlet file. It is also recommended that users access the Options section of the portlet via the "Options" feature, rather than by entering the "EDIT" mode of the portlet.
Alter the following code in your CompozeGroupware.portlet file
<netuix:content>
<netuix:pageflowContent contentUri="/portlets/compoze/content/contentController.jpf" refreshAction="refreshAction"/>
</netuix:content>
<netuix:content>
<netuix:pageflowContent contentUri="/portlets/compoze/content/contentController.jpf"/>
</netuix:content>
Description: With separate portlets configured in mini-views, switching accounts then accessing items in other portlets can cause errors.
Resolution: For more information, see "Refresh Action Specified in CompozeGroupware.portlet File May Not Work on SP2" on page B-4.
Description: When a Japanese or accented character is encountered the spell check stops and the dialog displays in English "An error has occurred".
Description: When using NS7.1 and Mozilla 1.3, the size of the popup may not be large enough to accommodate for the HTML that has been generated into the popup window.
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, aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa) will cause the portal page to be very wide
|
|
|