This content has been marked as final. 
    
Show                 2 replies
    
- 
        1. Re: JAXWSJBosssalex Dec 20, 2006 6:55 AM (in response to brunomatos)Yes, i've got the very same problem. 
 In build-impl.xml the ant task is defined as this:<taskdef name="wsimport" classname="com.sun.tools.ws.ant.WsImport"> <classpath path="${j2ee.platform.wsimport.classpath}"/> </taskdef>
 Changing the classpath to be:<classpath path="${libs.jaxws20.classpath}"/>
 fixes the build.
 I defined a library (JAX-WS) to point to the jwsdp-2.0 jars.
 But this fix breaks if build-impl.xml is regenerated next time by netbeans :-).
 I'm using netbeans 5.5.
- 
        2. Re: JAXWSJBosssalex Dec 20, 2006 7:08 AM (in response to brunomatos)In your build.xml you can overwrite auto-generated targets from your build-impl.xml. 
 Just copy the wsimport-init target to the build.xml file and change it to have the classpath ${javac.classpath}:<target name="wsimport-init" depends="init"> <mkdir dir="${build.generated.dir}/wsimport/client"/> <mkdir dir="${build.generated.dir}/wsimport/binaries"/> <mkdir dir="${classes.dir}"/> <taskdef name="wsimport" classname="com.sun.tools.ws.ant.WsImport"> <classpath path="${javac.classpath}"/> </taskdef> </target>
 You probably have to add the JAX-WS libraries to the project Libs.
 
    