Java TM 2 SDK, Enterprise Edition
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.
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.
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.
JDBC Data Access APIJDBC Technology DriversJDBC Drivers
deploytoolutility packages J2EE components and deploys J2EE applications.
realmtoolutility manages users for the J2EE server.
verifierutility validates J2EE component files.
packagerutility packages J2EE components.
cleanuputility deletes all deployed J2EE applications.
| Operating System
| J2SE Version
|Solaris TM 7, 8||1.2.2_05 or 1.3.0 Production Release|
| Windows NT 4.0,
Windows 2000 Professional
|1.2.2_005 or 1.3.0 Production Release|
|Linux Red Hat, v. 6.0, 6.1||1.2.2 or 1.3.0 Production Release|
| Bug ID
|.|| A bug in the Java 2 SDK, Standard Edition 1.2.2 JIT causes Cloudscape to crash on the Solaris TM platform unless the environment contains the following:
|.||Before switching the J2EE server from non-recoverable to recoverable mode (for transactions), it is necessary to run the the cleanup script first.|
|.||J2EE clients and servers cannot interoperate with ORB products using the IIOP1.0 protocol (such as JavaIDL in Java 2 SDK v. 1.2). Workaround: Use an ORB product which supports the IIOP1.1 protocol (such as RMI-IIOP 1.0.1 standard extension).|
|.|| The entire Java 2, SDK, Standard Edition is required to run the J2EE software. The standard edition contains a JRE (Java Runtime Environment). On some systems, when installing the standard edition the user has the option of installing a stand-alone JRE. This separate JRE cannot be used to run the J2EE software . In addition, a problem can occur if the root directory of the stand-alone JRE is set to the root directory where the standard edition was installed. In this case, everything will appear to run correctly until you deploy an enterprise bean:
java.rmi.RemoteException: Error processing ejb jar:access denied:
(java.io.FilePermission e:\testjava\lib ext read)
|4330251||The server incorrectly resolves extension mapping. For example, when FooServlet is mapped to *.foo, it is invoked even when the request URI is /bar/foo/something. Workaround: Use the exact macthing wherever possible.|
|4333017||The web server of the J2EE SDK uses the operating system's default character encoding for converting bytes (received from HTML forms) to Java strings. If the browser sends strings in HTTP requests which are encoded using a different character encoding than the webserver, then the servlet or JSP code will see incorrect Java strings. (This error might occur if the HTML file received from the webserver has a different character encoding than the webserver.) Workaround: Obtain the bytes from the Java string in the servlet or JSP code and then create a new string from the bytes with the correct encoding.|
|4335409||Loading servlets at server startup may fail under certain conditions. The J2EE server can load a servlet and call a servlet's init method when the server is started, but the results are unpredictable. Such servlets include those that are registered in the web.xml file with a <load-on-startup> element.|
|4295863||In the New Enterprise Bean Wizard, if the wrong classes are chosen and you go back to correct them, sometimes the container-managed persistence attributes for the classes chosen do not appear correctly. Workaround: Either restart the wizard; or, change the type of the bean, move forward, move back, change the bean type back to entity, and re-choose the classes.|
|4313158||Applications with spaces in the application name cannot be deployed. Workaround: Remove the space from the application name.|
|4332122||While specifying the URI paths in the descriptor make sure that you specify the path from the context (paths starting with "/"). This will ensure that the correct page gets invoked no matter where you are within the application.|
|4333858||During the installation, if you don't have enough disk space available, this misleading error message may be displayed: "The download file appears to be corrupted." Workaround: Free up sufficient disk space.|
|4335414||For a component with a long list of contents, you may reach the limit on the length of a string allowable in the command-line arguments for the packager. Workaround: Package the helper classes into a library .jar file and add the .jar file to the application's .ear file.|
|4335750||In an entity bean with container-managed persistence (CMP), if you update the .class files of the home or remote interfaces with the Application Deployment Tool, the CMP Settings Panel will not automatically refresh. Workaround: Save the application, close it, and re-open it.|
|4337092||In table 9-11 of the J2EE Developer's Guide, the JNDI name for the HTMLReaderBean is incorrect. The correct name is MyHTMLReader.|