Web Tools Platform 1.0M9 Release - New and Noteworthy for Web Services Tools


Below you will find details about enhancements to the Web services tools in 1.0M9.

Here are the highlights of the changes to the Web services tools for 1.0M9:

  • The Web service and Web service client creation framework had been updated to be based on project facet. The support for multiple modules per project had also been removed from the framework and from the Web service and Web service client wizards. Refer to the design document for enhancement 108595.
  • The user can create bottom-up Web service, top-down Web service and Web service client using Ant task. Refer to 98921 for more detail. Refer to the Web Service Ant Tasks tutorial for instructions on how to use the Ant tasks.

Aside from the items listed above, the focus has been on stabilizing existing function since WTP 0.8 milestone.


The following tutorials demonstrate functionality of the Web Services tools in the 1.0M9 release:

Known Problems

  • Please be aware of the following known problems when using the Web Services tools.  See the associated Bugzilla defect for further details.
    • 113933: When creating a Web service, you might get "Error occured when adding the module, null, to the server". Simply dismiss the error dialog and continue since the Web service scenario is successful despite the message.
    • 114852: When specifying Test Web service when going through the Web service or Web service client wizard, you might run into an intermittent problem where the generated sample JSP does not compile. The workaround is to restart the server manually and refresh the sample JSP page.
    • 102117: When creating a Web service, you might get "Error when deploying Web service to Axis runtime" when the component/project containing the Web service had already been added to a started server. The workaround is to restart the server manually before going through Web service wizard.
    • 117742: When creating a Web service or Web service client using the Tomcat 4.1 server, if the Web project do not already exist, you will get "Error occured when adding the module to the server". The workaround is to manually create the Web project first before going through the Web service wizard. When using the dynamic Web project wizard to create the Web project, hit Next to go to the second page and manually choose dynamic Web module version 2.3.
    • 117073: When creating a bottom-up Web service, if the compiler compliance level of the Web project containing the service bean is not at the same level as the JRE used to launch Eclipse, you might get "Error in generating WSDL form Java: java.lang.ClassNotFoundException". Change the compiler compliance level of the Web project by right-clicking on the project, select Properties -> Java compiler and select a compiler compliance level that matches with the JRE used to launch Eclipse.
    • 85823: When creating a Web service from Java bean, if you specify Generate proxy and Test the Web service, compilation errors may show up in the server console the first time the server is started complaining about "package org.eclipse.jst.ws.util does not exist". This is a timing problem because webserviceUtils.jar, which contains the class org.eclipse.jst.ws.util.JspUtils, is not added to the WEB-INF/lib directory of the Web project in time for the JSP compile. Despite the error, eventually the sample JSPs come up OK and the Web service can be invoked successfully. 
    • 92429: The Web Services Explorer does not work with the Netscape browser. Change the default Web Browser by using Window -> Preferences -> General -> Web Browser
    • 86552: If the service name in the WSDL file used in Web service client scenario does not follow Java naming convention, e.g. having a lowercase first letter, the Proxy class generated by the Web service client wizard may not be able to correctly reference the generated type and may have compile errors. 
    • 99728: The Axis 1.1 runtime included in WTP is configured to support creation of Web services in projects targeted to Apache Tomcat or Geronimo. The Web service wizard will fail with "IWAB0234E An internal error occurred. Details: null java.lang.IllegalArgumentException" if the selected artifact, be it a Java bean or WSDL file, is contained in a project with a runtime target other than Tomcat or Geronimo.
    • 117138, 103999 : The Geronimo 1.0 Server is enabled for the Web service wizard but not yet fully functional due to these significant defects.
    • 105090: Sample JSP launches with incorrect URL on SLES 9.0 when using the default browser "Konqueror". The workaround is to manualy update the URL starting with "http:/localhost" to "http://localhost".
    • 105611: When running Web services scenarios, you might get a warning in the Tomcat console with the warning that "Attachment support is disabled". This is expected and would not affect the running of the Web service.
    • 105459: When creating Web service using Tomcat 4.1, if the server does not already exist, there may be an intermitten problem of "Error in starting server". The workaround is delete the Tomcat 4.1 server created by the Web service wizard, create a Tomcat 4.1 server manually before launching the Web service wizard.
    • 105089: The Web Service Explorer may run into error opening WSIL files containing Japanese characters. You might get an error indicating that the document "is not a valid WSIL URL or HTML URL" or corrupted characters in the Web Service Explorer WSIL page summary table.
    • 105087: The Web Service Explorer is unable to publish objects with non-English name.
    • 106239: When using the Web Services Explorer with the IBM UDDI Test Registry to add business assertions, you might get an error message stating that the business in not owned by you.
    • 104993: When creating bottom-up Web service, you might get the exception:
      Unexpected exception occured. Detail: java.lang.NoClassDefFoundError: javax/activation/DataSource.
      Refer to comment #8 of the defect for workarounds.
    • 116025: The Web services Server Runtime preference page currently displays all server types in the "Server" combo box and all Web service runtimes in the "Web service runtime" combo box, instead of filtering them so that only compatible combinations appear. This means the user would be allowed to make an invalid selection without being stopped.