Java TM 2 SDK, Enterprise Edition 1.3.1 Release Notes
1. Read the Installation Instructions to find out how to set the
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.
3. Go to the J2EE Tutorial to learn how to use the J2EE SDK.
multiplicityelement for relationships in the XML deployment descriptor for Container Managed Persistence (CMP) 2.0.
queryelement in the XML deployment descriptor for CMP 1.1 entity beans (still supported for compatibility), which do not have the query feature of CMP 2.0 entity beans.
container-transactionelement in the XML deployment descriptor for the
getHandlemethod of entity beans.
JDBC Data Access APIJDBC Technology Drivers
After you've installed your driver, follow the instructions in the JDBC Drivers section of the Configuration Guide to configure the driver for use with the J2EE SDK. If you are using the Cloudscape DBMS included in this release, you do not have to configure its driver.
See the section New Treatment of Non-XA Data Transactions, for additional driver related information.
j2eeadminutility adds JDBC drivers, JMS destinations, and connection factories for various resources.
deploytoolutility packages J2EE components and deploys J2EE applications. In the 1.3.1 release it receives an enhanced update function and intelligent field completion.
keytoolutility 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 an option for the format conversion of PKCS12 certificates.
realmtoolutility manages users for the J2EE server.
verifierutility validates J2EE component files.
packagerutility packages J2EE components.
cleanuputility deletes all deployed J2EE applications.
In the J2SE 1.3.1 softeare, an
OutOfMemoryError can result when a very large number of classes are loaded by the Java virtual machine, even when there are free spaces on the Java heap. Workaround: Edit
bin/setenv.bat to add the following option to the
Note: The Tomcat implementation in the J2EE SDK might be slightly different from the version of Tomcat 4.0.2 distributed separately because of different release schedules. For more information about Tomcat, please see http://jakarta.apache.org/.
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.
Files that have not been found are listed in the lower half of the dialog, under Entries Not Found on Disk. Files can be moved into the found category by editing the search path so that they will be located by the program.
Note: Database drivers that support XA data-sources allow you to connect to multiple databases and to distribute transactions across machines or processes. JDBC 1.0 drivers do not support XA data sources. Some JDBC 2.0 drivers support XA data-sources and some do not. See the Configuration Guide for information about the installation of XA and non-XA drivers.
A local transaction is restricted to the use of exactly one non-XA data-source and to transactions that are completed within one Java virtual machine. Thus, a global transaction is not started and there is no need to go to the JTS layer. The resulting optimization results in a vast improvement in performance of begin/commit operations. With a local transaction there is no need for two-phase commits. The use of multiple non-XA data-sources or multiple Java virtual machines would require two-phase commits.
Breaking out local transactions will allow many uses of non-XA data-sources to be optimized. When two non-XA data sources are needed, they can be used by declaring them to be XA data sources in the J2EE SDK's
If more than one resource is used in a transaction, non-XA data sources must not be used. (Examples of resources are relational databases accessed through the JDBC API, JMS queues and topics, and EISs accessed through the J2EE Connector architecture.) Instead, all resources must support XA transactions. It is illegal to use more than one non-XA data source in the same transaction.
| Operating System
| J2SE SDK Version
| Solaris TM 7 Operating Environment
Solaris TM 8 Operating Environment
|1.3.1_02 or 1.4|
| Windows NT 4.0,
Windows 2000 Professional
|1.3.1_02 or 1.4|
|Linux Red Hat, v. 6.2||1.3.1_02 or 1.4|
| Bug ID
|4461245||The SQL generator in the deploytool generates database table names for storing the persistent state of CMP entity beans. The table name is 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 entity beans.|
|4533469|| RMIC generates an incorrect stub when compiling an EJB remote interface of the following form:
This bug only occurs when the method name is of the form
|4613829|| On Windows, the
|4625512|| With the command-line version of