Fixed Bugs

This section lists the bugs fixed in Web Space Server 10.0 SP1.

Need to sync with Liferay 5.2.1 (Bug ID: 6810345)

Description:

Need to synchronize with version 25766 of Liferay 5.2.x branch, which corresponds to Liferay 5.2.1.

Solution:

After applying the SP1 patch, the version file under <webspace_install_dir>\var\webspace shows:

Version=10.0

Build=1.14

Revisions=1357-25766-26479

Tunnel-Web authentication of users do not work when Web Space Server is configured with OpenSSO (Bug ID: 6778779)

Description:

Anything that uses tunnel-web user authentication does not work when Web Space Server is configured to use OpenSSO. For example, when OpenSSO is installed, users cannot load/store documents using the OpenOffice plugin.

Solution:

After applying the SP1 patch, perform the following steps to verify tunnel-web authentication:

1. Access http://<machine-name>:8080/tunnel-web/secure/axis

2. Provide the user name and password set using OpenSSO.

3. You can verify the web services after successful authentication.

On adding a workflow definition file, you can view it only when you click the “Search Definition” button (Bug ID: 6798724)

Description:

When a workflow definition file is added using the Workflow portlet, the file gets added, but the portlet does not display it by default, and the user must click the Search Definition button to view the workflow definition file.

Solution:

On applying the SP1 patch, the Workflow portlet displays all the workflow definition files which are configured for display. The issue got resolved when new Portlet Container jars were added to fix CR 6808979.

Incorrect logging during event propagation (Bug ID: 6799513)

Description:

Two portlets communicating with each other results in event generation. Consider a scenario involving two portlets, P1 and P2:

1. P1 sends an event to P2.

2. P2 process the event, and sends an event back to P1 in the event processing phase of P2.

After the event propagation from P1->P2 and P2->P1, the log states “Maximum event generation: 3 reached. No more events will be sent.”

Solution:

Apply the SP1 patch to address the issue of incorrect logging during event propagation. The issue got resolved when new Portlet Container jars were added to fix CR 6808979.

Multi-Lingual Version of GlassFish V2 needs to be shipped (Bug ID: 6798987)

Description:

The multilingual version of GlassFish v2 needs to be bundled along with Web Space Server to allow localized customers to use the Admin console and other features of GlassFish in their language.

Solution:

Web Space Server evaluation bundles that include GlassFish are not supported. You can install core Web Space Server on a multilingual version of GlassFish v2.

Web-form portlet does not work on Sun Portlet Container (Bug ID: 6808979)

Description:

When you build and deploy web-form-portlet on Liferay with Sun Portlet Container, it throws an exception.

Solution:

Apply the SP1 patch. The fix in Liferay is accepted and ported to Liferay 5.2.x branch, and synchronized with Web Space Server.

A guest user can view the portlets on the public page of another user, even when the guest user has no view permissions for the same (Bug ID: 6808452)

Description:

A guest user (an user who do not have a login account) can view the portlets on the public page of another user, even when the guest user has no view permissions for the same.

Solution:

Apply SP1 patch. The issue is fixed in Liferay, and ported to Web Space Server.

Core installer doesn't take Oracle hostname, port and database name inputs (Bug ID: 6808623)

Description:

When Web Space Server is installed on Oracle 10g, the database host, database port, and database names are hard-coded. Users will not have the flexibility of choosing a host name, port number, and database names.

Solution:

Apply the SP1 patch on a Web Space Server instance installed on Oracle 10g.

OpenSSO add-on install-gfv2.xml will create duplicate web.xml entries if template files are not renamed (Bug ID: 6812514)

Description:

The OpenSSO Add-On should be installed only after renaming *.template to *.properties files (Example, AMConfig.properties.template -> AMConfig.properties), and ensuring the AMConfig.properties and portal-ext.properties files are present.

Solution:

You can install the OpenSSO Add-On without this additional step after installing the SP1 patch.

HSQL data goes into domain/config directory (Bug ID: 6805773)

Description:

If var/webspace/data is the directory for all data, then the HSQL data should also go there for consistency.

Solution:

After applying the SP1 patch, HSQL data goes into the var/webspace/data/hsql directory.

bin/pkg bootstrap wrapper missing from install bundle (Bug ID: 6803670)

Description:

The Web Space Server 10.0 download bundle for MacOS that includes GlassFish v2.1 does not include the "bin/pkg" wrapper script. This wrapper script is useful because it enables the CLI (Command Line Interface) to easily bootstrap the pkg(5) client environment without also downloading the Update Tool GUI and its dependencies.

Solution:

Apply the SP1 patch.

OpenSSO exceptions are raised on every login after installing the OpenSSO add-on (Bug ID: 6812509)

Description:

After installing the OpenSSO Add-On, OpenSSO exceptions are encountered at every login.

Solution:

Install the add-on after installing the SP1 patch.

Scripts fail badly when Ant 1.6.5 (default Ant version for GlassFish) is used (Bug ID: 6812482)

Description:

Scripts fail badly when using an Ant version prior to 1.7.0. Users need to be reminded that the ANT_HOME environment variable must be set to the location of Ant 1.7.0 or higher version. If this variable is not explicitly set, the scripts will use the older, incompatible version of Ant included by default with GlassFish.

Solution:

After applying the SP1 patch, an error message is shown if the available Ant version is less than 1.7.0.