This section describes how to migrate from the Web services technology preview to WebSphere Application Server - Express Version 5.0.2.
You can normally reuse the Web Services Description Language (WSDL) file. If you created the WSDL file using the Java2WSDL command in the Web services technology preview and you encounter problems, regenerate the file. You must regenerate all Java classes generated by the WSDL2Java command in the technology preview. These classes fall into two categories, the development classes and the deployment classes. The development classes include the enterprise beans and exception classes generated by the WSDL2Java command. These classes are regenerated by running the wsdl2java -role develop-client (or -role develop-server) command. The deployment classes include *Stub.java, *Locator.java, *_Ser.java, *_Deser.java, and *_Helper.java classes. After you verify that no deployment class source code is included in the application EAR file, you can regenerate the deployment classes either by using the wsdeploy command, or by selecting Deploy Web Services on the application installation panels of the administrative console. Classes generated by the WSDL2Java command are identified by a comment at the top of the source file. You can reuse the original Web service client code and server implementation code. If you have any JAX-RPC handlers, rewrite the code to conform with SAAJ 1.1. For more information, see http://java.sun.com/xml/saaj/ 
. You can reuse the original webservices.xml and webservicesclient.xml deployment descriptors. Any information added to the original ibm-webservices-bnd.xml and ibm-webservicesclient-bnd.xml files need to be migrated to the new ibm-webservices-bnd.xmi and ibm-webservicesclient-bnd.xmi files.
In the Web services technology preview, all application exceptions extended IBM WebServicesFault. Now all application exceptions extend java.lang.Exception to comply with the J2EE specification.