All articles represent ideas and point of view of the author. Please use your judgement before taking actions. Author is not responsible for any kind of loss or damage due to actions taken following this blog. You are allowed to copy content provided a visible clickable link or courtesy is expressed to the original article in this blog. If you have suggestions or ideas, please contact admin@thecoolblogs.com

Saturday, April 2, 2011

java.io.IOException: FATAL ERRORS encountered by WSDL2Java tool

We will discuss how to resolve the below error message in Rational Application Developer (RAD) when you start the WebSphere Application Server


Error messages were issued.
java.io.IOException: FATAL ERRORS encountered by WSDL2Java tool.
at com.ibm.ws.webservices.wsdl.Parser.generate(Unknown Source)
at com.ibm.ws.webservices.wsdl.Parser.generate(Unknown Source)
at com.ibm.ws.webservices.tools.wsad.WSDL2Java._execute(Unknown Source)
at com.ibm.ws.webservices.tools.wsad.WSDL2JavaBase.execute(Unknown Source)
at com.ibm.etools.webservice.command.adapter.CommandToCommand.execute(Unknown Source)
at com.ibm.ast.ws.v7.jaxrpc.jee5.stub.WSDeployStub.execute(Unknown Source)
at sun.reflect.GeneratedMethodAccessor96.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)


In WebSphere Application Server, when you deploy or publish an application, it uses the WSDL files and generates the serializer and deserializer, even if it was already generated as a part of the proxies. This error message indicates that the WSDL file was either corrupted or not contains XSDs that does not match up. 


If you have your WSDLs changed recently, there could be chances that the server cache still has old WSDLs. We will discuss how to get rid of this error. Please follow the below steps


1) If any of your WSDLs changed, you need to make sure that you have all the dependent XSDs available in the same structure. Some XSD files will have references to other XSD files. In that case, you need to make sure the referenced XSDs files are also available


2) Select the project and right click and select "Refresh" form the menu


3) Build the project and start the server


4) If you still see the error, Right click on your server in the RAD Server view and select "Add and Remove Projects" and remove your project from server

5) Go to the Administrative Console -> Applications -> Application Types -> Websphere Enterprise Applications and uninstall your application, if it is listed there


6) Stop the server


7) Using the file system explorer navigate to <Websphere installation directory>\profiles\<your profile>\temp\wscache and delete your project from there


8) Then navigate to <Websphere installation directory>\profiles\<your profile>\temp\<your node>\<your server> and delete your project from there


9) Select your project in RAD and from the top menu select Project -> Clean (Make sure start a build immediately is checked)


10) Once the build is complete, right click on your server in the RAD Server view and select "Add and Remove Projects" and add your project to the server


11) Start the server. The error should be gone now

No comments:

Post a Comment