Friday 2 December 05
Last night I eventually figured out the problem I was having with the no class definition found when calling the CCSI webservice. The build script had an ant xslt task to transform the deploy.wsdd from the original (with the incorrect class names, eg org.coppercore.ccsi.DispatcherSoapBindingImpl) to an updated version (with the correct class names eg org.coppercore.ccsi.Dispatcher). The original ant xslt task was as follows:
<xslt basedir="WebContent/WEB-INF/@{service}Service/@{package.path}" destdir="WebContent/WEB-INF/@{service}Service/@{package.path}" extension=".wsdd" style="deploy.xsl">
<param name="newClassName" expression="@{implclass}" />
<include name="deploy.bak" />
</xslt>
and I changed this to:
<xslt in="./WebContent/WEB-INF/@{service}Service/@{package.path}/deploy.bak" out="./WebContent/WEB-INF/@{service}Service/@{package.path}/deploy.wsdd" style="deploy.xsl">
<param name="newClassName" expression="@{implclass}" />
</xslt>
So I’ve got it running and generating the deploy.wsdd files with the correct implementation class names, but that still doesn’t explain why it just stopped working, as I had had it running fine before!
