|Below you will find details about enhancements to the Web
services tools in WTP 1.0.
Here are the highlights of the changes to the Web services tools since the WTP 0.7 release:
- 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
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
- A new page was added to the Web Service wizard to start the
server asynchronously. Refer to defect 107141
- The option to do wizard WSDL validation was added to Web Service
wizard for top-down scenario and Web Service client wizard. You can
enable it in the Web Service -> Profile Compliance and Validation preference.
Refer to 107673
for more detail.
- The default use and style for creating bottom-up Web service had been changed from RPC encoded
to document literal wrapped.
Aside from the items listed above, the focus has been on stabilizing existing function since WTP 0.7 milestone.
Please be aware of the following known problems when using the Web Services
tools. See the associated Bugzilla defect for further details.
- Creating Web service or Web service client
When creating top-down Web service, if you selected Overwrite file without warning, any
existing skeleton implementation bean will be overwritten. Please back up the skeleton implementation bean
before creating top-down Web service if the skeleton implementation bean already exists.
When creating top-down Web service or Web service client, make sure that the WSDL file refered
by the URI to the WSDL or WSIL document in the Web service selection page is accessible. Otherwise,
the Web services wizard would be waiting indefinitely to try to access the WSDL file.
When using the Web Service wizard or Web Service Client wizard, do not use a
project that has a non-default project content, that is, one that exists
outside of the Eclipse workspace.
When creating a Web service, do not de-select the Intall Web Service checkbox
if there's no server in the workspace. Otherwise, the wizard would not advance
from the Web Service Configuration page.
When creating top-down Web service or Web service client, if you are entering an URI
to a WSDL or WSIL document not in the workspace, make sure that the document is loaded and the
table below the URI titled Select a WSDL is populated before proceeding with the wizard.
Otherwise, you may get an error message Selection must be WSDL and the fields
in the next page may be empty.
When creating Web service client, do not choose to generate Web service client proxy in the same
Web project as the one containing the Web service since if you selected Overwrite file without warning,
the generated Web service client proxy will overwrite the Web service implementation files contained in the Web
When creating Web service client, the server does not get started automatically if
Test the Web service is not also selected.
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.
- Web services Sample JSP
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.
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.
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.
- Supported servers
The Geronimo 1.0 Server is enabled for the Web service wizard but not yet fully
functional due to these significant defects.
- Web Services Explorer
The Web Services Explorer does not work with the Netscape browser. Change
the default Web Browser by using Window -> Preferences -> General ->
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.