Sun Java System Application Server Platform Edition 8 2004Q4 Beta Release Notes
Part Number 819-0072
The Sun Java System Application Server Platform Edition 8 2004Q4 Beta product is a J2EE 1.4 platform compatible server for the development and deploymentof J2EE applications and Java Web Services. Productioin use of this server is free of charge.
These release notes contain important information available at the time of the Sun Java System Application Server 8 2004Q4 Beta product release. Product requirements, what’s new, known problems, and other late-breaking issues are addressed here. Read this document before you begin using the Application Server product.
This document contains the following sections:
Third-party URLs are referenced in this document and provide additional, related information.
|
Note
|
Sun is not responsible for the availability of third-party Web sites mentioned in this document. Sun does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources. Sun will not be responsible or liable for any actual or alleged damage or loss caused by or in connection with the use of or reliance on any such content, goods, or services that are available on or through such sites or resources.
|
|
Release Notes Revision History
This section lists the changes that have been made in these release notes after the initial release of the Application Server Platform Edition 8 2004Q4 Beta product
Revision Date
|
Description of Change
|
September 2004
|
Sun Java System Application Server Platform Edition 8 2004Q4 Beta release.
|
.
About Application Server Platform Edition 8 2004Q4 Beta
The Sun Java System Application Server Platform Edition 8 2004Q4 Beta is a J2EE 1.4 platform compatible server for the development and deployment of J2EE applications and Java Web Services. The Application Server includes the following enhancements:
- J2EE 1.4 Platform Support: This release implements all of the specifications covered by the J2EE 1.4 platform.
- JavaServer Faces 1.1 Support: All levels of developers can quickly build web applications by: assembling reusable UI components in a page; connecting these components to an application data source; and wiring client-generated events to server-side event handlers.
- JavaServer Pages Standard Tag Library 1.1 Support: The Application Server supports the JavaServer Pages Standard Tag Library (JSTL) 1.1, which encapsulates core functionality common to many JSP applications.
- Administrative Tools: The Application Server includes a command-line tool and a browser-based Administration Console interface.
- High Performance Message Delivery: The Application supports concurrent message delivery with the Sun Java System Message Queue software.
- Developer Tool Integration: The Application Server supports the NetBeans IDE and Sun Java Studio Creator.
What’s New in This Release
The Sun Java System Application Server Platform Edition 8 2004Q4 Beta implements the new features specified by the J2EE 1.4 platform:
- Admin Console GUI Enhancements: The Admin Console’s new capabilities include an improved log viewer, a JNDI namespace browser, and a GUI for monitoring.
- Web Services Security: These container message security mechanisms implement message-level authentication (e.g. XML digital signature and encryption) of SOAP web services invocations using the X509 and username/password profiles of the OASIS WS-Security standard.
- WS-I Profile 1.1: This release implementsWeb Services Interoperability (WS-I) Basic Profile 1.1 to enable interoperability for web services applications.
- Migration Tool: The migration tool helps in moving applications running on other application servers such as JBoss, WebLogic and Websphere to this release of the Sun Java System Application Server.
JavaServer Pages Standard Tag Library 1.1 Support
The Sun Java System Application Server Platform Edition 8 2004Q4 Beta supports the JavaServer Pages Standard Tag Library (JSTL) 1.1.1 that uses internally named com.sun.* JAXP classes. The following issues have been resolved in the JSTL 1.1.1 release used with the Application Server:
Table 1 Bugs fixed since Standard 1.1.1 Taglib release
Bug ID
|
Summary
|
30646
|
Fixed implementation so that it compiles under J2SE 5.0. Changed the J2SE 5.0 reserved keyword "enum" to "enum_".
NOTE: the JAXP 1.2 classes will need to be specified with J2SE 5.0 since the 5.0 bundled JAXP 1.3 packages have been moved around and re-named.
|
30647
|
Followed the BluePrints Guidelines for web application project structure. Most IDEs assume the BluePrints structure so abiding by these guidelines will help them integrate the examples.
The following changes were made to the examples directory structure:
- moved the examples deployment descriptor to the web/WEB-INF directory out from conf
- moved the jstl-examples.tld to web/WEB-INF/tlds
- updated build.xml to reflect new directory structure
|
None
|
Sun Java System Application Server 8 2004Q4 Beta contains an implementation of JSTL 1.1.1 that uses the internally named com.sun.* JAXP classes. If you use another JSTL implementation, for instance from Apache, with J2SE 5.0 you will need to include a JAXP implementation with your web application.
- In JstlUriResolver when external entitities are resolved the ‘base’ varies from different Xalan implementations. Fixed how base is handled.
|
The JSTL 1.1 Specification is available at http://java.sun.com/products/jstl
Java API for XML Processing
The Sun Java System Application Server Platform Edition 8 2004Q4 Beta includes the Java API for XML Processing (JAXP) 1.2.6_01 which supports the JAXP 1.2 API. The default transformer is XSLTC.
- The Xerxes and Xalan packages have been renamed from org.apache.subpackage.* to com.sun.org.apache.subpackage.internal.*
- The base versions of Xerces and Xalan are:
- Xerces: 2.6.2 +
- Xalan: 2.6.0 +
The JAXP 1.2.6 release notes are available at: http://java.sun.com/webservices/docs/1.4/jaxp/ReleaseNotes.html
System Requirements
This section lists the requirements that must be met before installing the Sun Java System Application Server Platform Edition 8 product.
Platform Requirements
The following table lists the operating systems that are supported for Sun Java System Application Server Platform Edition 8 2004Q4 Beta product.
Table 2 Supported Operating Systems
Operating System
|
Minimum Memory
|
Recommended Memory
|
Minimum Disk Space
|
Recommended Disk Space
|
JVM
|
Sun Solaris 9 (SPARC) Solaris 9 (x86)
|
256 MB
|
512 MB
|
250 MB free
|
500 MB free
|
JDK 1.4.2_05
|
Sun Java Desktop System
|
256 MB
|
512 MB
|
83 MB free
|
300 MB free
|
JDK 1.4.2_05
|
Redhat Enterprise Linux 2.1 Update 2, 3.0 Update 1
|
256 MB
|
512 MB
|
250 MB free
|
500 MB free
|
JDK 1.4.2_05
|
Microsoft Windows 2000 Advanced Server Service Pack 4+
|
256 MB
|
512 MB
|
250 MB free
|
500 MB free
|
JDK 1.4.2_05
|
Microsoft Windows XP Professional Service Pack 1+
|
256 MB
|
512 MB
|
250 MB free
|
500 MB free
|
JDK 1.4.2_05
|
On UNIX, you can check your operating system version using the uname command. Disk space can be checked using the df command.
Solaris Patch Requirements
It is recommended that Solaris 9, 10 (x86, SPARC) users have the “Sun recommended patch cluster” installed. This patch cluster is available under “Recommended and Security Patches” here:
http://sunsolve.sun.com/
RedHat Enterprise Linux 3.0 Additional Package Requirements
To run native components of this product, including installer, the following package, which is not part of the standard RedHat Enterprise Linux 3.0 distribution, should be installed: compat-libstdc++-7.3-2.96.118.i386.rpm
The package can be downloaded from:
http://mirrors.kernel.org/redhat/redhat/linux/9/en/os/i386/RedHat/RPMS/compat-libstdc++-7.3-2.96.118.i386.rpm
JDBC Drivers and Databases
The Sun Java System Application Server Platform Edition is designed to support connectivity to any DBMS with a corresponding JDBC driver. For a list of components that Sun has tested and found to be acceptable for constructing J2EE compatible database configurations, please refer to the following table:
Table 3 J2EE Compatible JDBC Drivers
JDBC Vendor
|
JDBC Driver Type
|
Supported Database Server
|
i-net Software
|
Type 4
|
Oracle (R) 8.1.7, 9i, 9.2.0.3 Sybase ASE 12.5.2 MS SQL Server 2000 4.0 Service Pack 1
|
DataDirect
|
Type 4
|
Oracle 9i, 10G Sybase ASE 12.5.2 MS SQL Server 2000 4.0 Service Pack 1 IBM DB2 8.1 Service Pack3+
|
PointBase
|
Type 4
|
PointBase Network Server 4.8
|
i-net Software
|
Type 2
|
Oracle (R) 9i,
|
IBM
|
Type 2
|
IBM DB2 8.1 Service Pack 3+
|
For more information about i-net Software, see:
http://www.inetsoftware.de/
For more information about DataDirect Technologies, see:
http://www.datadirect.com/
The following table identifies additional supported JDBC drivers; however these drivers are not J2EE compatible.
Table 4 JDBC Drivers not J2EE compatible
JDBC Vendor
|
JDBC Driver Type
|
Supported Database Server
|
Oracle
|
Type 4
|
Oracle (R) 9.2.0.3, 10G
|
Sybase
|
jConnector
|
Sybase ASE 12.5.1
|
Additional drivers have been tested to meet the JDBC requirements of the J2EE 1.4 platform with the JDBC Driver Certification Program. These drivers can be used for JDBC connectivity with the Sun Java System Application Server. While Sun offers no product support for these drivers, we will support the use of these drivers with the Sun Java System Application Server.
Web Servers
This section lists the web servers that are supported for the Sun Java System Application Server Platform Edition 8 2004Q4 Beta.
Table 5 Supported Web Servers
Web Server
|
Version
|
Operating System
|
Sun Java System Web Server
|
6.0 Service Pack 6+
|
Solaris SPARC 8 9, 10 Red Hat Enterprise Linux 2.1 Update 2, 3.0 Update 1
|
Apache Web Server
|
1.3.27+
|
Solaris SPARC 9, 10 x86, Red Hat Enterprise Linux 2.1 Update 2, 3.0 Update 1
|
Microsoft IIS
|
5.0+
|
Windows Server 2003 Windows 2000 Advanced Server Service Pack 4+
|
Browsers
This section lists the browsers that are supported with the Sun Java System Application Server Platform Edition 8 2004Q4 Beta.
Table 6 Browsers Supported
Browser
|
Version
|
Netscape Navigator
|
4.79, 6.2, 7.0
|
Internet Explorer
|
5.5 Service Pack 2, 6.0
|
Upgrading the Sun Java System Application Server
Refer to the Installation Guide for complete instructions for upgrading from a previous version of the Application server to the Sun Java System Application Server Platform Edition 8 2004Q4 Beta.
Other Requirements
The following additional requirements should be met before installing the Sun Java System Application Server software.
- Free space: your temporary directory must have a minimum of 35MB free for Sun Java System Application Server installation, and 250 MB of free space for the SDK installation.
- Using the uninstall program: If you need to remove the application server from your system, it is important to use the uninstall program that is included with the software. If you attempt to use another method, problems will arise when you try to reinstall the same version, or when you install a new version.
- Free ports: You must have seven unused ports available.
- The installation program automatically detects ports in use and suggests currently unused ports for the default settings. By default, the initial default ports are 8080 for the HTTP server, and 4848 for the Admin Server.
- The installation program will detect used ports and assign two others for you: Sun JavaTM System Message Queue (by default, 7676), and IIOP (by default, 3700 for IIOP and 3820 and 3890 for IIOP/SSL). If these default port numbers are in use, the installation program will assign a random port number from the dynamic port range (note that this may not be the next available port number).
- Starting previously-installed servers (UNIX) — unless you are replacing the previously installed server, you should start it before you begin the Sun Java System Application Server 8 installation process. This allows the installation program to detect ports that are in use and avoid assigning them for other uses.
- Replacing previously-installed servers (UNIX) — if you have an older version on the Sun Java System Application Server installed that you wish to replace with the current Application Server, you should stop it before installing the new server. Use the installation program upgrade wizard to upgrade the server.
- Shutting down firewall (Microsoft Windows) — You must stop any firewall software before installing the Sun Java System Application Server software, because some of this software disables all ports by default. The installation program must be able to accurately determine which ports are available.
For further compatibility information, see the Compatibility Guide available at:
Documentation
In addition to these release notes, the Application Server product includes an entire set of documentation that can be found at this location:
The following table summarizes the books included in the Application Server core application documentation set.
Books in This Documentation Set
Book Title
|
Description
|
Release Notes
|
Late-breaking information about the software and the documentation. Includes a comprehensive, table-based summary of supported hardware, operating system, JDK, and JDBC/RDBMS.
|
Compatibility Guide
|
Differences between the adjacent product releases and configuration options that may result in incompatibility with the product specifications.
|
Quick Start Guide
|
How to get started with the Sun Java System Application Server product.
|
Installation Guide
|
Installing the Sun Java System Application Server software and its components, such as sample applications, the Administration Console, and the high-availability components. Instructions for implementing a basic high-availability configuration are included.
|
Developer’s Guide
|
Creating and implementing Java 2 Platform, Enterprise Edition (J2EE platform) applications intended to run on the Sun Java System Application Server that follow the open Java standards model for J2EE components and APIs. Includes general information about developer tools, security, assembly, deployment, debugging, and creating lifecycle modules.
|
J2EE 1.4 Tutorial
|
Using J2EE 1.4 platform technologies and APIs to develop J2EE applications and deploying the applications on the Sun Java System Application Server.
|
Administration Guide
|
Information and instructions on the configuration, management, and deployment of the Sun Java System Application Server subsystems and components, from both the Administration Console and the command-line interface. Topics include cluster management, the high-availability database, load balancing, and session persistence. A comprehensive Sun Java System Application Server glossary is included.
|
Reference
|
Editing the Sun Java System Application Server configuration file, domain.xml.
|
Migration Guide
|
Migrating your applications to the new Sun Java System Application Server programming model, specifically from iPlanet Application Server 6.x and from Netscape Application Server 4.0. Includes a sample migration.
|
Troubleshooting Guide
|
Information on solving Sun Java System Application Server problems.
|
Diagnostics in Log Resource Bundles
|
Information on solving Sun Java System Application Server error messages.
|
Utility Reference Manual
|
Utility commands available with the Sun Java System Application Server; written in manpage style.
|
Known Problems and Limitations
This section describes known problems and associated workarounds for the Sun Java System Application Server Platform Edition 8 2004Q4 Beta product. If a summary statement does not specify a particular platform, the problem applies to all platforms. This information is organized into the following sections:
Connectors
This section describes the known connector issues and associated solutions.
ID
|
Summary
|
6165776
|
Cascade connector undeploy fails in remote Enterprise Edition deployment scenarios.
When a connector module is deployed on a cluster which has instances on local and remote machine(s) and the user invokes undeploy of the connector module with the cascade option set to true, the undeployment fails with the following error:
CLI171 Command undeploy failed: ERROR - Stop Application in remote-server-instance Component not registered.
Solution
The cascade option in the undeploy command is used to automatically delete dependent resources of a connector module. Instead of using the cascade option in remote server instance deployments in the Enterprise Edition of the Application server, delete the dependent resources using the relevant asadmin command or the Admin Console, then invoke the undeploy command without the cascade option.
|
Container Managed Persistence
This section describes the known container managed persistence issues and associated solutions.
ID
|
Summary
|
5052946
|
DBSCHEMA: 117 failures in CMP with new version of oracle inet driver
The capture-schema utility does not successfully capture all of the table information needed by the CMP container when using the inet Oraxno 2.06 or later driver. The maximum size of the LOB DataType on Oracle is 4GB. Starting with inet Oraxno release 2.06, the JDBC driver will not return the correct size of 4GB for a LOB via DatabaseMetaData.getColumns().
Solution
Use a previous version of the inet Oraxno driver with capture-schema. This does not effect the use of the Oraxno 2.06 driver with the Sun Java System Application Server after you capture the information for the schema.
|
Deploytool
This section describes the known Deploytool issues and associated solutions.
ID
|
Summary
|
5036156
|
On Windows, invoking the Sun-specific Settings CMP Database, then saving the changes causes the changes to be lost and a tmp#####.jar file to be created.
Changes may be lost for the Container Managed Persistence Enterprise Java Bean JAR after the CMP Database dialog has been invoked by any of the following ways:
1. Click on Sun-specific Settings button on the EJB JAR General tab.
2. Click on Sun-specific Settings button on EJB General tab. Select CMP Database from the View menu.
3. Click on the CMP Database (Sun-specific) button on Entity tab.
Solution
When this problem occurs a tmp#####.jar is created in the same location as the original CMP EJB JAR file. The tmp#####.jar is the CMP EJB JAR file with the newly saved changes. The tmp#####.jar can be renamed and opened in Deploytool for editing. “#####” represents a random number - i.e., tmp46278.jar.
|
5045659
|
Deploytool incorrectly sets the fetch group for BLOB/CLOB column types.
If the user selects the Sun-specific Settings button to bring up the CMP Database dialog and hasn’t specified the fetch group for BLOB/CLOB column types in the sun-cmp-mappings.xml file, the fetch group for the BLOB/CLOB column types is incorrectly set to Default.
Solution
Set the BLOB/CLOB type column fetch group to None.
1. Click on the Sun-specific Settings button in the EJB JAR General tab.
2. For each Enterprise Bean that has “BLOB” or “CLOB” listed under the Type column in the Field Mappings table, select None in the Fetch column.
3. Close the CMP Database dialog.
4. Save the application.
|
J2EE Tutorial
ID
|
Summary
|
6157260
|
The instructions for deploying the example in the section of Chapter 34 entitled An Application Example That Consumes Messages from a Remote J2EE Server does not work as described in the Deploying the Applications subsection.
The instructions to retrieve a client JAR file when deploying JupiterClientApp.ear results in an error.
Solution
To deploy this application and retrieve the client JAR, instead of selecting the Return Client JAR checkbox in the Deploy Module dialog box, perform one of the following:
- Deploy the application to the remote server without saving the client JAR. Select the server, select the deployed application, and click the Client JAR button on the Deployed Applications page to save the client JAR.
- Use the asadmin deploy command with the --retrieve option to specify the directory where the client JAR is to be saved.
|
Lifecycle Management
This section describes the known lifecycle management issues and associated solutions.
ID
|
Summary
|
5064098
|
On Windows, application server startup fails with error: appservDAS.exe - Entry Point Not Found.
While trying to start the Application server domain, the startup cannot be initiated using the Menu Item on the Start Menu or the asadmin start-domain command.
The server startup fails after displaying the following dialog box:
The procedure entry point PK11_DestryPBEParas could not be located in the dynamic link library nss3.dll The procedure entry point SECKEY_PublicKeyStrengthInBits could not be located in dynamic link library nss3.dll
Solution
The problem is caused by presence of an older version of libnspr4.dll in Windows system location (for example, C:\WINDOWS\System32). In general, this file is left behind by older versions of the Sun Java System Web Server even after uninstallation. Rename the file to some other name to workaround this application server startup problem.
|
6165358
|
Synchronization file locking problem when starting the same instance without stopping it first.
When creating an instance and starting it, if the start-instance command is executed again, and subsequent start-instance commands return success while the list-instances command reports that the instance is not running. The instance is in fact running, however, when attempting to stop it an exception is thrown.
Solution
Stop the instance prior to starting the instance again. If the instance is still running, kill the instance then start the instance again.
|
Resources
This section describes the known resources issues and associated solutions.
ID
|
Summary
|
6158411
|
The delete-resource-adapter-config command fails to delete the resource-adapter-config when the resource adapter configuration was created using resources_xml file.
Solution
Create the resource-adapter-config using the create-resource-adapter-config command instead of using the XML resource file. Once a resource-adapter-config is created this way, it can be deleted using the delete-resource-adapter-config command.
|
Servlets
This section describes the known servlet issues and associated solutions.
ID
|
Summary
|
6159619
|
On Windows, CTS servlet/sepc/requestmap/URLClient.java#longestPathMatchTest2 fails.
If the user defines two URIs (servlet mappings) differing in case alone, they are treated as the same on Windows.
Solution
Users should not differentiate URI definitions based on case alone.
|
Upgrade Utility
This section describes the known Upgrade utility issues and associated solutions.
ID
|
Summary
|
6157205
|
Certification Migration for 7.x Enterprise Edition not working.
When running the Upgrade utility and selecting the security certificate to migrate, the following problem is encountered:
libsmine3.so: version “NSS_3.4 not found.
Solution
Skip the certificate migration option when upgrading.
|
6157425
|
Failed to create a new instance in 7.x Enterprise Edition.
If Server 7.x Enterprise Edition has two instances (server1:7070, server2:7071), server2 is not converted correctly to the Sun Java System Application Server Platform Edition 8 2004Q4 Beta.
Solution
This issue will be resolved in the final release of the Application Server Enterprise Edition 8 2004Q4 product.
|
6165528
|
Domains created in custom-path other than install_dir/domains directory are not upgraded directly while upgrading from Application Server Platform Edition 8 to Application Server Platform Edition or Standard Edition 8 2004Q4 Beta.
When running the Upgrade Utility and identifying the install_dir as the source installation directory, the upgrade process upgrades only those domains that are created under install_dir/domains directory. Domains created in other locations are not upgraded.
Solution
Before starting the upgrade process, copy all the domain directories from their different locations to the install_dir/domains directory.
|
Web Applications
This section describes the known web application issues and associated solutions.
ID
|
Summary
|
6165505
|
servletRequest.getlocalName returns an IP address instead of a DNS name.
If a request has a servlet that makes the servletRequest.getlocalName method call, an IP address is returned.
Solution
There is no known workaround for this issue.
|
Web Container
This section describes the known web container issues and associated solutions.
ID
|
Summary
|
6116887
|
Cannot start domain as user different from install.
After installing the Application Server as root user and creating a domain using the create-domain command, the domain gets created, but starting the domain fails and the following error is logged:
{#|2004-07-23T21:21:34.351-0700|ALERT|sun-appserver-ee8.1|javax.enterprise.system.container.web|_ThreadID=10;|HTTP Service: security (27699) : CORE3259: Temporary directory /opt/SUNWappserver/temp (specified by the TempDir magnus.conf directive) is not owned by the server user. Please change TempDir or remove the directory and restart the server.|#]
Solution
Under the http-service element in the domain.xml (pertaining to the domain that is newly created), set the TempDir property to some location that the domain creator owns. For example:
<property name=”TempDir” value=”/home/kmeduri/ASDomains/domains/mydomain/temp” />
|
6155216
|
Different return values of javax.servlet.http.HttpServletRequest getHeader() and getHeaders() on Sun Java System Application Server Platform Edition 8 Beta and Enterprise Edition 8 Beta.
Sun Java System Application Server Platform Edition 8 2004Q4 Beta aggregates several HTTP request headers of the same name into a single HTTP request header with a comma-separated list of header values. Sun Java System Application Server Platform Edition 8 2004Q4 Beta does not perform this type of header aggregation.
This means that in Sun Java System Application Server Platform Edition 8 2004Q4 Beta, HTTP request headers with the same name are represented as individual items in the enumeration returned by javax.servlet.http.HttpServletRequest.getHeaders, whereas in Sun Java System Application Server Platform Edition 8 2004Q4 Beta they are represented as a single enumeration item with their header values separated by comma.
Likewise, in Sun Java System Application Server Platform Edition 8 2004Q4 Beta javax.servlet.http.HttpServletRequest.getHeaders always returns the aggregated header values (separated by comma) if the HTTP request contains multiple headers with the specified name, whereas in Sun Java System Application Server Platform Edition 8 2004Q4 Beta, this method returns the first header in the request if there are multiple headers with the specified name in the request.
Either behavior is conformant with the HTTP 1.1 Specification (see http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2).
Solution
Servlet code must consider the possibility of header aggregation when calling javax.servlet.http.HttpServletRequest getHeader() or getHeaders().
|
6159663
|
Case differences in HTTP response header names between Sun Java System Application Server Platform Edition 8 Beta and Enterprise Edition 8 Beta.
If a servlet developer adds an HTTP response header to the HTTP response, by calling one of the addXXXHeader() methods on javax.servlet.http.HttpServletResponse, the header name in the HTTP response returned to the client will differ in case between the Application Server Platform Edition 8 Beta and Enterprise Edition 8 Beta.
While Application Server Platform Edition 8 preserves the case of the HTTP response header named provided to addXXXHeader(), the Application Server Enterprise Edition 8 converts the first character to uppercase, and converts all remaining characters to lower case.
Notice that either behavior is compliant with the HTTP 1.1 specification which declares header names to be case-insensitive (see http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2).
The same is true for all response headers added by the web container itself. For example, the standard “X-Powered-By” response header will be returned as “X-Powered-By” on the Sun Java System Application Server Platform Edition 8, and will be returned as “X-powered-by” on the Sun Java System Application Server Enterprise Edition 8.
Solution
Have the HTTP client perform s case-insensitive search for header names in the HTTP response.
|
none
|
Web container performance is sub-optimal for the beta release.
The web container performance is slow.
Solution
The final release will resolve this issue.
|
Redistributable Files
Sun Java System Application Server Platform Edition 8 does not contain any files that can be redistributed.
How to Report Problems
Use the following resources to handle problems you may encounter with the Application Server product:
- Feedback Submittal form—A form for submitting feedback on the Application Server product, here:
- J2EE-INTEREST list—A mailing list for J2EE questions, here:
- Bug database on Java Developer Connection—To view bugs or to submit a bug, use the Java Developer Connection Bug Parade here:
- Java Technology Forums—An interactive message board for sharing knowledge and questions about Java technologies and programming techniques. Use the J2EE SDK forum here for discussions related to the Sun Java System Application Server 8 Platform Edition product:
For More Information
Useful information can be found at the following locations:
- Application Server product information:
- Java developer resources:
- Java 2 Platform, Enterprise Edition (J2EE) site:
- Application Server product documentation:
- Sun Microsystems product documentation:
Legal Notices