If you want to deploy your Web services to a WebSphere v5.0 server using the WebSphere v5 runtime and server targetting preference is enabled but your service Web or EJB project is set to No server target specified in a bottom-up Java bean or EJB Web service scenario, then you might get this error from the Web service wizard:
Error in generating WSDL file from Java.
Details: java.lang.ClassNotFoundException: com.ibm.ws.webservices.engine.encoding.SimpleType
When that happens, you will notice that the Web or EJB project has empty Java build path and the Task view shows the errors:
This compilation unit indirectly references the missing type java.lang.Object.
The project was not built since its classpath is incomplete. Cannot find the class file for java.lang.Object
To workaround this problem, first:
- disable the J2EE server targetting preference (this preference is already disabled by default), or
- if you have to enable the J2EEserver targetting preference, you need to create your service Web or EJB project and client Web project and target them to WebSphere Application Server v5.0
then, re-run the Web service wizard.
You might get a similar empty Java build path problem in other Web service scenarios if the server targetting preference is enabled and your client Web project is set to No server target specified or if the service Web or EJB project has server targetting set to WebSphere Application Server v5.0 and you let the Web services wizard create a client Web project for you automatically.
You can avoid this problem by following the workaround mentioned above or if you are already in this situation where the Java build path is empty on a Web or EJB project, you could right-click on the project, select Target Server, then select Modify and select a different server target than the current one. After that, you could go back and modify the server target back to WebSphere Application Server v5.0. With this workaround, the Java build path of the Web project would be set up properly again.
If you right click on a proxy generated by the Web services wizard, select Web Services-> Generate Sample Application, then choose the Web Tool Java bean JSP as the test facility and hit finish, you might get an exception when you try to run the methods in the generated sample. This occurs because the getEndPoint and setEndPoint methods have not been excluded. You could workaround the problem by deselecting these two methods when invoking the Web Tool Java bean JSP from the pop-up, or choose the Web services sample JSP or the Universal Test Client as the test facility. Alternatively if you are using the SOAP runtime, you could invoke the Web tool Java bean JSP from the Web services wizard.
Return to the main readme file
(C) Copyright IBM Corporation 2000, 2003. All Rights Reserved.