marginal improvements - still no automated client constructor.

[jalview.git] / build.xml

diff --git a/build.xml b/build.xml
index fd4257c..303437d 100755 (executable)
--- a/build.xml
+++ b/build.xml
@@ -39,7 +39,9 @@
       <property name="wsdl.File" value="http://anaplog.compbio.dundee.ac.uk:8080/axis/services/jpred?wsdl" />
       <property name="wsdl.Files" value="http://anaplog.compbio.dundee.ac.uk:8080/axis/services/vamsas?wsdlFiles" />
       <property name="wsdl.MsaWS" value="http://anaplog.compbio.dundee.ac.uk:8080/axis/services/MuscleWS?wsdl" />
-
+      <property name="wsdl.MsaWS2" value="http://anaplog.compbio.dundee.ac.uk:8080/axis/services/ClustalWS?wsdl" />
+      <property name="wsdl.MsaWS2" value="http://anaplog.compbio.dundee.ac.uk:8080/axis/services/ClustalWS?wsdl" />
+        <property name="WSInterf" value="MsaWS" />
       <property name="WebStartLocation" value="http://www.compbio.dundee.ac.uk/~jimp/jalviewtest"/>
       <property name="wsdl.Namespace" value="vamsas" />
       <property name="wsdl.ClientNS" value="ext.vamsas" />
@@ -200,6 +202,16 @@
     </target>
 
     <target name="buildextclients" depends="init">
+<!-- Currently, we do not do this automatically.
+     1. Run WSDL2Java as below, which generates an ext.vamsas +
+     vamsas.<datapackages> fileset.
+     2. refactor ext.vamsas.SpecificserviceWS* to
+     ext.vamsas.ServiceclassWS* that implements the ServiceclassWSI interface.
+     3. Update the jalview.ws.*WServices classes to reflect the
+     interface type, and all locations of this wsdl type that Jalview
+     might be using.
+     
+-->
       <path id="axisbuild">
         <!--        <path refid="axis.classpath"/> -->
         <path refid="build.classpath"/>
@@ -214,7 +226,7 @@
       <axis-wsdl2java
       output="${sourceDir}"
       verbose="true"
-      url="${wsdl.MsaWS}"
+      url="${wsdl.MsaWS2}"
       serverside="false"
       deployscope="Request"
       debug="false"