JAL-3070 pushed down JABAWS specific args for WsJobParameters to Jws2Client

[jalview.git] / src / jalview / ws / jws2 / Jws2Client.java

diff --git a/src/jalview/ws/jws2/Jws2Client.java b/src/jalview/ws/jws2/Jws2Client.java
index 3e4cc97..dfa7598 100644 (file)
--- a/src/jalview/ws/jws2/Jws2Client.java
+++ b/src/jalview/ws/jws2/Jws2Client.java
@@ -32,6 +32,7 @@ import jalview.ws.api.UIinfo;
 import jalview.ws.jws2.dm.AAConSettings;
 import jalview.ws.jws2.dm.JabaWsParamSet;
 import jalview.ws.jws2.jabaws2.Jws2Instance;
+import jalview.ws.params.ArgumentI;
 import jalview.ws.params.ParamDatastoreI;
 import jalview.ws.params.WsParamSetI;
 import jalview.ws.uimodel.AlignAnalysisUIText;
@@ -112,10 +113,10 @@ public abstract class Jws2Client extends jalview.ws.WSClient
               && paramset.size() > 0)
                       ? new WsJobParameters((ParamDatastoreI) null, sh,
                               (WsParamSetI) null,
-                              paramset)
+                              JabaParamStore.getJwsArgsfromJaba(paramset))
                       : new WsJobParameters((ParamDatastoreI) null, sh,
                               preset,
-                              (List<Argument>) null);
+                              (List<ArgumentI>) null);
       if (adjustingExisting)
       {
         jobParams.setName(MessageManager