Well, that could be caused by any number of problems. For example:
The IDE configuration is corrupted The file may have a wsdl extension but actually contains the Data Access Definition eXtended (DADX) file that is used to generate a DB2 DADX Web Service from a stored procedure from SQL statements (how terribly un-SOA of WebSphere) which is useless to you as a client. Check the contents of the file. Does it look anything like the
WSDL Document example?
If it doesn't go back and get the WSDL that should be published/generated by the the DADX web service.
Otherwise use the WSDL2Client command line tool in
<RAD60_HOME>/bin
as described on page 408 of "Using commandline tools: WSDL2client" in
WebSphere Version 6 Web Services Handbook Development and Deployment WSDL2Client Manual Page It will take a URI that is remote or on the file system.
See also
Importing the WSDL2Client generated client into a Java project