I'm trying to create a Web Service in Eclipse Java EE IDE (Helios Service Release 2, Windows 7 32-bit) based on a WSDL file, but when I click "finish" in the creation wizard I always get:

IWAB0014E Unexpected exception occurred.

(details: java.lang.NullPointerException
at org.eclipse.jst.ws.internal.axis.creation.ui.widgets.skeleton.SkeletonConfigWidgetDefaultingCommand.getOutputJavaFolder(SkeletonConfigWidgetDefaultingCommand.java:86)
at org.eclipse.jst.ws.internal.axis.creation.ui.widgets.skeleton.SkeletonConfigWidgetDefaultingCommand.execute(SkeletonConfigWidgetDefaultingCommand.java:47)
at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:419)
at **...**)

I'm 100% sure that WSDL file is correct - the error happens no matter how trivial etc. the file is.

The way I'm doing it:

create a general project and add a new WSDL file to it;

File -> New -> Other -> Web Services -> Web Service

In the Web Service wizard, I choose "Top down Java Bean Service" and select the appropriate WSDL file.

When I click Next or Finish, the above exception occurs and no source files are generated.

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.

Hi, thanks for your response; however, no, it doesn't work, the same exception with this WSDL. I actually had some friends try different WSDLs on their machines (same Eclipse version, same everything) and it works just fine, but fails for me for some reason. I updated Java, Java EE, checked for Eclipse Updates and still nothing.
–
md2511Mar 25 '11 at 20:23

The reason for this seemed to be messed up workspaces. I removed workspaces first from Eclipse Project Explorer, then from the filesystem. I then recreated the workspace and got no exceptions thrown.
–
md2511Mar 27 '11 at 14:14

this ended up working for me. not the best "solution", since it doesn't really address whatever workspace issues exist that caused the need for this workaround in the first place, but still, this works. I ended up running the web service client generation tool with all options I needed, and didn't even have to create a project. I just created an empty workspace, went through the wizard, and then copied generated code to my actual workspace, where things worked perfectly. thanks for adding your perspective on this, basselkh!
–
liltitus27Dec 3 '13 at 20:44