Sun Java Solaris Communities My SDN Account Join SDN

Documentation

J2EE[tm] v1.4 Application Server Release Notes

 

The Java™ 2 Platform, Enterprise Edition (J2EE) Application Server greatly simplifies the task of creating and administering web services applications. The J2EE Application Server provides a development path for web services that simplifies the development process while providing uniquely flexible growth opportunities.

These release notes contain important information available at the time of the J2EE 1.4 Application Server product. Product requirements, what’s new, platform summary, installation notes, known problems, and other late-breaking issues are addressed here. Read this document before you begin using the J2EE 1.4 Application Server product.

This document contains the following sections:


What’s New in the J2EE 1.4 Application Server

The J2EE 1.4 Application Server implements the new features specified by the J2EE 1.4 platform. The following sections describe the new features and technologies:

Application Server Implementation Changes

Compared to the J2EE 1.3 SDK (reference implementation), the J2EE 1.4 platform Application Sever includes significant enhancements. The following features are of particular interest for users of the previous reference implementation.

Automatic Deployment

You can automatically deploy an application in a running instance of J2EE 1.4 Application Server by copying the EAR, EJB JAR, or WAR file to the domain’s autodeploy directory.

Command Line Utilities

J2EE 1.4 Application Server provides asadmin, a robust command-line utility for administering the server and deploying applications. J2EE 1.4 Application Server also contains the asant utility which you can use to accelerate the development process for J2EE applications. For more information on these utilities, see the manpages.

Administration Console

J2EE 1.4 Application Server provides the Admin Console -- a WSYWIG interface for administering the server.

Container-Managed Persistence (CMP)

The J2EE 1.4 Application Server includes the ability to wrap existing database schemas to CMP enterprise beans.

Read-Only Entity Beans

The read-only bean is an entity bean that is never modified by an EJB client. Read-only beans avoid database updates completely.

PointBase Database Server

This release includes the PointBase database server, replacing the Cloudscape database server.

JavaServer Pages Standard Tag Library (JSTL) 1.1

This library is shipped as a convenience library with J2EE 1.4 Application Server. It adds standard functions and is dependent upon the JSP 2.0 expression language. JSTL 1.1 no longer has its own expression evaluator.

J2EE 1.4 Platform Changes

The following sections describe the new features and technologies added to J2EE 1.4 platform:

Web Services

Support for Web services for the J2EE 1.4 platform is included in this release. Web services based on SOAP and HTTP are supported, so that J2EE technology can be integrated with Web services in a variety of ways. You can expose J2EE components (servlets and enterprise beans) as Web services. Clients that are written in the Java programming language or existing Web service clients that don’t take advantage of Java technology can access these services. Also, J2EE components can act as Web service clients. This release provides full support of the WS-I Basic Profile specification, which is a standard intended to improve interoperability of Web services.

The following sections briefly describe the new Web service APIs.

Java API for XML-based RPC (JAX-RPC) 1.1

  • Interoperability based on SOAP and WSDL
  • Servlet-based endpoints
  • Stateless session bean endpoints (as defined in EJB 2.1)
  • Client programming model for stubs, dynamic proxies, or dynamic invocation interfaces
  • Serializers and deserializers for most Collection types
  • Support for xsd:anyType
  • Configurable support for SSL-based authentication
  • Data binding for document literal operations

Java API for XML Registries (JAXR) 1.0

  • Standard API for accessing different kinds of XML registries
  • Unified information model describing the content and metadata within XML registries

Web Services for J2EE 1.1

  • Deployment requirements for Web service clients and endpoints
  • Standard deployment descriptors
  • JAX-RPC programming model
  • JNDI lookup of service objects
  • Container-managed security
  • Declaration of handlers and serializers

SOAP with Attachments API for Java (SAAJ) 1.2

  • Extends Document Object Model (DOM) APIs so that SAAJ trees are also DOM trees, making SAAJ integrate more easily with many applications and tools.
  • Gives end users more control over details about formatting and encoding of a SOAP message.
  • Provides new methods to automate frequent or error-prone tasks.

Other New J2EE Technologies

The following sections list other new technologies that have been added to this release:

J2EE Deployment API 1.1

  • Deployment tools independent of J2EE Application Server
  • JavaBeans™ for editing deployment information

J2EE Management API 1.0

  • Information model for management that includes attributes, events, statistics, and state management
  • May be available through standard management protocols such as SNMP and WBEM
  • Uses Java Management Extensions (JMX)

Enhancements to Existing J2EE Technologies

This release includes important enhancements to technologies that were delivered in previous releases of the J2EE SDK. The following sections briefly describe these technologies:

J2EE Connector 1.5

  • Bi-directional connectivity (synchronous and asynchronous) between EISs and J2EE applications provided by resource adapters
  • Java Message Service™ (JMS) pluggability

Enterprise Java Beans™ (EJB™) 2.1

  • Web service endpoints (stateless session beans)
  • Message-driven bean generalization with corresponding support in J2EE Connector 1.5
  • EJB QL enhancements
  • Timer service

JavaServer Pages™ (JSP™) 2.0

  • Simple expression language (from JSTL)
  • Improved XML syntax
  • Simple tag handlers
  • Tag files
  • Global configuration

Java Servlet 2.4

  • Request listeners
  • Filters under a request dispatcher

Java Message Service (JMS) 1.1

  • Common interfaces to allow access to either point-to-point or publish-subscribe. The administered objects that you use remain domain-specific, and the behavior of the application will depend partly on whether you are using a queue or a topic. However, the code itself can be common to both domains, making your applications flexible and reusable.
  • Integration using a J2EE Connector Architecture resource adapter. Deployers configure message-driven beans using the EJB 2.1 activation configuration properties. These properties may be specified in the deployment descriptor for the message-driven bean or in the runtime deployment descriptor.
  • Message flow properties for message-driven beans. The resource-env-ref element from release 1.3 is still supported.

Conversion of Deployment Descriptors to XML Schema

  • More parser validation
  • Old deployment descriptors are still supported.

Installed Library Support

  • Separate installation from applications
  • Referenced with the JAR file attributes of the J2SE™ platform

Other Technologies

In addition to the technologies listed above, the following technologies are supported for J2EE 1.4 platform:

  • Java API for XML Processing (JAXP) 1.2
  • JDBC 3.0
  • JavaMail 1.3
  • Java Transaction API (JTA) 1.01B
  • JavaBeans Activation Framework (JAF)

J2EE SDK Bundle

For this release, you can get a stand-alone J2EE 1.4 Application Server, or you can get the Java 2 Platform, Enterprise Edition 1.4 SDK bundle. This bundle contains:

  • J2SE 1.4.2_02 platform
  • Java 2 Platform, Enterprise Edition 1.4 Samples (contains BluePrints and J2EE 1.4 Application Server samples)
  • J2EE 1.4 Application Server

You can also get the Java 2 Platform, Enterprise Edition 1.4 BluePrints bundle, which contains just the BluePrints documentation and examples.


Key Features

The J2EE Application Server includes the following components:

Application Server

The Application Server supports the current drafts of the J2EE 1.4 specifications.

  • Supports the Java Web Services APIs:
    • Java API for XML Processing (JAXP) version 1.2
    • Java API for XML-based Remote Procedure Calls (JAX-RPC) version 1.1
    • Java API for XML Registries (JAXR) 1.0
    • SOAP with Attachments API for Java (SAAJ) version 1.2
  • Supports the Enterprise JavaBeans specification version 2.1
  • Supports the WS-I Basic Profile specification
  • Supports the J2EE Deployment API version 1.1
  • Supports the J2EE Management specification version 1.0
  • Supports the Java Authorization Contract For Containers 1.0
  • Supports the JavaServer Pages specification version 2.0
  • Supports the Java Servlet specification version 2.4
  • Supports the Java Naming and Directory Interface (JNDI) specification version 1.2
  • Supports the Java Database Connectivity (JDBC) specification version 3.0
  • Supports the JavaMail API version 1.3
  • Supports the JavaBeans Activation Framework (JAF) version 1.0.
  • Supports the J2EE Connector specification version 1.5
  • Supports the JavaServer Pages Standard Tag Library (JSTL) version 1.1
  • Includes runtime control, process, and thread management
  • Embeds a highly scalable and high-performance Container Managed Persistence runtime
  • Java Transaction Service-based, all-Java transaction manager
  • Object Request Broker (ORB)
  • J2EE verifier utilities
  • Customized Apache Ant tasks (asant utility)
  • Browser-based administration tool (Admin Console)
  • Command-line administration tool (asadmin) with interactive and scripting modes
  • Graphical deployment utility (deploytool) to simplify application, enterprise bean, and connector packaging and deployment
  • Sample applications that demonstrate the features of the Application Server and J2EE technology

Sun Java System Message Queue

Also available as a separate product, the Sun JavaTM System Message Queue product (formerly known as Sun ONE Message Queue) is an integral part of the Application Server. This all-Java programming language component delivers a robust JMS provider for both JMS clients and message-driven beans. It is extremely scalable, with high-performance. This product includes the Sun JavaTM System Message Queue Platform 3.5. To get enhanced JMS features, the Sun JavaTM System Message Queue Enterprise 3.5. can be separately purchased.

PointBase Database Server and Type 4 JDBC Driver

PointBase Server 4.6 relational database is included with the J2EE Application Server to support the sample applications and development of JDBC-based applications. PointBase's Type 4 driver supporting the JDBC™ API (“JDBC driver”) is preconfigured during installation. Tables are also created and populated for all of the sample applications that depend on JDBC. The bundled PointBase distribution has a 5 MB total database size limitation.

Java 2 Software Development Kit, Standard Edition

J2EE Application Server is certified with the J2SE platform SDK and leverages the performance and feature improvements that are part of the J2SE 1.4 platform.


System Requirements

This section lists the requirements that must be met before installing the J2EE 1.4 Application Server product.

Platform Requirements

The following table lists the operating systems that are supported for J2EE 1.4 Application Server product.

Operating System

Architecture

Minimum Memory

Recommended Memory

Minimum Disk Space

Recommended Disk Space

JVM

Sun Solaris 9

32 and 64 bit

256 MB

512 MB

250 MB free

500 MB free

JDK 1.4.2

Red Hat Linux 8.0

32 bit

256 MB

512 MB

83 MB free

300 MB free

JDK 1.4.2

Microsoft Windows 2000 Professional

Intel 32 bit

256 MB

512 MB

250 MB free

500 MB free

JDK 1.4.2

Microsoft Windows XP Professional

Intel 32 bit

256 MB

512 MB

250 MB free

500 MB free

JDK 1.4.2

Microsoft Windows 2000 Server SP3+

Intel 32 bit

256 MB

512 MB

250 MB free

500 MB free

JDK 1.4.2

Microsoft Windows Server 2003

Intel 32 bit

256 MB

512 MB

250 MB free

500 MB free

JDK 1.4.2

On UNIX, you can check your operating system version using the uname command. Disk space can be checked using the df command.


Note

Third party J2SEs, even with appropriate version numbers, are not supported.


The following table lists the JDBC driver and database combinations that are supported for J2EE 1.4 Application Server product.

JDBC Vendor

JDBC Driver Type

Supported Database Server

Datadirect Technologies

Connect JDBC 3.2 (Type 4)

Oracle (R) 9.2

PointBase

Type 4

PointBase Network Server 4.6

Solaris Patch Requirements

For Solaris 8 systems, the following Solaris patches must be installed:

  • 109326-06
  • 108827-26 or 108993-18

These patches can be retrieved from the patch finder page located here:

http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access

It is recommended that Solaris 8 users have the "Sun recommended patch cluster" installed. The cluster includes the three required patches listed above. This patch is available under "Recommended and Security Patches" here:

http://sunsolve.sun.com/

JDBC Drivers and Databases

The J2EE 1.4 Application Server 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:

JDBC Vendor

JDBC Driver Type

Supported Database Server

Datadirect Technologies

Connect JDBC 3.0 (Type 4)

Oracle (R) 8.1.7

iNet Software

iNet JDBC Driver

Oracle (R) 8.1.7 v2.03.08

Additional drivers have been tested to meet the JDBC requirements of the J2EE 1.3 platform with the JDBC Driver Certification Program. These drivers can be used for JDBC connectivity with the J2EE 1.4 Application Server. While Sun offers no product support for these drivers, we will support the use of these drivers with the J2EE 1.4 Application Server.

Other Requirements

The following additional requirements should be met before installing the J2EE 1.4 Application Server software.

  • Free space: your temporary directory must have a minimum of 100 MB free.
  • 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 80 for the HTTP server (Windows), 1024 for the HTTP server (UNIX), 1043 for HTTPS, 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 1060 and 1061 for IIOP/SSL). If these default port numbers are in use, the installation program will assign the next available port (for example, 7677 or 7678, and so on).
  • (For UNIX) Starting previously-installed servers-If there are previously-installed application servers or web servers on the target machine, you must start them before you begin the J2EE 1.4 Application Server installation process. This allows the installation program to detect ports that are in use and avoid assigning them for other uses.
  • (For Microsoft Windows) Shutting down firewall-You must stop any firewall software before installing the J2EE 1.4 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 J2EE 1.4 Application Server product includes an entire set of documentation that can be found at this location:

The following list provides a brief description of the documentation in the J2EE 1.4 Application Server collection:

  • Quick Start Guide—Describes how to get started with the J2EE 1.4 Application Server product. Focuses on initial developer exposure; is also suited for users evaluating the product.
  • Installation Notes—Provides instructions for installing or uninstalling the J2EE 1.4 Application Server software and its components. Supported platforms are listed.
  • J2EE 1.4 Tutorial—Describes how to develop software using the technologies provided in the J2EE 1.4 Application Server product. You can find the J2EE 1.4 Tutorial here:
  • Compatibility Guide—Provides information on backward compatibility issues.
  • Manpages for Command-line Interface and Utilities—Documentation for all command-line interface commands and theJ2EE 1.4 Application Server utility commands.
  • Online help for the Admin Console—Provides content-specific online help for the J2EE 1.4 Application Server Administration Console web-based interface.
  • Online help for the deploytool utility—Provides content-specific online help for the J2EE 1.4 Application Server deploytool utility.
  • Troubleshooting Guide—Provides information on solving problems associated with the J2EE 1.4 Application Server product..

    Note

    J2SE 1.4.1 documentation can be found here:

    http://java.sun.com/j2se/1.4.1/docs/index.html



Known Problems and Limitations

This section describes known problems and associated workarounds for the J2EE 1.4 Application Server product. If a summary statement does not specify a particular platform, the problem applies all platforms.

ID

Summary

4403166

On Microsoft Windows, package, path, and application names longer than 255 characters will fail to deploy applications.

On Microsoft Windows, long package and path names are not supported because of a JDK limitation. During deployment, the deploytool utility will try to extract the class file from the archive. If the expanded name is more than 255 characters, the extraction fails.

  • Example of a long application name:

servlet_jsh_HttpServletRequestWrapper.ear

  • Example of a long package name:

servlet_jsh_HttpServletRequestWrapper_1\servlet_jsh_HttpServlet
RequestWrapper_servlet_war\WEB-INF\classes\tests\javax_servlet_http\
HttpServletRequestWrapperHttpServletRequestWrapperConstructorTest
Servlet.class

  • Example of a long path name:

drive\:Sun\j2ee1.4sdk_beta2

Solution

Consider the following solutions:

1.  Make a shorter directory structure during installation. For example, drive\:App\ instead of the default drive:\Sun\j2ee1.4sdk_beta2.

2.  Use the create_instance command to rename the instance to something shorter. For example, <INSTALL>/instance1/domain1/ could be changed to <INSTALL>/i/d.

3.  Use shorter package, path, and application names.

4855659

Regression test hangs after about 7 clients sending to server.

In testing, after 7-8 clients are created and each client runs 10 tests sending data to a server, the test hangs.

Solution

None

4857325

Error "minor code 202" or hanging occurs as the last client sends data to the server (see description for Bug 4855659).

4859611

On Linux, the installer crashes while attempting to install on partition with insufficient disk space.

On Linux platforms only, if you select an installation directory on a partition that has insufficient disk space, the installation program correctly performs the disk space check operation (at the Ready to Install page) and reports the insufficient disk space problem.

If you now return to the Select Installation Directory page, select a different installation directory, and try to proceed with installation, the installation program crashes during the repeated disk space check, throwing the following exception:

Warning: Cannot convert string "MetaCtrl<Key>Insert" to type VirtualBinding InvocationTargetException thrown in method getUndersizedPartitions in class com.sun.install.products.ProductServerObject
Target Exception Trace:
java.lang.NullPointerException
 at LinuxNativeToolkit.getPartitionFreeSpace(LinuxNativeToolkit.java:166)at LinuxPlatformToolkit.getPartitionFreeSpace(LinuxPlatformToolkit.java:390)
 at com.sun.wizards.core.SystemInterface.getPartitionFreeSpace(SystemInterface.java:211)
...

Solution

On Linux, if the installation program reports insufficient disk space, do not try to change the installation location in the same session. Cancel the installation session, restart the installation, and specify a different installation directory.

4913449

On Windows and Linux multi-processor systems seem to hang.

This is a verified JDK bug that is being addressed.

Solution

none

4922274

Installer should use ServerSocket to perform the port probing.

Currently, installer uses client socket to test if a port is free. However, if a firewall is active, the request hangs for 5 minutes.

Solution

You must have seven unused ports available.

4924777

If an error occurs when clicking "Finish" on either the "Create Connector Connection Pool" or "Create JDBC Connection Pool" wizard, the error is not displayed in the Administration Console and the wizard closes losing all information gathered.

Solution

Restart the wizard.

4925543

If an error occurs while submitting a form in the Administration Console, all changes to that form may be lost.

Solution

Retype your input in the form.

4927544

When the given file path is invalid, or an invalid file (ear, jar etc) is given in the deployment page of the Administration Console, it stays in the same page without showing any exception message.

Solution

Enter a valid file path.

4934561

Directory not getting cleaned after undeployment

When undeploying WAR files containing libraries, the JAR is not cleaned up from the domains/domain1/applicatioins/j2ee-modules directory.

Solution

Stop the server and delete the libraries that have not been cleaned up.

4941142

When using any command that accepts the --property option and you include two equal signs (=), the Command-line interface allows the command to successfully complete, but the domain.xml file property entry is not updated.

An ambinguous name/value pair is provided for the property option. For example, abc=def=ghi:123=456. The colon (:) is the delimiter between the pairs, so there are two name/value pairs here abc=def=ghi and 123=456. However, the first name/value pair is ambiguous since there are two equal (=) signs. The Command-line interface cannot distinguish which one is the name which one is the value. So the property fields are not added when creating the element.

Solution

The equal sign (=) must be preceded by an escape character “\”' to disambiquate the name/value pairs. For example if the property is abc=def\=ghi. The name is abc the value is def=ghi.

Additionally, the following characters must also be preceded by the escape character: : / < > ! $ % ^ & * | { } [ ] " ’ ‘ ~ ;

4941344

A Message Queue process stays behind on failed startup

Solution

When an Application Server startup fails, you can correct the configuration issue and restart the domain. The appserver will get attached to the already running Message Queue. Before deleting a domain, ensure that all processes for the domain are stopped.

You can determine which the Message Queue port is in use by examining the var/instances/<instance_name>/lock file.

4942108

Validation exception during the set of default attribute values for ejb-timer-service.

Configuration validator enforces that redelivery-interval-internal-in-millis should be greater than minimum-delivery-interval-in-millis, but the default values in sun-domain_1_0.dtd does not adhere to this rule.

Solution

Set "Redelivery Interval" to a value not less than the "Minimum Delivery Interval" and continue to work.

If you do need to set "Redelivery Interval" to a value less than the "Minimum Delivery Interval,”, stop the server, edit domain.xml file to set the proper ejb-timer-service attribute values, then restart server.

4942180

Deploytool doesn’t offer the just installed system as the default deployment.

Solution

1.  Delete the server that is offered by selecting File, Delete Server.

2.  Add a new server by selecting File, Add Server; with the requisite host/port combination.

4927886

On Solaris and Linux, when using asadmin utility, pressing Ctrl-C kills the domain when the domain is started in multimode.

Solution

1.  Do not use Ctrl-C to terminate asadmin mutimode. Use either "exit", "quit" or "Ctrl-D".

2.  Modify domain_dir/bin/startserv and add an ampersand (&) after the command on the last line.

When you install the Application Server for the first time, a default domain is created. For default domain, domain_dir is the install_dir/domains/domain1 where install_dir is the directory you selected when you installed the Application Server.

4939739

On Linux, the server process is killed during functional tests.

Solution

None

4945843

Incorrect information in the Deploytool CMP Settings dialog box online help.

The CMP Settings dialog box Create Field Mappings action needs modification. The JNDI name is not used by the Deploytool to connect to the database.

Solution

In the CMP Settings dialog box, provide the JNDI name of the CMP resource on the server instance where this EJB JAR is being deployed. Although the on line help says deploytool will try to connect using this JNDI name to determine which database vendor is based on to generate the database table, you actually need to specify the vendor name in the Create Field Mappings Dialog as this version of deploytool does not attempt to connect.

4946491

Deploytool requires WAR to have a Web component for deployment.

When a user deploys a standalone web application (WAR file), or an EAR consisting of a WAR file, Deploytool does not allow deployment if the WAR does not have at least one component specified in the XML descriptor file. This problem can occur, for example, when creating a WAR with only JSP pages and not providing explicit web.xml servlet mappings for any of them. Although this is a valid WAR, Deploytool will refuse to deploy it.

If it is a standalone WAR file, the following error message is displayed: Please add JSP/Servlet component to this WAR module and save your changes.

If it is an application EAR, the following error message is displayed: The following WAR module(s) need attention before they can be deployed.

Solution

1.  Add at least one servlet mapping via the Deploytool interface. Or, close the WAR or application, manually edit the web.xml in the WAR to specify at least one JSP file or servlet class. Then open the WAR or application again and deploy it.

2.  Use one of the other available method to deploy the WAR or application such asadmin command-line interface, or the Administration Console.

4948788

Must update Verisign root certificate.

The root certificates in cacerts.jks are picked up from the root certificate of cacerts file in jth JDK and they are exactly identical. Root certificate verisignclass1ca expires in 2020 while verisignclass3ca, verisignclass2ca, and verisignclass4ca certificates expire in Jan 2004.

Solution

1.  Download jdk1.4.2_03

2.  Get the cacerts file under jre/lib/security/cacerts

3.  Export verisign certificates (verisignclass2ca, verisignclass3ca, versignclass4ca) using keytool export command.
For example: keytool -export -alias verisignclass2ca -file /tmp/verisignclass2ca.cer -keystore cacerts

4.  Go to the cacerts.jks file for the particular domain for the Application Server (under domains/domain_name/config/cacerts.jks)

5.  Delete Verisign (class2ca, class3ca, class4ca) certificates using keytool.
For example: keytool -delete -alias verisignclass2ca -keystore cacerts.jks

6.  Import the certificates exported in step 3 into the Application Server cacerts.jks file.
For example: keytool -import -alias verisignclass2ca -file /tmp/verisignclass2ca.cer -keystore cacerts.jks

4949459

In Deploytool, whenever you close and reopen an application, make some modifications then save the application, the modifications may be lost.

If you close an application or module, open it again and perform some modifications and then save the module, the modifications are saved to a tempory file instead of the EAR/JAR you were working on. It appears as if the modifications have been lost.

Solution

To avoid this situation, if you want to re-open an application that you have previously closed, you should exit and restart the Deploytool.

4954585

File-based persistence of HTTP sessions broken.

HTTP sessions fail to be reloaded if the file-based PersistentManager,which persists HTTP sessions in a file, is used. The file-based PersistentManager is enabled by setting the persistence-type attribute of the session-manager element in sun-web.xml to "file", as follows:

<sun-web-app>
...
<session-config>
    <session-manager persistence-type=file>
        ....
    </session-manager>
</session-config>
...
</sun-web-app>

Solution

Use the StandardManager, which is the default session manager.


How to Report Problems

Use the following resources to handle problems you may encounter with the J2EE 1.4 Application Server product:


For More Information

Useful information can be found at the following locations:


Revision History

This section lists the changes that have been made in these release notes after the initial release of the J2EE 1.4 Application Server product

Revision Date

Description of Change

November 2003

J2EE 1.4 Application Server release.