I ran into the same error situation last week, and tracked it down to a problem related to client/jbossws14-client.jar. This file is installed with JBoss 4.0.4 CR2 ejb3 profile (my choice of profile), and includes an out dated version of the schema/jbossws-tool_1_0.xsd that mandates element names like javaToWsdl instead of java-wsdl.
My solution is to remove the jbossws14-client.jar file from the client directory, and all the sample Web Services compiled without further problems.
You can also modify the imported-build.xml file to take jbossws14-client.jar out of the compile classpath if you want to.
awesome, that worked. thanks much!!
How were you able to do that?
Unfortnately the wstool is as well part of the client jar. But if you only delete the xsd from within the jar it works.
i simply removed jbossws14-client.jar from the $JBOSS_HOME/client directory. i didn't need the java 1.4 version anyway, i'm using 1.5. my common/import-build.xml file still references jbossws-client.jar, just not jbossws14-client.jar. that's all it took.
how on earth does everything build properly without the xsd? did you attempt to deploy anything with the xsd missing from the client jar? just curious... oh i removed line 58 of imported-build.xml by the way.