WebObjects 5: WebObjects 5 Update 3 Overview

This document contains an overview and download information for Apple's Update 3 for WebObjects Release 5. This update corrects the known incompatibilities between WebObjects 5 and Mac OS X 10.1 and is required on that platform. This update should not be installed on Mac OS X versions earlier than 10.1.

The WebObjects Current Patch List, document 70037, contains information on all available patches and updates for all versions of WebObjects. Read this document if you're not sure which patches you need on your system.

 Related Documents

70037 WebObjects Current Patch List

IMPORTANT

WebObjects 5 Update 3 includes an API change which corrects an incompatibility between WebObjects 4.5(.1) and WebObjects 5. This change will also be made in future versions of WebObjects. Specifically, the return type of WORequest.formValueForKey() has been changed to Object. Due to the nature of Java, an application that uses this method which was built using a version of WebObjects 5 prior to Update 2 will generate exceptions if it is run on a system with WebObjects 5 Update 2 or later installed. These applications will need to be rebuilt with minor source code changes to run on systems with WebObjects 5 Update 2 or later installed. This change is further documented below as Apple Reference #2736189.

Language/OS Required Release Date Version Read Me Software
Any language (multicountry)
Mac OS X 10.1
Developer Update		 2001-10-22 1.0
English
Developer
Update
14.6 MB
Any language (multicountry)
Mac OS X 10.1
Deployment Update		 2001-10-22 1.0
English
Deployment
Update
10.6 MB

WebObjects 5 Update 3 for Mac OS X (Server) 10.1

Important: There are two mutually exclusive updates for this platform. If you have WebObjects 5 Developer installed on Mac OS X 10.1, you need WebObjects 5 Developer Update 3. If you have WebObjects 5 Deployment installed on Mac OS X Server 10.1, you need WebObjects 5 Deployment Update 3. You do not need both on any system.

This update includes all changes made in WebObjects 5 Updates 1 and 2. Therefore, you do not need to install either of the earlier WebObjects 5 updates before installing this one. If you already have one or both of the earlier updates installed on your system, you can install WebObjects 5 Update 3 on top of them.

This update is available through the Software Update feature of Mac OS X. If you use this method, only the proper update for the software which you have installed on your system will be visible and available for download. If you prefer to download and install the package manually, follow the instructions below.

Note: WebObjects 5 Deployment Update 3 requires Mac OS X Server 10.1 or later. WebObjects 5 Developer Update 3 requires Mac OS X 10.1 or later as well as the Mac OS X 10.1 Development Tools (Not the December 2001 Mac OS X 10.1 Developer Tools). If you have not yet updated to the correct version of Mac OS X (Server) and Tools, you must do so before installing WebObjects 5 Update 3. The Mac OS X 10.0.1 and Mac OS X 10.1 Development Tools images are still available on the Apple Developer web site.

Note: If you are creating a new Mac OS X WebObjects 5 development system, you should install the software in the following order:


If you are upgrading an existing Mac OS X 10.0.x WebObjects 5 development system, you should install the software in the following order:
Important: Whether you are using Software Update or installing the update manually, you must be logged in as "root" user in order to perform the installation. Logging in as "Administrator", or authenticating as "root" is insufficient. Failure to follow this requirement will result in an installation failure. You must also ensure that no WebObjects or EOF applications are running during the installation of the update.

Manually Installing WebObjects 5 Developer Update 3 on Mac OS X 10.1

These instructions are for manually downloading and installing WebObjects 5 Developer Update 3. If you are installing using Software Update, see the section titled "WebObjects 5 Update 3 for Mac OS X 10.1", above.

Note: This update requires Mac OS X 10.1 or later. If you have not updated to this version of Mac OS X, you must do so before installing WebObjects 5 Update 3.


Manually Installing WebObjects 5 Deployment Update 3 on Mac OS X Server 10.1

These instructions are for manually downloading and installing WebObjects 5 Deployment Update 3. If you are installing using Software Update, see the section titled "WebObjects 5 Update 3 for Mac OS X 10.1", above.

Note: This update requires Mac OS X Server 10.1 or later. If you have not updated to this version of Mac OS X Server, you must do so before installing WebObjects 5 Update 3.


Corrected in WebObjects 5 Update 3

OpenBase JDBC drivers installed in the wrong java home dir for Mac OS X 10.1

Apple Reference # 2737345

ISSUE:

Mac OS X 10.1 includes an updated Java 1.3.1 VM, which has its Java home extensions directory in a different location than the 1.3 VM included with Mac OS X 10.0.x. WebObjects applications can therefore not find the OpenBase JDBC drivers after installing WebObjects 5 on Mac OS X 10.1.

RESOLUTION:

During installation of this update, a post-install script copies the OpenBase JDBC drivers to the new 1.3.1 JVM extensions directory (/Library/Java/Extensions).

WOAssistant doesn't work on 10.1

Apple Reference # 2767516

ISSUE:

When creating a new project, the dialogs to add frameworks and models to the project did not function properly. The predefined lists could not be modified.

RESOLUTION:

The framework and model lists can now be modified as expected.

Creating Java Client application fails on 10.1

Apple Reference # 2768399

ISSUE:

Java Client projects cannot be created. The project setup fails, which appears in the GUI as though it never completes. (Project Builder does not hang.)

RESOLUTION:

This problem has been corrected.

Need updated java eopalette to work with 10.1

Apple Reference # 2779596

ISSUE:

There are incompatibilities in Interface Builder between Mac OS X 10.0.x and Mac OS X 10.1.

RESOLUTION:

The java eopalette has been upgraded to work with Interface Builder on Mac OS X 10.1.

WebObjects Builder broken after upgrading to 10.1

Apple Reference # 2780028

ISSUE:

The upgrade installer for Mac OS X 10.1 removes HTMLEditing.framework from the system. Since WebObjects Builder depends on this framework, it no longer runs. Upon launching WebObjects
Builder, you see the following error message:

dyld: /Developer/Applications/WebObjectsBuilder.app/Contents/MacOS/WebObjects Builder can't open library:

/System/Library/PrivateFrameworks/HTMLEditing.framework/Versions/A/HTMLEditing

(No such file or directory, errno = 2)

RESOLUTION:

The update installs the version of HTMLEditing.framework shipped with WebObjects 5.

Need correct version of genclasspath

Apple Reference # 2780497

ISSUE:

The version of /usr/lib/genclasspath included with the Mac OS X 10.1 Developer Tools does not work properly with WebObjects.

RESOLUTION:

The update installs the version of /usr/lib/genclasspath shipped with WebObjects 5.

Apache adaptor doesn't build on Mac OS X 10.1

Apple Reference # 2795562

ISSUE:

The Apache adaptor fails to build on Mac OS X 10.1 with an "Undefined symbols" link error. The error is related to the two level namespace changes in Mac OS X 10.1.

RESOLUTION:

Customers who need to rebuild the Apache adaptor can add the linker flag "-flat_namespace". This can be added in ProjectBuilderWO using the Build Attributes panel in the Project Inspector.

Corrected in WebObjects 5 Update 2

to-one and to-many browser icons look the same on Mac OS X

Apple Reference # 2704283

ISSUE:

It was difficult to distinguish to-one and to-many relationships in the variables browser of WebObjects Builder.

RESOLUTION:

The icons are now drawn with a more distinct appearance.

Truncated binding character does not display properly in Japanese environment

Apple Reference # 2704286

ISSUE:

Due to an incorrect setting of the system encoding, the character displayed in WebObjects Builder when a binding was too long was not the intended ellipsis, but a kanji character.

RESOLUTION:

The truncated binding character is now displayed as an ellipsis in a Japanese environment.

Adaptor XML parser can crash with bad syntax

Apple Reference # 2706425

ISSUE:

Certain textual formatting errors in the XML configuration file for the WebObjects adaptor can cause the adaptor to crash. (Note that wotaskd produces correct XML, so this only applies if a file is being used to configure the adaptor.)

RESOLUTION:

The XML parser has been modified to correctly handle the case that was causing the crash.

Error when adding a JavaClient palette element to a component

Apple Reference # 2709167

ISSUE:

Dragging a JavaClient palette element into a component results in an alert panel containing the message "This palette resource requires 'nil' which is not part of this project." The palette item does not get added to the component even after the 'Add framework' button is clicked in the alert panel.

RESOLUTION:

This problem has been corrected.

WebObjects Builder does not properly display Display Group array attributes

Apple Reference # 2717487

ISSUE:

Arrays of objects with attributes were sometimes displayed as a single object in Display Groups.

RESOLUTION:

Arrays are now handled properly in Display Groups.

WOActiveImage height and width attributes in wrong place

Apple Reference # 2718064

ISSUE:

For a WOActiveImage located outside of a form WebObjects uses the combination of an image and a hyperlink to provide the WOActiveImage functionality. Attributes of the WOActiveImage have to be set on either the image or the hyperlink. In the case of the height and width these attributes were set on the hyperlink component instead of the image, which caused sizing issues.

RESOLUTION:

Height and width are now set as image attributes.

NSArray's key value coding operators (@min, @max, etc.) don't work

Apple Reference # 2718082

ISSUE:

Using valueForKey()/valueForKeyPath() with @min or @max operators on NSArrays only worked with numbers.

RESOLUTION:

The operators were rewritten to work with more data types (numbers, timestamps, strings, and comparables where possible).

International characters are not passed correctly using WOFileUpload

Apple Reference # 2721949

ISSUE:

The form values passed as part of a mutipart/form-data form (FileUpload functionality) were not encoded properly.

RESOLUTION:

The form values passed as part of mutipart/form-data form are now encoded properly.

WOHTTPConnection returns a WOResponse with no associated real content when content-length=0

Apple Reference # 2722156

ISSUE:

WOHTTPConnection was HTTP/1.0 compliant. In HTTP/1.1, servers are allowed to skip the the content-length entry in the returned headers or even return content-length=0. These servers employ several different ways to allow the client to deduce the actual length, including chunking (Transfer-Encoding="chunked") and using the "multipart/byteranges" media type. Since WOHTTPConnection was HTTP/1.0 compliant, it couldn't figure out the actual content length and data.

RESOLUTION:

WOHTTPConnection is now HTTP/1.1 compliant. When you create a WORequest you should set the version to "HTTP/1.1".

Building frameworks for Deployment doesn't install Info.plist

Apple Reference # 2722167

ISSUE:

Building a WebObjects framework project with the Deployment build style results in a framework without a Resources/Info.plist file. This causes a null pointer exception in the app when trying to access the component in the framework.

RESOLUTION:

The Info.plist file is now correctly generated for framework projects.

Key value coding issues with booleans

Apple Reference # 2725731

ISSUE:

Some key value coding operations with boolean/Boolean methods/variables were not executed correctly and raised exceptions.

RESOLUTION:

Key value coding now properly handles boolean variables and methods..

EOModel objects not sorted correctly

Apple Reference # 2725732

ISSUE:

Most arrays of model objects (like entities, attributes, and relationships) were not sorted by name.

RESOLUTION:

Sorting has been fixed for model objects.

WODisplayGroup does not reset batch index count after fetch

Apple Reference # 2727686

ISSUE:

WODisplayGroup did not reset the batch index count after qualifying its datasource. This sometimes caused the display group to not show the fetched objects.

RESOLUTION:

The display group batch index count is now reset when the datasource is requalified.

Compiling does not re-compile changed source files

Apple Reference # 2730063

ISSUE:

Rebuilding a running application would fail to update the jar file on Mac OS X.

RESOLUTION:

Build scripts were using 'CpMac' instead of cp for certain file copies. 'CpMac' will not copy over files which are in use. The build scripts now use 'cp' instead, which does copy over files which are in use.

D2WQueryBoolean throws IllegalStateException

Apple Reference # 2730164

ISSUE:

D2WQueryBoolean is represented as a WOCheckBoxList, which was calling a deprecated API at creation time. The deprecated API then threw an exception.

RESOLUTION:

WOCheckBoxList no longer uses the deprecated API and therefore D2WQueryBoolean does not throw the IllegalStateException.

JSImageFlyover throws exception

Apple Reference # 2731214

ISSUE:

JSImageFlyover throws an exception "lookup of unknown key: 'uniqueID'" in the appendToRespose cycle.

RESOLUTION:

JSImageFlyover now works correctly.

NullPointerException in EODistributionContext

Apple Reference # 2732498

ISSUE:

EODistributionContext did not handle some notifications from other object stores well and raised NullPointerExceptions.

RESOLUTION:

The handling of notifications in EODistributionContext is now null-pointer safe.

EODatabaseContext sometimes incorrectly ignores the result of the delegate method subEntityForEntity

Apple Reference # 2735570

ISSUE:

When creating a fault for a destination entity that has subentities, EODatabaseContext sometimes ignores the result of the delegate method subEntityForEntity. This can lead to an unnecessary fetch to resolve the ambiguity about the exact entity for the fault.

RESOLUTION:

EODatabaseContext now uses the result of the delegate method subEntityForEntity to determine the final subentity for the destination object.

WORequest formValueForKey( ) should return Object, not String

Apple Reference # 2736189

ISSUE:

In some cases a form needs to return a value different than a String, e.g. in WOFileUpload. In such cases there is no way to get the proper value unless the type returned is Object.

RESOLUTION:

The return type for WORequest.formValueForKey() has been changed to Object. This change requires developers using the formValueForKey() method to modify their code. New methods have been added to allow developers to retrieve specific value types:

public String stringFormValueForKey( String aKey )

public Number numericFormValueForKey( String aKey, NSNumberFormatter numericFormatter )

public NSTimestamp dateFormValueForKey( String aKey, NSTimestampFormatter dateFormatter )

Applications which previously called formValueForKey() to retrieve a String value should be changed to call the new method stringFormValueForKey() instead.

Display Group Component lacks button icons

Apple Reference # 2745375

ISSUE:

The Display Group Assistant does not add all required graphics to the project.

RESOLUTION:

The Display Group Assistant now correctly adds all button graphics to the project.

IIS adaptor cannot upload a file larger than 64 KB

Apple Reference # 2747535

ISSUE:

Due to a problem in the native ISAPI call ReadClient, the WebObjects IIS adaptor could not upload a file larger than 64 KB.

RESOLUTION:

The IIS adaptor now works around the bug in ReadClient and can upload files larger than 64 KB.

Exception when using distributionContext binding on WOJavaClientApplet

Apple Reference # 2755813

ISSUE:

WOJavaClientApplets have a binding "distributionContext" which can be used to return a special EODistributionContext (or a subclass of it). There was a problem causing exceptions when this binding was used.

RESOLUTION:

The problem has been fixed and the distributionContext binding can now be used to create EODistributionContext instances.

Client arguments incomplete on client-side in Java Client

Apple Reference # 2765206

ISSUE:

Some arguments needed to initialize EOF completely were not sent to the client in some situations. Most applications were probably unaffected, but there might have been issues with temporary global IDs if many clients were used.

RESOLUTION:

The problem has been fixed and EOF is now completely initialized .

Launch scripts are generated badly on Windows

Apple Reference # 2769581

ISSUE:

If you build an application on Windows and transfer it to a Mac OS X system, it will not run because of the following two issues:


However, the reverse (moving an application from Mac OS X to Windows) works well.

RESOLUTION:


EOModeler gives "No Reason Provided" when reverse engineering a database

Apple Reference # 2773149

ISSUE:

There is an issue with the version of OpenBase that ships with WebObjects 5 that wasn't handled in a robust manner.

RESOLUTION:

Tables are now correctly reverse engineered from OpenBase databases. However, relationships are not reverse engineered and will need to be created in EOModeler.

Can't update Oracle LOBs

Apple Reference # 2772901

ISSUE:

Inserting an Oracle CLOB or BLOB works. However, trying to update that LOB fails with an exception "com.webobjects.jdbcadaptor.JDBCAdaptorException: Expected a LOB count of 2 but could not fetch that many objects". This is caused by an error in the generated SQL statement that attempts to update the LOB.

RESOLUTION:

The update now generates the correct SQL statement so that the Oracle LOB will be updated as expected.

Sorting: JDK compareTo() not compatible with NSComparator

Apple Reference # 2727709

ISSUE:

NSComparator expects {-1,0,1}, but the JDK compareTo() methods return different values which more loosely conform to { < 0, 0, > 0 }. Developers attempting to use compareTo() while implementing methods used by NSComparator will experience incorrectly sorted results.

RESOLUTION:

NSComparator now accepts less well defined input.

Cannot use char with OpenBase > 254 characters

Apple Reference # 2750823

ISSUE:

The meta data (type information) WebObjects uses for OpenBase is incorrect. The precision for char types has been increased to 4096 (as supported in OpenBase v6.5.7).

RESOLUTION:

WebObjects now has the OpenBase metadata in a file which is current for OpenBase v6.5.7. The file is in /System/Library/Frameworks/JDBCEOAdaptor.framework/Resources/Info-macos.plist for EOModeler and /System/Library/Frameworks/JavaJDBCAdaptor.framework/Resources/Info.plist for WebObjects applications.

Fetching OpenBase metadata (type information) hangs

Apple Reference # 2750824

ISSUE:

OpenBase expects a non-standard commit() after an invocation of getMetaData() on its JDBC Connection class. Otherwise, a transaction is left open, which can later cause a client application to hang.

RESOLUTION:

WebObjects now has the OpenBase metadata in a file which is current for OpenBase v6.5.7. The file is in /System/Library/Frameworks/JDBCEOAdaptor.framework/Resources/Info-macos.plist for EOModeler and
/System/Library/Frameworks/JavaJDBCAdaptor.framework/Resources/Info.plist for WebObjects applications.

Corrected in WebObjects 5 Update 1

WOB hangs after quitting ProjectBuilder

Apple Reference # 2695877

ISSUE:

Quitting ProjectBuilder with unsaved components open in WOB would result in WOB hanging.

RESOLUTION:

Quitting ProjectBuilder now has no effect on WOB.

WOB crashes after project manipulations in ProjectBuilder

Apple Reference #2695881

ISSUE

Under certain circumstances WOB could crash after receiving project update messages from ProjectBuilder.

RESOLUTION

This problem has been fixed.

Using lots of WOComponents from non-project frameworks like JavaWOExtensions.framework causes slow performance during rapid turnaround

Apple Reference #2695952

ISSUE:

The resource name/path caches used by rapid turnaround might be improperly invalidated in some cases, causing them to be refreshed too often. In the case of projects that use lots of reusable components, particularly those projects that link against many frameworks, these extra refreshes significantly slow performance. There is no such performance issue for deployed applications.

RESOLUTION:

Rapid turnaround performance in this configuration has been significantly improved.

Can't switch adaptor in EOModeler when the inspector window is open

Apple Reference #2700580

ISSUE:

If the inspector window has been opened, it will be impossible to switch the adaptor or set the adaptor info from the file menu. The inspector continually puts the old values back into the model.

RESOLUTION:

The connection dictionary inspector window now allows you to switch the adaptor and set adaptor info.

Dragging an Entity from EOModeler into WOB would not copy model correctly

Apple Reference #2700581

ISSUE:

Because WOB would not see the model in the project, it would attempt to add it multiple times. In certain circumstances the .eomodeld file could end up being deleted.

RESOLUTION:

WOB and ProjectBuilder now handle the .eomodeld correctly in this case.

ParseException while using EOQualifier.qualifierWithQualifierFormat()

Apple Reference # 2702519

ISSUE:

One would see an exception like:
[com.webobjects.eocontrol._private.ParseException] Encountered "and" at line 1, column 38. Was expecting: ")" .... This happened when trying to use a compound qualifier within a parenthetical expression.

RESOLUTION:

EOQualifier.qualifierWithQualifierFormat() now correctly handles this case.

Formatters were not created for Java Client detail relationship controls

Apple Reference # 2703810

ISSUE:

When the assistant on Mac OS X created a JavaClient nib, the formatter would not be applied to the detail-side controls of a master-detail relationship.

RESOLUTION:

Formatters are now created properly for master-detail relationship controls.

Prototypes do not work

Apple Reference # 2703989

ISSUE:

At runtime, a NullPointerException would be raised when a model using prototype attributes was loaded.

RESOLUTION:

Models with prototype attributes will now work as expected.

To-many relationships not displayed properly in WOB's variables browser

Apple Reference # 2704287

ISSUE:

To-many relationships in eomodels were not properly displayed as aggregate keys.

RESOLUTION:

WOB now displays these relationships accurately.

EOEditingContextDidSaveChanges notification has bad userInfo dictionary

Apple Reference # 2707102

ISSUE:

EOEditingContext mistakenly put the wrong objects in the userInfo dictionary for the notification.

RESOLUTION:

This has been corrected.

In some cases, one cannot catch an NSValidation.ValidationException

Apple Reference # 2707105

ISSUE:

In a few places within EOControl, validation exceptions were erroneously being placed within an NSForwardException instead of simply being rethrown.

RESOLUTION:

These validation exceptions are now simply rethrown.

An exception in an action causes a NullPointerException in the Exception Page display page itself.

Apple Reference # 2707125

ISSUE:

The exception display page failed to initialize its own state correctly.

RESOLUTION:

This has been corrected.

With entity inheritance, NullPointerException in EODatabaseContext.arrayFaultWithSourceGlobalID()

Apple Reference # 2708798

ISSUE:

In some situations while using entity inheritance, the EOGlobalID used for a fault would not become final when necessary, leaving it in an inconsistent state. Eventually, use of this EOGlobalID object would cause a crash.

RESOLUTION:

The EOGlobalID now becomes final appropriately.

Object graphs not kept in sync with entity inheritance in Java Client

Apple Reference # 2708954

ISSUE:

Due to a problem in the EODistribution layer, the client side of Java Client applications did not recognize inverse relationships of inherited entities correctly. As a result, methods like addObjectToBothSidesOfRelationshipWithKey were not functional on the client side.

RESOLUTION:

The EODistribution layer now correctly identifies inverse relationships even with entity inheritance.

Rapid turnaround does not work properly with frameworks

Apple Reference # 2709211

ISSUE:

WOB was not finding framework projects that were open in ProjectBuilder. This resulted in some keys and actions not showing up in the variables browser. The framework must be installed in the system and its project open in ProjectBuilder in order for WOB to find it.

RESOLUTION:

WOB now finds framework projects that are open in ProjectBuilder.

EOCustomObject does not work with deferred faulting

Apple Reference # 2709919

ISSUE:

Due to a problem in the EOAccess layer, using public accessor methods for to-one relationships (for example, public void setStudio(Studio value)) and deferred faulting (for example, subclasses of EOGenericRecord with explicit public accessors or subclasses of EOCustomObject with deferred faulting explicitly turned on) did not work and produced IllegalArgumentExceptions when objects were initialized. Also, if you have a relationship to an abstract entity, the object class representing that abstract entity in memory cannot be declared abstract (you can declare the entity abstract in the EOModel, but not the class used for that entity).

RESOLUTION:

This has been corrected, but you cannot use abstract classes for abstract entities.

EOCustomObject does not work with deferred faulting in Java Client

Apple Reference # 2709931

ISSUE:

Due to a problem in the client side EODistribution layer, using public accessor methods for to-one relationships (for example, public void setStudio(Studio value)) and deferred faulting (for example, subclasses of EOGenericRecord with explicit public accessors or subclasses of EOCustomObject with deferred faulting explicitly turned on) did not work and produced IllegalArgumentExceptions when objects were initialized. Also, if you have a relationship to an abstract entity, the object class representing that abstract entity in memory cannot be declared abstract (you can declare the entity abstract in the EOModel, but not the class used for that entity).

RESOLUTION:

This has been corrected, but you cannot use abstract classes for abstract entities.

Unable to create a WOCookie that expires when the browser window is closed

Apple Reference # 2712534

ISSUE:

The main non-deprecated WOCookie constructor (the one with six arguments) specifies timeouts, which specify values for the "max-age" header for a cookie. The "max-age" header doesn't support the old cookie feature wherein a cookie can be expired upon closing of a browser window. However, the old "expires" header does support the expire-on-browser-window-close behavior, in that a missing "expires" header indicates the behavior. Unfortunately, "max-age" supercedes the "expires" header (present or not) if the "max-age" header is present.

RESOLUTION:

In order to take advantage of the expire-on-browser-window-close feature, you must do the following. If you invoke the non-deprecated, six-argument WOCookie constructor (the one that uses an int timeout instead of an NSTimestamp date), specify a "-1" value for the timeout parameter. If you use the two-argument constructor, there's nothing more to do, because it already specifies a "-1" value for the timeout parameter. Then, as you did in previous WebObjects releases, ensure that you avoid calling setExpires on the WOCookie object you get back from the constructor, or make sure that you call "setExpires(null)" on the WOCookie object before using it. This will prevent the WOCookie object from generating either a "max-age" or an "expires" header, which will indicate the expiration behavior you desire. For example:
WOCookie cookie = new WOCookie ("cookieName", "cookieValue", "/", null, -1, false);
cookie.setExpires(null);

Client-side jars are not copied into doc root on Mac OS X Server

Apple Reference # 2719079

ISSUE:

Installing WebObjects 5 Deployment on Mac OS X Server installs the client-side jars and other files needed on the web server into a temporary directory on the system, but does not move them to the web server's doc root.

RESOLUTION:

WebObjects 5 Deployment Update 1 installs the updated client-side files that are part of the update into the temporary directory and then correctly moves all the files into the web server's doc root.

Published Date: Oct 10, 2016