© Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM® Corp.
If you are using a proxy server that requires basic authentication to access the Internet, then you will receive an error if you are using UDDI within the Web Services Explorer.
For example:
If the Web Services Explorer UDDI page is displayed and then you attempt to connect to a registry and to find a business, then following message is returned in the results pane:
IWAB0135E An unexpected error has occurred.
UDDIException
java.net.SocketException: Connection reset
If you import an existing Web service client project generated in an earlier version of the product into the workspace, and then regenerate the Web service client and sample JSPs into the same project, you might see validation errors on the generated Result.jsp page stating that org.eclipse.jst.ws.util.JspUtils cannot be resolved. This class is in webserviceutils.jar; the sample JSPs actually compile and run without problems even though the validation errors are listed.
The workaround for this problem is to close and re-open the project, and then perform a clean and build of the project.
You will not be prompted to check out a read-only/checked-in WSDL file that is under source control whenever an attempt is made to modify the WSDL file opened in the WSDL Editor. This initial change and any subsequent changes that follow will not be saved. The solution is to first check out the WSDL file prior to making any changes.
There is a similar problem with the XML Schema Editor. You will be prompted when checking out the file, however if changes are made in the graphical view then the changes will be lost after you save. If the changes are made in the source view then the changes are saved. The workaround is to first check out the XSD file prior to making any changes.
When launching the Web services sample JSP in a Web service scenario, occasionally, you might get "HTTP Error code 404" with the message "Failed to find resource /sampleProjProxy/TestClient.jsp". The workaround for the problem is to wait until the "Publishing to server" message disappears in the progress indicator on the lower right-hand corner of the workbench, then select the sample JSP in the browser, right-click and choose Refresh to refresh the JSP.
In the Web Service Server and Runtime preference page, the Web Service Runtime field might change when the Server field is changed. The server and runtime shown might not be a valid combination. Ensure that the server and runtime are the desired settings and are valid before applying the change.
When publishing a Web service to a Unit Test UDDI Registry, the Next button on the Web Service Publication page takes you to a page where you can choose a server to publish to. In some cases, the Next button is disabled and you can only click on Finish. Clicking Finish brings up the Web Service Explorer but the Web service is not actually published to the UDDI registry.
When generating a top-down Web service using the Web Service Wizard, you will encounter a NullPointerException if the following conditions are true:
1. The service definition field is initially blank.
2. You click Browse to open the Select Service Definition dialog box.
3. You close the Select Service Definition dialog box without selecting anything.
4. You enter a valid WSDL URL into the service definition field and click Next or Finish.You can recover from the NullPointerException by browsing to a valid WSDL URL through the Select Service Definition dialog box rather than entering the text directly into the service definition field.
If your workspace path has spaces in it the Java™ Editor is not launched automatically after a top-down Web service generation scenario. If this occurs, you should manually open the
generated service implementation file. The naming convention for the service implementation file is <WSDL portType name>Impl.java
When creating bottom-up Web service using the context menu from the JSR-109 Web Services branch of the J2EE Project Explorer, you might get an "Unexpected exception occurred - java.lang.ClassCastException" if you selected to Hide Create Web Service Dialog in the Web Services Popup Dialog Selection preference or select Do not show me this dialog box again in the Web services wizard.
The Web services wizards remembers userid and password information for servers that have basic authentication enabled. This can cause problems if the incorrect user id and password are entered.
To workaround this problem Eclipse needs to be restarted.
When running the Web Services Explorer against an HTTPS URL, the Web Services Explorer may generate the following error:
java.lang.ClassNotFoundException on com.ibm.websphere.ssl.protocol.SSLSocketFactory
The workaround for this problem is to restart the Eclipse workbench and to not to invoke any server related operations such as “Initial Server Status” or “Publishing” before running the Web Services Explorer.