IBM WebSphere Studio Application Developer Interim Fix 003

for WebSphere Studio Application Developer, Version 5.1.0



This refresh contains fixes for the following problems:

Server tools

  1. When exceptions were displayed in the console during the server run-time, they did not contain hyperlinks that took you directly to the source of the problem (as they did in WebSphere Studio v5.0). The hyperlinks have now been restored for all server types.

  2. The application client launcher for WebSphere Application Server - Express did not use the correct JRE located under express_v5\java. This ifix fixes this problem.

  3. After importing a RAR file into a connector project, you would not be able to configure the RAR file as a standalone connector in the J2C page of the WebSphere v5.0 server configuration editor. This ifix enables you to configure and run the RAR file as a standalone project.

  4. After saving a WebSphere Studio v5.0 configuration in the configuration editor, sometimes a dialog would appear indicating that the configuration had now changed on the filesystem. This dialog appeared because the configuration files were not closed immediately after they were saved. With this ifix, the files will now close correctly and the dialog will not appear.

EJB deployment

  1. The types for the keys in 390 were too large when using the default varchar sizes on Top-down generation. They have been reduced from 250.50
  2. The SQL generation of a recursive bidirectional 1:1 navigation finder did not work properly. This is now fixed.
  3. The char regression in the query engine on the z/OS platform did not work properly. This is now fixed.
  4. The error level returned by the batch deploy was zero in certain cases where the batch deploy reported problems. This incorrect error level led to undesired results. This has now been fixed.
  5. PreparedStatement objects were leaked when root-leaf inheritance with multiple tables were used. This adversely affected the performance (execution time and memory requirements) of the deployed application. This has now been fixed.
  6. The SELECT statement for finder methods contained CASTs that are not supported on DB2 OS/390. Specifically, using CAST as BIGINT causes SQL -473 error. This error no longer occurs.
  7. Previously, the code generated by the EJB deploy did not reset the cached attribute values of the base class (this problem occurs when a root leaf inheritance is used). As a result when subsequent create/update operations were performed on instances of the same EJB class, old values from prior instances of the same EJB class were persisted in the data store for those attributes for which no values were specified in the new instance. This is now fixed.
  8. Previously, the fully qualified name of the log file was not specified in the error message dialog that appeared when problems occurred during the rmic code generation phase of ejbdeploy. The fully qualified filename of the log file is now specified in this dialog.
  9. When the RMIC error occurred , the error information was not captured to any file . This is now fixed by sending it to the .log file.

Debugger tools

  1. Previously, when the default debug editor was used for all compiler languages other than JAVA, you could not scroll past line 100 of the source files. As well, the file compare support in the editor would cause a crash when used. The ifix fixes both of these problems. Also, the user and API documentation has been updated to describe the revised Lpex class structure.

Documentation

  1. The Getting Started documents have been updated to reflect the most up- to-date list of What's New items.

  2. This fix includes updates to the translated versions of the product documentation for Component Test in Japanese, Korean, Simplified Chinese and Traditional Chinese. Please note that it is recommended for users to use Internet Explorer version 6.0 or above as some documentation based in HTML will not show up in previous versions of IE.

  3. This fix includes updates to the translated versions of the product documentation for EJB and Java UML visual editing in Japanese, Korean, Simplified Chinese and Traditional Chinese. Please note that it is recommended for users to use Internet Explorer version 6.0 or above as some documentation based in HTML will not show up in previous versions of IE.

Data tools

  1. When using EJBDeploy from the command line, relational database table DDL files were not properly exported to the output EAR file. This is now fixed.

EJB tools

  1. When creating a Copy Helper or a Java Wrapper Access Bean the constructor method that was being used to generate the Access Bean class was not the correct method that the user selected in the wizard. This was causing constructors with the key object and the init args not getting generated. This is now fixed

  2. There was restriction for 1.1 beans that the field names of the composer target class needed to match the field names described in the composer class. This has now been lifter.

  3. Unqualified bean class names were being generated in finder methods within the home implementation class of BMP beans. The problem surfaced when the interface and bean class were in different packages. This is now fixed.