IBM^® WebSphere^® Application Server - Express Interim Fix 008

for WebSphere^® Application Server - Express, Version 5.1.1

This interim fix contains fixes for problems in the following components. APAR numbers, if applicable, are included in parentheses:

• EGL tools
• J2EE tools
• Server tools
• Web services
• Web tools
• XML tools

This interim fix also contains previous fixes from interim fix 007 and interim fix 006.

To view the IBM WebSphere Application Server - Express Interim Fix 007 readme file, go to this Web address: www3.software.ibm.com/ibmdl/pub/software/websphere/studiotools/html/Interim_Fix007/wasexpress512/readme.html

To view the IBM WebSphere Application Server - Express Interim Fix 006 readme file, go to this Web address: www3.software.ibm.com/ibmdl/pub/software/websphere/studiotools/html/Interim_Fix006/wasexpress512/readme.html

EGL tools

• (JR21174) This fixes a problem where EGL Java generation causes a null pointer exception when SQL SELECT condtion contains anything other than column names, and no INTO clause is specified. This case is now restricted during validation. Improper Java code is generated if a program variable is passed as argument to a user-defined routine.
• (JR21388) This fixes a problem in EGL Forms where the shift key does not modify function keys. Shift+F1 should act as F13, but it acts as F1.
• (JR21405) This fixes a problem where EGL generated code does not release cursors when using an Oracle database.
• (JR21503) This fixes inconsistent behavior when using a command hyperlink in an EGL page handler application.
• (JR21517) This fixes a problem where printing to a file when fields contain trailing whitespace results in output data positioned incorrectly.
• (PK04735) This fixes a NumberFormatException in an EGL page handler when the input string is "".
• (JR21552) This fixes a problem in EGL page handlers where transferring to a program in a different package does not work.
• (JR21608) This fixes a problem where a VAGen SQL statement is migrated incorrectly when "?" is used in a SQL SELECT clause.
• (JR21833) This fixes an error in EGL Java generation when '?' is used in a SQL SELECT clause.
• (JR21633) This fixes the debug error WN.DBG.0102.
• (PK05905) This fixes the duplicate class name error when running a distributed build for a program that contains an EGL data table.
• (JR21878) This fixes a problem where an EGL library part generates a Java method larger than the 65K limit.
• (JR21925) This fixes a problem in EGL page handlers, where if a check box is bound to a control that has paging, the check box selection is lost when you page forward. Once you have applied this interim fix, you must perform the following steps:
  1. If you are using a Web project, remove the EGL runtime jar files, fda.jar and fdaj.jar, from the project lib folder.
  2. Copy the new EGL runtime jar files from the plugin folder, install_dir\egl\eclipse\plugins\com.ibm.etools.egl.generators_5.1.2.n\runtime, to the project lib folder. (Note: choose n with the highest integer value in the plugin folder which corresponds to the latest version of the interim fix.)
  3. Regenerate the EGL page handler programs.
• (PK04938, PK04987)This fixes an Index out of range exception in stage 2 of VAGEN to EGL migration.

J2EE Tools

• This fixes a problem where the StringBuffer.append(StringBuffer) method is not found on JDK 1.3.
• This fixes an import problem in which the Import WAR operation was throwing exceptions when importing into a workbench with existing closed Web projects.
• This fixes a problem during binary WAR imports in which WAR import files were failing to be saved when they have extremely similar names (example AutoLogin.xml and Login.xml) This fix insures the proper importing of all files in the archive.
• This adds a checkbox to the Project Interchange export wizard to allow you to specify whether or not you want to export derived files in the Project Iinterchange file.The default is set to false.
• This fixes some issues concerning normalization of URIs.

Server tools

• This fixes the following problem of WebSphere Application Server v5.0 JAR files being added to the build path of a Java project during creation of a Web service client even when the selected server is a WebSphere Application Server Enterprise Edition V5.1 test environment and server targeting is enabled. With this fix, the JAR files from the WebSphere Application Server Enterprise Edition V5.1 test enviroment or server are put on the build path of the Java project.

Web services

• This fixes the following problem where nothing would happen when a you elected the Deploy Web service action on a WSDL file that imports another WSDL file.
• The Java and WSDL/XML code generated by the Web services tools is produced by the Java2WSDL and WSDL2Java emitters from WebSphere Application Server. The emitters have been upgraded from 5.1.1 Cumulative Fix 3 (5.1.1.3) to 5.1.1 Cumulative Fix 5 (5.1.1.5). This upgrade applies to the Web services wizards and related tools found in the graphical user interface only. This upgrade does not apply to the command-line tools found in the bin directory, for example the WSDL2WebService or the WSDL2Client, etc)
  Further details about the WebSphere Application Server v5.1.1 cumulative fixes, including fixes made in 5.1.1.4 and 5.1.1.5, is available at this site:
  www.ibm.com/software/webservers/appserv/was/support/ 
• This fixes the problem when an XML escape character such as &, <, >, in a Web Service request/response does not handle the data correctly.
• This fixes the regression introduced in interim fix 007 where when loading a WSDL model, imports within inline schemas are not resolved correctly. This problem presents itself as though schema structures are incorrect. Where you would expect to see a referenced element, you will only see a string type. This is often made visible by code generators or other tools that process an inline schema and provide some viewable artifact.
• The following limitations in the Web Services Explorer, specifically its support for invoking operations declared in WSDL documents, have been fixed. In all of these cases, the observable symptom is that
  some or all of the input form for a given WSDL operation and the complex input type it uses would be absent:
  1. The Web Services Explorer does not handle XML Schema documents that do not have a target namespace.
  2. The Web Services Explorer does not handle complex types that extend a complex type from another namespace.
  3. The Web Services Explorer does not support element attributes.
  4. The Web Services Explorer does not support nillable elements
  Entry fields will now be rendered within the input form for the types and type structures noted above. Furthermore, for #3, a new Nill checkbox will show up in the input form next to fields for elements that are declared with nillable="true" in the schema.
• This fixes the following problem: When the WSDL2Java emitter is run, the default timeout (45 seconds) may not be long enough for code generation against a WSDL file with large number of data types. This may result in a runtime exception in the Web service wizard and the Web service command line tool without any workaround. This problem is addressed by removing the timeout period completely.

Web tools

• There is a problem when BeanInfo Introspection is done on an interface that extends more than one interface. The symptom is that wizards that are trying to do this fail and there is a log msg in the LoggingUtil.log about NullPointerException in the BeanInfoClassAdapter class.
• This fixes the problem of DataTable's Row Action component storing previously clicked DataTable rows and incorrectly executing their actions again on subsequent clicked rows.
• This fixes the problem where DataTable's pager components show the incorrect page number when the number of pages has decreased to below that of the current page, as may happen with a search query resulting in fewer DataTable pages displayed.
• This fixes the problem where DataTable's pager component may become inaccurate if dynamically setting DataTable's 'first' attribute, for example, a row action that sets the selected row as first may have this problem when using the pagers previous or next actions.

XML tools

• This fixes the problem where the DTD to XSD transformation is not performed properly when multiple space characters are followed by "<!ENTITY" in a DTD file. For example:multiple space characters are followed by <!ENTITY in a DTD file. For example:
  <!ENTITY % InheritanceAccount "(AssetHolding|MonetaryAccount|Reserve|UnitHolding)">