Details

    • Type: Task Task
    • Status: Open Open (View Workflow)
    • Priority: Optional Optional
    • Resolution: Unresolved
    • Affects Version/s: 4.8
    • Fix Version/s: 4.x
    • Component/s: Web Services
    • Security Level: Public (Everyone can see)
    • Labels:
      None
    • Similar Issues:
      Show 10 results 

      Description

      The version we use is 1.7.1 and the current version is 3.5.

      We need to look at updating.

        Activity

        Hide
        Tom Cunningham
        added a comment -

        I started taking a look at this - it looks like switching the versions (I went soapui-1.7.1 -> soapui-3.5.1, looks-2.1.2 -> looks-2.2.0, and soapui-xmlbeans-1.7 -> soapui-xmlbeans-3.5.1) creates a couple of compilation errors. I fixed these with this patch :

        [tcunning@localhost services]$ svn diff
        Index: soapui-client/src/main/java/org/jboss/soa/esb/services/soapui/SoapUIClientService.java
        ===================================================================
        — soapui-client/src/main/java/org/jboss/soa/esb/services/soapui/SoapUIClientService.java (revision 33536)
        +++ soapui-client/src/main/java/org/jboss/soa/esb/services/soapui/SoapUIClientService.java (working copy)
        @@ -80,6 +80,7 @@
        import org.w3c.dom.NodeList;
        import org.xml.sax.SAXException;

        +import com.eviware.soapui.DefaultSoapUICore;
        import com.eviware.soapui.SoapUI;
        import com.eviware.soapui.impl.wsdl.WsdlInterface;
        import com.eviware.soapui.impl.wsdl.WsdlOperation;
        @@ -181,7 +182,7 @@
        xmlPropertyIS.close() ;
        }

        • SoapUI.initSettings(soapUIPropertyFile.getAbsolutePath()) ;
          + ((DefaultSoapUICore)SoapUI.getSoapUICore()).init(soapUIPropertyFile.getAbsolutePath()) ;
          }
          }

        @@ -527,7 +528,8 @@
        WsdlInterface[] wsdlInterfaces = getWsdlInterfaces(wsdl, httpClientProps);

        for (WsdlInterface wsdlInterface : wsdlInterfaces) {

        • List<Operation> operations = wsdlInterface.getOperations();
          + Map<String, Operation> mapOperations = wsdlInterface.getOperations();
          + Collection<Operation> operations = mapOperations.values();

        for(Operation operation: operations) {
        if(operation.getName().equals(operationName)) {

        I think these changes need to be coalesced with the AOP fix that dward added and one of the tests looks like it is failing with this change so that should be looked at as well.

        Show
        Tom Cunningham
        added a comment - I started taking a look at this - it looks like switching the versions (I went soapui-1.7.1 -> soapui-3.5.1, looks-2.1.2 -> looks-2.2.0, and soapui-xmlbeans-1.7 -> soapui-xmlbeans-3.5.1) creates a couple of compilation errors. I fixed these with this patch : [tcunning@localhost services] $ svn diff Index: soapui-client/src/main/java/org/jboss/soa/esb/services/soapui/SoapUIClientService.java =================================================================== — soapui-client/src/main/java/org/jboss/soa/esb/services/soapui/SoapUIClientService.java (revision 33536) +++ soapui-client/src/main/java/org/jboss/soa/esb/services/soapui/SoapUIClientService.java (working copy) @@ -80,6 +80,7 @@ import org.w3c.dom.NodeList; import org.xml.sax.SAXException; +import com.eviware.soapui.DefaultSoapUICore; import com.eviware.soapui.SoapUI; import com.eviware.soapui.impl.wsdl.WsdlInterface; import com.eviware.soapui.impl.wsdl.WsdlOperation; @@ -181,7 +182,7 @@ xmlPropertyIS.close() ; } SoapUI.initSettings(soapUIPropertyFile.getAbsolutePath()) ; + ((DefaultSoapUICore)SoapUI.getSoapUICore()).init(soapUIPropertyFile.getAbsolutePath()) ; } } @@ -527,7 +528,8 @@ WsdlInterface[] wsdlInterfaces = getWsdlInterfaces(wsdl, httpClientProps); for (WsdlInterface wsdlInterface : wsdlInterfaces) { List<Operation> operations = wsdlInterface.getOperations(); + Map<String, Operation> mapOperations = wsdlInterface.getOperations(); + Collection<Operation> operations = mapOperations.values(); for(Operation operation: operations) { if(operation.getName().equals(operationName)) { I think these changes need to be coalesced with the AOP fix that dward added and one of the tests looks like it is failing with this change so that should be looked at as well.
        Hide
        David Ward
        added a comment -

        JBESB-3276 is the "AOP fix" that Tom mentioned.

        Show
        David Ward
        added a comment - JBESB-3276 is the "AOP fix" that Tom mentioned.

          People

          • Assignee:
            Tom Cunningham
            Reporter:
            Kevin Conner
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: