IBM^® WebSphere^® Studio Site Developer Interim Fix 007

for WebSphere^® Studio Site Developer, Version 5.1.2

This refresh contains fixes for problems in the following components:

• Web Services
• J2EE Tools
• Web Tools
• Data Tools
• EGL Tools
• Java Tools

This refresh also contains previous fixes from interim fix 006. To view the IBM WebSphere Studio Site Developer Interim Fix 006 readme file, go to this Web address: www3.software.ibm.com/ibmdl/pub/software/websphere/studiotools/html/Interim_Fix006/wssd512/readme.html

Web Services

• WSDL validator problem
  This fixes the following problem with the WSDL validator where a WSDL document with an inline schema which declares a value=":" may be incorrectly flagged as not valid.
   
• Enhancement to WSDL2WebService and WSDL2Client command line tools
  This change enhances the WSDL2WebService and WSDL2Client command line tools by exposing the WebSphere WSDL2Java command's -noWrappedOperations extended flag.
  


• Java and XML code generator upgrade
  The Java and XML code generators in the Web services tools in WebSphere Studio Application Developer have been upgraded based upon the Java2WSDL and WSDL2Java emitters from WebSphere Application Server 5.1.1 Cumulative Fix 3 (5.1.1.3) plus interim fix PQ97028.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 WebSphere Studio Application Developer bin/ directory (WSDL2WebService, WSDL2Client, etc).
  
  Further details about the WAS v5.1.1.3 cumulative fix is available at this site:
  www.ibm.com/software/webservers/appserv/was/support/
  


• Backing up and overwriting a skeleton Java bean
  If a Web service Java skeleton is generated, any previous version of this class will be backed up with a .bak extension. This behavior can now be switched on or off via the new "Do not backup and overwrite skeleton Java bean" Web Service preference.
   
• WSDL editor problem
  This fixes the problem where the WSDL editor had difficulty handling a WSDL file which had no prefix for the targetnamespace (component names are not qualified). This led to the following known problem: The connecting lines (binding -> operation -> messages) in the graph view do not appear.
  


• WSDL validator problem
  This fixes the following problem with the WSDL validator where an inline schema in a WSDL document with no specified target namespace is not assigned the default namespace of the WSDL document. The fix assigns the namespace of the WSDL document to the inline schema.
  


• WSDL validator problem
  This fixes the following problem with the WSDL validator where a WSDL document that contains a schema import with a schema location that is not valid, may not be flagged as an error or warning by the WSDL validator.
  
  
• Deploying Web services with a large number of files
  This fixes the problem where deploying applications with SOAP/Web services and a large number of files fails to deploy correctly.
  
  
• WSDL editor problem
  This fixes the problem in the WSDL editor where changing the schemaLocation of an imported schema defined in the inline schema of a WSDL does not update the WSDL file properly. The available types and elements of the previously imported schema are still available for use (in the WSDL editor) while the types and elements defined in the newly specified imported schema are not available.
  
  
• WSDL editor problem
  This fixes the problem in the WSDL editor where after deleting the types section, the WSDL editor behaves erratically. For example, the editor does not recognize that changes have been made to the WSDL file and will subsequently close without prompting a save.
  
  
• WSDL validator problem
  This fixes the following problem with the WSDL validator where a WSDL document with an inline schema that contains a restriction pattern with the ":" character may incorrectly be reported as not valid.
  
  
• Incorrect beans generated for arrays of complex types
  This change corrects a previous regression on WebSphere Studio Application Developer IntegrationEdition where incorrect beans were generated for arrays of complex types.

J2EE Tools

Ant errors
1) The plugin.xml is changed to eliminate headless ant error about ReadWebpage or ReadTargetsFile
2) projectBuild+workspaceBuild correctly restores DEBUG setting
3) linux runAnt.sh+buildExample.sh correctly handles CurrentDir="."

Web Tools

• JavaServer Faces unable to display yen symbol
  This fixes the problem where the Yen sign symbol was unable to be specified in the JSF inputText field.
  
  
• JavaServer Faces performance problem
  This fixes a performance problem that was occurring when using advanced features of some JSF JSP components (e.g. data table pager) and the Tivoli Access Manager (TAM) was installed and running on the server.
  


• Struts OutOfMemory error
  This fixes a problem where an Out of Memory error can occur when validating links in a Struts Web project. On certain Web projects with a web.xml that contains many <init-param> tags listed under the Struts servlet, during a project build a dialog box may appear saying that an Out of Memory error has occurred.
  


• h:messages error
  This fixes incorrectly rendered HTML when h:messages attribute layout="table" is set.
   
• Nested data tables error
  This fixes the problem of incorrect ids rendered for data tables nested within data tables and the resulting incorrect behavior of contained components.
   
• Lost data in a data table when an input field fails validation
  This fixes the problem of losing data entered into a data table when a input field outside of the data table fails validation.
   
• hx:panelBox error
  This fixes the problem of when hx:panelBox contains components that have their 'rendered' attribute set to 'false', unnecessary empty table cells are rendered at runtime.
  
  
• JSP batch compile problem
  This fixes the problem when using the jspbatchcompile script to compile the JSP files beneath the web-module folder (WAR folder) of a WebSphere installed application (e.g., WAS/installedApps/node/...ear/...war), when more than one of the JSP files is a symbolic link.
   
• Rendering of hx:graphicImageEx and hx:commandExButton
  This fixes the rendering of components hx:graphicImageEx and hx:commmandExButton where rendered img or input HTML tags were not closed.
  
  
• JSF InputText problem
  This fixes the problem with inputText of currency type with input assist enabled where negative currency values are not formatted correctly.
  
  
• JSF CalendarPicker not working
  This fixes the problem of the CalendarPicker not working.
  
  
• JSF InputText problem
  This fixes the problem of when input assist is on for an inputText of currency type and a value is entered and then deleted where the currency symbols remain and cannot be deleted.
  
  
• Performance problem when loading JavaScript
  This fixes the problem where if the context path is encoded, a performance problem is encountered when loading JavaScript resources.
  A context-param named com.ibm.faces.USE_UNENCODED_CONTEXT_PATH can now be added to the web.xml file to specify the context path of a Web application to work around the resource caching problems caused by encoded context paths. For example:
  

  <context-param>
    <param-name>com.ibm.faces.USE_UNENCODED_CONTEXT_PATH</param-name>
    <param-value>\appname</param-value>
    </context-param>
    

  The value for this param can be either:
  - a context path string e.g.<param-value>\project1</param-value>
  - a number to specify the number of nodes to use from the encoded context path starting from the left
  For example,  if the context path is /screen/faces/SSID1102675496962q-XhOlSRS1mYr1sP03cgIfj/RID1102676009061 and <param-value>1</param-value> the context path will be evaluated as /screen.
  

Data Tools

• Cannot retrieve views from DB2 v7 on zSeries
  This fixes the problem where you cannot retrieve views having "WITH CHECK OPTION" in their syntax from DB2 v7 on zSeries.
  


• Informix database problem
  This fixes the problem where the FK columns order was incorrect after loading an Informix database
  

EGL Tools

• EGL Debug exception
  This fixes the problem where an exception occurs in EGL Debug when executing a call to a remote program when conversionTable = *
  
  

Java Tools

• Java model access
  Changes in a dependent API for Java model access require an update to the way classes are reflected in the model access code. Without the update, model access can result in errors, with messages that complain about a closed zip file. This patch corrects the Java model access code.