Java TM 2 SDK, Enterprise Edition 1.3_01 Release Notes
1. Read the Installation Instructions to find out how to set the J2EE_HOME and JAVA_HOME environment variables. The Installation Instructions are on our web site and may be reached by a link on the J2EE SDK download page.
2. Install the software that the Java TM 2 SDK, Enterprise Edition relies on. See the Required Software section of this document.
JDBC Data Access APIJDBC Technology Drivers
j2eeadminutility adds JDBC drivers, JMS destinations, and connection factories for various resources.
The deploytool utility packages J2EE components and deploys J2EE applications.
The keytool utility creates public and private keys and generates X509 self-signed certificates. The J2EE SDK version is a wrapper for the J2SE SDK version, but adds a Java Cryptographic Extension provider that has implementations of RSA algorithms (licensed from RSA Data Security).
realmtoolutility manages users for the J2EE server.
verifierutility validates J2EE component files.
packagerutility packages J2EE components.
cleanuputility deletes all deployed J2EE applications.
Note: Versions of the Java TM 2 SDK, Standard Edition not listed in the preceding table have not been tested and are not supported. For example, J2SE v. 1.2 will not work with this release of the Java TM 2 SDK, Enterprise Edition.
In J2SE 1.3.1, an
OutOfMemoryError can result when a very large number of Java classes are loaded by the JVM, even when there are free spaces on the Java heap. Workaround: Edit
bin/setenv.bat to add the following option to the JAVACMD variable:
Note: The Tomcat implementation in the J2EE SDK might be slightly different from the version of Tomcat 4.0 distributed separately because of different release schedules. For more information about Tomcat, please see http://jakarta.apache.org/.
The j2ee-ri-svc.jar file is located in the lib directory of the J2EE SDK installation. It contains portable system value classes such as implementations of javax.ejb.Handle and javax. ejb.EJBMetaData. These implementations are specific to the J2EE SDK.
For more information on EJB container interoperability, please refer to section 19.2 of the Enterprise JavaBeans 2.0 Specification. A link to the Specification may be found on the J2EE SDK download page.
Note that the persistence manager in the J2EE SDK only supports forward mapping of a CMP 2.0 abstract schema to a relational database. Using the J2EE SDK's tools, it is not possible to reverse map from existing database tables to a CMP 2.0 abstract schema.
| Operating System
| J2SE Version
|Solaris TM 7, 8||1.3.1_01|
| Windows NT 4.0,
Windows 2000 Professional
|Linux Red Hat, v. 6.2||1.3.1_01|
| Bug ID
|4365998||The Update Files function in the DeployTool no longer works after the display name for an Application is changed. Workaround: Update each file individually and re-add the new files to the contents of the EJB/Web/App bundle.|
|4412002|| A deployed J2EE client on Windows or Solaris cannot connect to J2EE on a default installation of Red Hat Linux. The Red Hat Linux method
|4461245||The SQL generator in the DeployTool generates database table names for storing the persistent state of CMP EntityBeans based on the bean class name. If there are two or more beans with the same bean class name (in the same EAR or in multiple deployed EARs), the table names will conflict. Workarounds: use different datasources for storing beans in different EARs. Or, change the table names in the generated SQL statements in the Deployment Settings dialog for EntityBeans.|
|4491857|| The PageContext.include() method does not perform a flush. To be portable,a tag library implementation should not rely on flush being performed by the web container. Workaround: Perform an explicit flush (e.g.