JavaTM 2 SDK, Enterprise Edition Release Notes Version 1.2.1

Note: If you are reading this document from the download bundle, you may want to check the latest version of the Release Notes on our web site.

Contents

• Read This Section First
  
  
• What's New in This Release
  
  
• Supported Platforms
  
  
• Supported Databases and JDBC^TM Drivers
  
  
• What This Release Includes
  
  
• Required Software
  
  
• Current Limitations
  
  
• Known Bugs
  
  
• Differences Between Tomcat and the J2EE^TM SDK
  
  

Read This Section First

1. If you've downloaded the software but haven't read the Installation Instructions, please do so.

2. Make sure that you've installed the software that the Java^TM 2 SDK, Enterprise Edition relies on. See the Required Software section of this document.

3. Configure the Java^TM 2 SDK, Enterprise Edition software. See the Configuration Guide .

4. Read the Getting Started document to learn how to build your first J2EE application.

What's New in This Release

The new redeployment feature of the Application Deployment Tool enables the iterative development of J2EE applications. For example, if you want to modify a .class file in an enterprise bean, all you have to do is edit the source code, recompile it, and click the redeploy button on the Application Deployment Tool. The tool automatically replaces the old .class file in the application with the new one. (Prior to this release, if you wanted to modify an enterprise bean, you had to step through several wizard screens to rebuild the bean.) If you want to change a deployment setting, such as a JNDI name, you simply edit the appropriate field in the inspector panel of the Application Deployment Tool and then click the redeploy button.

This release also contains important bug fixes:

• You can create a composite primary key for an entity bean with container-managed persistence. (A composite primary key is made up of multiple instance variables of an entity bean.)
  
  
• Enterprise bean classes, home interfaces, and remote interfaces can inherit methods from super classes and interfaces.
  
  
• JSP^TM pages with character encodings other than ISO-8859_1 are supported on non-English locales.
  
  
• In JSP pages, nested compile-time includes are supported when relative URIs are used to specify the JSP pages.
  
  

Supported Platforms

• Solaris^TM Operating Environment, version 2.6
  
  
• Windows NT, version 4.0
  
  

Supported Databases and JDBC^TM Drivers

• Oracle8 Server, version 8.05
  
  
• Microsoft SQL Server, versions 6.5, 7.0
  
  
• Cloudscape, version 3.0.4
  
  

What This Release Includes

Services

• EJB^TM
  
  
• HTTP
  
  
• HTTP over SSL
  
  
• COS naming
  
  
• Authentication
  
  

Utilities

• Application Deployment Tool
  
  

  The deploytool utility packages J2EE components and deploys J2EE applications.

• Realm Tool
  
  

  The realmtool utility manages users for the J2EE server.

• Verifier
  
  

  The verifier utility validates J2EE component files.

• Packager
  
  

  The packager utility packages J2EE components.

• Cleanup Script
  
  

  The cleanup utility deletes all deployed J2EE applications.

Cloudscape DBMS

Java APIs for the Enterprise

• Enterprise JavaBeans^TM API, version 1.1
  
  
• Java^TM Servlets, version 2.2
  
  
• JavaServer Pages^TM technology, version 1.1
  
  
• JDBC^TM Standard Extension, version 2.0
  
  
• Java Naming and Directory Interface^TM API, version 1.2 (CosNaming SPI)
  
  
• RMI/IIOP
  
  
• Java^TM Transaction API, version 1.0
  
  
• JavaMail^TM API, version 1.1
  
  
• Java^TM Messaging Service, version 1.0 (API only, no implementation)
  
  

Required Software

The Java^TM 2 SDK, Enterprise Edition (v 1.2.1) requires the versions of the Java^TM 2 SDK, Standard Edition listed in the following table:

TABLE 0-1 Required Versions of the Java^TM 2 SDK, Standard Edition (J2SE)

Operating System	J2SE Version
SolarisTM Operating Environment	1.2.2_05 Production Release
Windows NT	1.2.2 or 1.3.0

Versions of the Java^TM 2 SDK, Standard Edition not listed in the preceding table have not been tested and are not supported.

Current Limitations

Container-Managed Persistence

• The entity bean class may be mapped to only one table in the database.
  
  
• A container-managed field may be mapped to only one column in the table.
  
  
• When the container loads the container-managed fields from the underlying database, it loads all of them. If the amount of data loaded is large, this approach may be inefficient because a business method may not need all of the container-managed fields.
  
  
• If the container-managed fields of multiple entity beans map to the same data item in a database, and if these beans are invoked in the same transaction, they may see an inconsistent view of the data item.
  
  
• The Application Deployment Tool generates SQL statements for the ejbCreate, ejbRemove, ejbLoad, and ejbStore methods. You may modify only the table and column names of these SQL statements. You may not modify the number and order of the question marks, which are place holders for the input parameters.
  
  
• You cannot call stored procedures in the generated SQL statements.
  
  
• In the "Create Table" SQL statement, you may change the SQL type of a table column provided that the SQL type is compatible with its corresponding instance variable.
  
  
• The table and column names in all of the SQL statements must be consistent.
  
  
• The generated SQL statements have been tested with these types of databases: Cloudscape, Oracle, and Microsoft SQL Server. You may need to edit the generated SQL statements to satisify the requirements of your database.
  
  

Database Calls During Result Set Iteration

String query = "SELECT DEPTNO FROM DEPT . . .";
String update = "UPDATE EMPLOYEE . . .";
ResultSet rs = stmt.executeQuery(query);
while (rs.next()) {
   String s = rs.getString("DEPTNO");
   // The following statement will FAIL:
   stmt.executeUpdate(update);
   . . .
}

1. Use a stored procedure that contains the same SQL calls.

2. Substitue the iteration with a single SQL statement that contains a subquery. Here's an example:

String update = "UPDATE EMPLOYEE
    SET DEPTNO =
      (SELECT DEPTNO FROM DEPT
       WHERE LOC = `ATLANTA')
   WHERE TITLE = `ENGINEER'";

Scalability and Memory Requirements

Common Development Environment

Redeployment

RMI-IIOP and JAXP Standard Extensions

Known Bugs

Differences Between Tomcat and the J2EE^TM SDK

Copyright © 2000 Sun Microsystems, Inc. All rights reserved.