Resolved and Known Issues in WebObjects 5.3

This document contains information about known issues and workarounds for WebObjects 5.3.

EOModel

Radar #4108187

EOModel, at present, is not localized

Description:

Currently, you can only use Xcode’s EOModel plug-in in English.

Resolution:

None.

Radar #4112167

New EOModel references are not created correctly

Description:

When creating a new EOModel in Xcode 2.1, the EOModel bundle is not created and inserted correctly in the project.

Workaround:

Remove the EOModel reference in your project and then add it back into the project through the Xcode Project menu.

Tools

Radar #3516904

The performance on WebObjects Builder degraded significantly when it encountered certain CSS contents, complex WebObjects Component, or components with malformed HTML contents

Description:

Certain CSS contents, complex WebObjects Components, or components with malformed HTML contents could bring WebObjects Builder into a panic state, which led to a spinning wheel and a major performance hit.

Resolution:

This issue has been resolved.

Radar #4117166

Direct To Web Assistant or Direct To WebServices assistant not starting correctly

Description:

In the run log, you'll see error messages complaining about missing classes. This is because the WebObjects webserver document root is not populated correctly.

Workaround:

To correctly start the assistants:

  1. Copy the jar files in /Library/WebObjects/lib to /Library/WebServer/Documents/WebObjects/Java

  2. unjar them in that directory

cd /Library/WebServer/Documents/WebObjects/Java
find . -name "*.jar" -exec jar -xf {} \;

Radar #4123573

WebObjects building does not let you bind to @avg, @sum, @min, @max, or @count for NSArrays

Description:

In the bindings browser, you cannot bind to @avg, @sum, @min, @max or @count for NSArrays of data.

Workaround:

You can manually add the bindings in the source view. For instance:

movieDisplayGroup.allObjects.@count

Frameworks

Radar #4117882

Exceptions when building WebObjects J2EE bundles in Xcode 2.1

Description:

You might get an exception building WebObjects J2EE bundles in Xcode 2.1 when going through the WebObjects project assistant.

Workaround:

Manually add the settings in your project target:

SERVLET_SINGLE_DIR_DEPLOY = YES/NO if single servlet directory option
SERVLET_TRUE_WAR = YES/NO if true war bundle option
SERVLET_WEBAPPS_DIR = [path to container deployment directory
SERVLET_COPY_JARS = YES/NO is YES only if you want the jars under  one directory,  not need for war bundle option
SERVLET_DEPLOY_LICENSE= WebObjects deployment license

Radar #3748926

Certain debug information was logged to NSLog.err instead of NSLog.debug

Description:

Information such as the URL for connecting to the WebObjects Application via WebServer went to NSLog.err instead of NSLog.debug.

Resolution:

This issue has been resolved.

Radar #2850117

WOMailDelivery uses obsolete sun.net.smtp.SmtpClient for mail delivery

Description:

As its original API has been deprecated, WOMailDelivery now uses the JavaMail API.

Resolution:

WOMailDelivery now uses JavaMail if found on the classpath. Otherwise it falls back to sun.net.smtp.SmtpClient.

Radar #3590569

WOStatistics store has a ceiling of 50 transactions that it can log

Description:

WOStatistics store has a ceiling of 50 transactions that it can log.

Resolution:

The WOStatisticsStoreSessionMax property can be configured in the Properties file.

Radar #3888799

WOCookies were not serializable in previous releases

Description:

WOCookies were not serializable in previous releases.

Resolution:

WOCookies are now serializable.

Radar #3055679

DirectToWebServices applications don't automatically open WebServicesAssistant

Description:

Launching a DirectToWebServices application would automatically open a browser window telling you to copy and paste a URL into WebServicesAssistant.

Resolution:

DirectToWebServices WO applications will now automatically open WebServicesAssistant directly when the WSAssistantEnabled property is enabled.

Radar #3961655

WSDL generated by WebObjects had duplicate namespaces

Description:

WSDL generated by WebObjects had duplicate namespaces and caused interop problems with other client applications.

Resolution:

The issue is now resolved.

Radar #3989185

WebObjects web services using Axis 1.0

Description:

WebObjects web services should upgrade to the latest GM Axis release.

Resolution:

Axis 1.1 is now used in WebObjects.

Deployment

Radar #3935864

Creating a new instance of WebObjects Application causes JavaMonitor to throw an exception

Description:

Under certain circumstances, creating a new instance of WebObjects Application could make JavaMonitor throw a null pointer exception.

Resolution:

This issue has been resolved.

Radar #4129134

The Apache httpd.conf file is missing a reference to WebObjects adaptor

Description:

The Apache httpd.conf file is missing a reference to WebObjects adaptor. Check the /etc/httpd/httpd.conf file and look for the line:

Include /System/Library/WebObjects/Adaptors/Apache/apache.conf
Workaround:

Add the lines below to your /etc/httpd/httpd.conf file and restart your web server.

# Including WebObjects Configs
Include /System/Library/WebObjects/Adaptors/Apache/apache.conf

WebObjects Documentation

Radar #4101257

Third Party jars folder that was in WebObjects 5.2 is not shipped with WebObjects 5.3 release

Description:

In previous releases of WebObjects, there was a 3rd party jars folder that contained various java components that could be used with WebObjects. We are not shipping these jars with the WebObjects 5.3 release.

Resolution:

Customers will have to download versions of these jars if they want to use the functionality.

The following can be placed in the /Library/Java/Extensions directory:

jta_1.0.1.jar

Contains the Java Transaction API 1.0.1a classes (javax.transaction.*)

jdbc2_0-stdext.jar

Contains the JDBC[tm] 2.0 extensions (javax.sql.*)

jconn2.jar

Contains the Sybase JDBC driver

The following JAR files should be placed in the WebObjects extensions directory:

activation.jar

Contains the Java Activation Framework 1.0.1 (javax.activation.* and com.sun.activation.*)

clutil.jar

Contains commandline parsing utilities for AXIS (org.apache.avalon.excalibur.*)

ejb-1.0.jar

Contains the Enterprise JavaBeans 1.1 interfaces (javax.ejb.*)

jaas_1.0.jar

Contains the APIs for the Java Authentication and Authorization Service (JAAS) defined by Sun Microsystems

jca_1.0.jar

Contains the J2EE Connector Architecture classes (javax.resource.cci.* and javax.resource.spi.*)

Installer

Radar #4101546

OpenBase example databases not starting correctly

Description:

The OpenBase WebObjects databases might not start correctly in some installs. This will manifest itself in WebObjects example applications not being able to connect to the database.

Workaround:

To correctly start the OpenBase example databases:

  1. Launch the OpenBase Manager application in /Applications/OpenBase

  2. Select the menu item 'OpenBaseManager' --&gt 'Local Settings Settings'

  3. Deselect the 'Network Access Allowed' checkbox

  4. Select the Local databases

  5. Start the WebObjects example databases

Radar #4128791

Installing Xcode 2.1 developer tools on Tiger Server changes the WebObjects deployment settings

Description:

The Xcode 2.1 tool set on Tiger Server installs developer specific settings and will therefore override some of your deployment configuration.

Workaround:

Remove the /System/Library/Frameworks/JavaWebObjects.framework/Resources/Properties file.

Radar #4128807

Properties file installed in /JavaWebObjects.framework/Resources on Tiger Server

Description:

The Properties file is likely coming from the WebObjectsRuntime.pkg and should not be installed on Tiger Server systems but should be installed on Tiger Client systems.

Workaround:

Remove the Properties file and you won't get the development specific settings.