Hi,
I was able to get all of this to work in CS 10.0, but I'm having issues with the ant build file from the 10.5 section. In both cases, I've reverted my environment to use Java JDK 1.7.0_80 rather than JDK 1.8. I also copied the tools.jar from JDK_Home\lib to my ${base.dir}\lib\java directory along with the other jars required by the build.xml file. Using the version of the build that only does the C# compile for IIS, I was able to get a clean build. However, when I try to get the java services built, that's where I run into problems.
THe message I get from ant is the following:
\development\projects\FileFacets-EVault-Provider\CS10.5\WSAPI>ant
Buildfile: \development\projects\FileFacets-EVault-Provider\CS10.5\WSAPI\build
.xml
BUILD FAILED
\development\projects\FileFacets-EVault-Provider\CS10.5\WSAPI\build.xml:28: ta
skdef A class needed by class com.sun.tools.ws.ant.WsGen cannot be found: com/su
n/istack/tools/ProtectedTask
using the classloader AntClassLoader[D:\development\projects\FFEV-
Pro\CS10.5\WSAPI\lib\java\jaxws-tools.jar;D:\development\projects\FFEV-Pro\CS10.5\WSAPI\lib\java\tools.jar
Here are the relevant sections from my build file
<path id="classpath">
<pathelement location="${basedir}/lib/java/commons-logging-1.1.jar" />
<pathelement location="${basedir}/lib/java/csapi.jar" />
<pathelement location="${basedir}/lib/java/service-api-10.5.0.jar" />
<pathelement location="${basedir}/lib/java/service-jaxws-10.5.0.jar" />
<pathelement location="${basedir}/lib/java/jaxws-tools.jar" />
<pathelement location="${basedir}/lib/java/tools.jar" />
</path>
<path id="jaxws.classpath">
<pathelement location="${basedir}/lib/java/jaxws-tools.jar" />
<pathelement location="${basedir}/lib/java/tools.jar" />
</path>
<taskdef name="wsgen" classname="com.sun.tools.ws.ant.WsGen">
<classpath refid="jaxws.classpath" />
</taskdef>
Note that I added the tools.jar explicitly to my path to wsgen, whereas the rest of this build file is exactly what is in the 10.5 Extending CWS on the knowledge centre.
Has anyone else encountered this, and if so, what was your workaround? Right now, my only work around is to tell clients that we can do custom web services only for IIS, and not for Tomcat.
-Hugh Ferguson
