IBM WebSphere Studio Application Developer Interim Fix 001

for IBM WebSphere Studio Application Developer, Version 5.1.0



This refresh contains fixes for the following problems:

Web Services tools

  1. The Web service wizards no longer allowed you to create an Apache/IBM SOAP v2.3 Java proxy or Java bean skeleton from WSDL documents without a <service> endpoint. A similar limitation in the wizards for the WAS v5.0.2 Web services runtime remains, and will be addressed in a later release.

  2. The "-fileNStoPkg" option of the WSDL2WebService command tool did not work. The option will now correctly accept and process a mapping properties file with customized namespace-to-package mappings.

  3. If you followed a bottom-up or top-down WAS v5.0.2 Web services scenario with proxy generation enabled, and clicked "Finish" immediately after selecting a security configuration for the service (ie. without clicking "Next"), the wizard would not create the security configuration for the client side. This would result in the client and service being unable to connect.

  4. By default, the ejb-name of an EJB created in Studio is the same as the base name of the EJB interface. However, if and only if the EJB's ejb-name happens to differ from its interface basename, the Web services wizard, in a bottom-up EJB scenario for WAS v5.0.2, will emit an incorrect ejb-link value into the Web services deployment descriptors. This in turn will prevent the EJB-based Web service from starting.

  5. In the Web services creation wizard, using the "Back" and "Next" buttons to flip between the second and third pages would yield new, unwanted Server configurations and also lead to an internal exception within the wizard.

  6. In the Web services client wizard, your choice of runtime selection would usually be altered if you pressed "Next" to leave the page, then "Back" to return to the page.

  7. If you already had a Server named "WebSphere v5.0 Test Environment", then the Web service wizard would not allow you to create a new WebSphere v5.0 Test Environment server. This has been fixed. The wizard will now allow you to create a new server, and will choose a new, unique, name for the server (eg. "WebSphere v5.0 Test Environment (2)".

  8. The Web services wizard automatically configures the Web or EJB "router" projects necessary to route Web service traffic to an EJB in an EJB project. In non-trivial workspaces, the wizard would often choose or incorrectly name the router project, or assign the router project to the incorrect EAR (that is, to an EAR other than the one containing the EJB project). The wizard has been fixed to choose or name router projects correctly in virtually all cases, to configure them into the appropriate EARs, and to block progress with an error message whenever incompatible router and EJB projects are selected in the wizard.

  9. In WAS/Express on Linux only, no Server is selected by default. This has been fixed. An available and supported server, such as "WebSphere Express v5 Test Environment", will be selected by default.

  10. In WAS/Express on Linux only, when a Java bean is pre-selected in the workspace, the Web service creation wizard did not choose the "Java bean Web service" type by default.

  11. The "Finish" button was not enabled on the first page of the Web service client wizard when beginning with a selected WSDL file in the workspace. The button is now enabled, allowing you to finish the wizard without having to first hit "Next" one or more times.

  12. In an EJB top-down scenario for the WAS v5.0.2 runtime, if you pressed Finish on the second page and your EJB project did not yet exist, the wizard would fail to publish the Web service EAR to the server.

  13. When generating two or more Web service clients into the same module, all but the most recently generated client were deleted from the webservicesclient.xml deployment descriptor, preventing all but the most recently generated client from functioning in a container-managed environment (as signified by looking up a Web
    service via JNDI). This has been fixed. Multiple Web service client references are merged together in webservicesclient.xml.

  14. Various errors were produced incorrectly by WebSphere Studio's WSDL Validator for valid MIME binding elements in a WSDL document. These errors in turn prevented the generation of HTML documentation from the WSDL.

EJB Tools

  1. Fix to allow the option to generate a copy helper for the key attribute of a CMP during Access Bean generation. The key attribute needs to have getter method on the bean class of the CMP to get this option in the AccessBean Creation Wizard.

  2. Duplicate entries for "Container" are shown in the ResourceReference wizard available from the References page of the EJB Deployment Descriptor Editor. With this fix there will be only 2 Authentications type ("Container"," Application") available in the Authentication drop down.

XML tools

  1. The SOAP Encoding namespace is now imported automatically in WSDL documents for use anywhere in the document including inline schemas. Reciprical import statements in inline schemas defined in WSDL documents are now allowed.

  2. If, in the source view of the XSD Editor, you position the cursor on a reference to a global component and you press 'F3', the editor's context will switch to the component's declaration in the source. For example, the source view will scroll to the appropriate line where the component is declared. If the reference is in another schema in the workspace, a new editor will be opened.

Page Designer

  1. Page Designer fails to preview when JavaScript is faulty