Please be aware of the following known problems when using the Web Services
tools. See the associated Bugzilla defect for further details.
Going through Web Service top down scenario on a WSDL file in a path containing
a space would result in an error:
Failed to copy WSDL file. Detail:
The workaround is to avoid using spaces or special characters not
allowed in java.net.URI as specified in RFC 2396: Uniform Resource Identifiers (URI):
Generic Syntax in the path where the WSDL file is located in
(e.g. installation directory, project and workspace name).
When the Browse... button is clicked in the Web Services Explorer to launch
the WSDL Browser to browse the WSDL files in the workspace,
no WSDL files are listed. The workaround is not to use Browse... button
but instead manually enter the WSDL location in the WSDL URL field.
When creating Web service, if you choose Test the Web service, you will need to select
Generate Proxy as well. Otherwise, if the client project does not already exist, you
will get the error:
Unexpected exception occured .
If this happens, you can either
create the client project manually before going through the Web service wizard or
select/deselect both options together.
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.
When going through the Web services wizard, you might run into an intermitten problem where
the error dialog "Errors during build. Resource .deployable does not exist" may pop up.
When that happens, just dismiss the dialog and continue.
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.
The Web Services Explorer does not work with the Netscape browser. Change
the default Web Browser by using Window -> Preferences -> General ->
Do not create bottom-up Web services from beans in the default package.
Otherwise, you will get "Error in getting method from bean" when going
through the Web Service wizard. Instead, put your service bean in a Java
package before creating a Web service from it.
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.
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.
The Geronimo 1.0 Server is enabled for the Web service wizard but not yet fully
functional due to these significant defects.
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
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.
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.
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.
The Web Service Explorer is unable to publish objects with non-English name.
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.
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.