13 Oracle Beehive Workspaces Client Notes

This module contains the following types of information on Oracle Beehive Workspaces Client:

• Known Limitations and Workarounds with the Oracle Beehive Workspaces Client

• Known Issues with the Oracle Beehive Workspaces Client

Known Limitations and Workarounds with the Oracle Beehive Workspaces Client

This section contains information on the known limitations and workarounds related to Oracle Beehive Workspaces Client, and contains the following topic:

• Oracle Beehive Workspaces Client May Not be Accessible After Restarting BEECLIENT OC4J

• Oracle Beehive Workspaces Client Does Not Allow Successive Attempts for Unresolved Document Uploads

• Oracle Beehive Does Not Propagate Meetings Scheduled by Coexisting Exchange Users Through Workspaces Client

Oracle Beehive Workspaces Client May Not be Accessible After Restarting BEECLIENT OC4J

Note:

This issue is resolved in Oracle Beehive Release 1 (1.5.1.1) and later.

Bug 8429409. After a restart of the BEECLIENT OC4J, the Oracle Beehive Workspaces Client may not be accessible. If this occurs, users who attempt to log in to the client will receive the following error message:

500 Internal Error

For administrators, the following message will appear in system log files:

workspaces-client: Servlet error java.lang.NoClassDefFoundError at oracle.ocs.wiki.beeki.beans.CoreBean.createAllWorkspacesJson

To resolve this issue, restart the BEECLIENT OC4J again.

Oracle Beehive Workspaces Client Does Not Allow Successive Attempts for Unresolved Document Uploads

Note:

This issue is resolved in Oracle Beehive Release 1 (1.5.1.3) and later.

Bug 8460651. Oracle Beehive Workspaces Client does not allow users to re-attempt document uploads when initial attempts are unresolved, that is, when the initial attempts either did not complete successfully or users did not cancel them outright. If a user re-attempts to upload a document in this situation, the following error message appears:

The upload could not complete because the destination folder is currently being updated. Please retry the operation.

If this occurs, the user should wait at least 24 hours and try again.

Oracle Beehive Does Not Propagate Meetings Scheduled by Coexisting Exchange Users Through Workspaces Client

Although coexisting Microsoft Exchange users can schedule meetings through Oracle Beehive Workspaces Client, Oracle Beehive does not propagate these meetings to the calendars of other Exchange-based workspace members. Only meetings created by users that have been migrated to Oracle Beehive Messaging are propagated to the calendars of coexisting Microsoft Exchange users.

Known Issues with the Oracle Beehive Workspaces Client

This section contains information on the known issues related to Oracle Beehive Workspaces Client, and contains the following topic:

• Oracle Beehive Workspaces Client May Display Incorrect Users Names in Deployments with Large User Bases

• Opening Wiki Pages that Contain Multiple Comments May Result in Error Messages

• Adding Files to Workspaces May Fail in High Availability Deployments if Oracle Beehive Application Tier Instances Shut Down During File Uploads

Oracle Beehive Workspaces Client May Display Incorrect Users Names in Deployments with Large User Bases

Note:

This issue is resolved in Oracle Beehive Release 1 (1.5.1.1) and later.

Bug 8393291. In deployments with large user bases (>10,000), the Oracle Beehive Workspaces Client may display incorrect user names, such as in the "You are signed in as" field and in the Participants list. It has been determined that this is a display issue only and poses no known security risks.

Opening Wiki Pages that Contain Multiple Comments May Result in Error Messages

Note:

• This issue does not affect users with the role of workspace-participant-coordinator.

• This issue is resolved in Oracle Beehive Release 1 (1.5.1.2) and later.

Bug 8403667. Attempting to open Oracle Beehive wiki pages that contain multiple comments may result in the following error message:

An error occurred. Cause: An unexpected internal error occurred. Effect: The requested operation cannot be performed Action: Contact system administrator.

Despite the error message, the content of the selected page appears. However, the comments for the page do not appear.

Adding Files to Workspaces May Fail in High Availability Deployments if Oracle Beehive Application Tier Instances Shut Down During File Uploads

Note:

This issue is resolved in Oracle Beehive Release 1 (1.5.1.2) and later.

Bug 8393033. If an Oracle Beehive Application Tier instance is shut down in a high availability (HA) deployment while a user attempts to upload a file to an Oracle Beehive workspace, the upload operation may fail. In these cases, Oracle Beehive Workspaces Client will display a message ("Uploading the document") indicating that the upload operation is proceeding, although the operation ultimately fails.