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. HTH, -- Weiqi Gao [EMAIL PROTECTED] View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3941977#3941977 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3941977 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
