Important: The information in this document is obsolete and should not be used for new development.
This document contains information about known issues and workarounds for WebObjects 5.3.
EOModel, at present, is not localized
Currently, you can only use Xcode’s EOModel plug-in in English.
None.
New EOModel references are not created correctly
When creating a new EOModel in Xcode 2.1, the EOModel bundle is not created and inserted correctly in the project.
Remove the EOModel reference in your project and then add it back into the project through the Xcode Project menu.
The performance on WebObjects Builder degraded significantly when it encountered certain CSS contents, complex WebObjects Component, or components with malformed HTML contents
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.
This issue has been resolved.
Direct To Web Assistant or Direct To WebServices assistant not starting correctly
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.
To correctly start the assistants:
Copy the jar files in /Library/WebObjects/lib to /Library/WebServer/Documents/WebObjects/Java
unjar them in that directory
cd /Library/WebServer/Documents/WebObjects/Java |
find . -name "*.jar" -exec jar -xf {} \; |
WebObjects building does not let you bind to @avg, @sum, @min, @max, or @count for NSArrays
In the bindings browser, you cannot bind to @avg, @sum, @min, @max or @count for NSArrays of data.
You can manually add the bindings in the source view. For instance:
movieDisplayGroup.allObjects.@count |
Exceptions when building WebObjects J2EE bundles in Xcode 2.1
You might get an exception building WebObjects J2EE bundles in Xcode 2.1 when going through the WebObjects project assistant.
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 |
Certain debug information was logged to NSLog.err instead of NSLog.debug
Information such as the URL for connecting to the WebObjects Application via WebServer went to NSLog.err instead of NSLog.debug.
This issue has been resolved.
WOMailDelivery uses obsolete sun.net.smtp.SmtpClient for mail delivery
As its original API has been deprecated, WOMailDelivery now uses the JavaMail API.
WOMailDelivery now uses JavaMail if found on the classpath. Otherwise it falls back to sun.net.smtp.SmtpClient.
WOStatistics store has a ceiling of 50 transactions that it can log
WOStatistics store has a ceiling of 50 transactions that it can log.
The WOStatisticsStoreSessionMax property can be configured in the Properties file.
WOCookies were not serializable in previous releases
WOCookies were not serializable in previous releases.
WOCookies are now serializable.
DirectToWebServices applications don't automatically open WebServicesAssistant
Launching a DirectToWebServices application would automatically open a browser window telling you to copy and paste a URL into WebServicesAssistant.
DirectToWebServices WO applications will now automatically open WebServicesAssistant directly when the WSAssistantEnabled property is enabled.
WSDL generated by WebObjects had duplicate namespaces
WSDL generated by WebObjects had duplicate namespaces and caused interop problems with other client applications.
The issue is now resolved.
WebObjects web services using Axis 1.0
WebObjects web services should upgrade to the latest GM Axis release.
Axis 1.1 is now used in WebObjects.
Creating a new instance of WebObjects Application causes JavaMonitor to throw an exception
Under certain circumstances, creating a new instance of WebObjects Application could make JavaMonitor throw a null pointer exception.
This issue has been resolved.
The Apache httpd.conf file is missing a reference to WebObjects adaptor
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 |
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 |
Third Party jars folder that was in WebObjects 5.2 is not shipped with WebObjects 5.3 release
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.
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:
Contains the Java Transaction API 1.0.1a classes (javax.transaction.*)
Contains the JDBC[tm] 2.0 extensions (javax.sql.*)
Contains the Sybase JDBC driver
The following JAR files should be placed in the WebObjects extensions directory:
Contains the Java Activation Framework 1.0.1 (javax.activation.* and com.sun.activation.*)
Contains commandline parsing utilities for AXIS (org.apache.avalon.excalibur.*)
Contains the Enterprise JavaBeans 1.1 interfaces (javax.ejb.*)
Contains the APIs for the Java Authentication and Authorization Service (JAAS) defined by Sun Microsystems
Contains the J2EE Connector Architecture classes (javax.resource.cci.* and javax.resource.spi.*)
OpenBase example databases not starting correctly
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.
To correctly start the OpenBase example databases:
Launch the OpenBase Manager application in /Applications/OpenBase
Select the menu item 'OpenBaseManager' --> 'Local Settings Settings'
Deselect the 'Network Access Allowed' checkbox
Select the Local databases
Start the WebObjects example databases
Installing Xcode 2.1 developer tools on Tiger Server changes the WebObjects deployment settings
The Xcode 2.1 tool set on Tiger Server installs developer specific settings and will therefore override some of your deployment configuration.
Remove the /System/Library/Frameworks/JavaWebObjects.framework/Resources/Properties file.
Properties file installed in /JavaWebObjects.framework/Resources on Tiger Server
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.
Remove the Properties file and you won't get the development specific settings.
Last updated: 2005-10-04
