Export of Mock Service as WAR File not compatible with latest Tomcat
When trying to run exported war on Tomcat 11, I'm getting: org.apache.catalina.core.StandardWrapperValve.invoke Allocate exception for servlet [SoapUIMockServlet] java.lang.ClassNotFoundException: javax.servlet.http.HttpServlet With Tomcat 9 everything runs fine. My suspicion that the problem related to jakarta switch in latest Tomcat. Does Soap UI support newer server versions and if yes what should be configured to have proper war created? Thanks
Shared workspace
Hi, I have a couple-three dozen Projects, stored on a Google Drive, that i want to share with a couple co-workers, such that we are all working off the same song sheet. I have shared the google drive folder where they all reside, with them, but is there a way to allow them to import all the Projects into their SoapUI in one swell foop? Has seen something about shared Workspace, but can't find anything about how to accomplish that. Can anyone suggest?
Project WSDL replaced from another project
I have SoapUI v5.8.0 and two projects loaded. I noticed that if I open the Interface Viewer for first project, then the WSDL for the second project gets overwritten by the WSDL of the first project. In steps: - close SoapUI - open SoapUI - in the project list on the left (the Navigator), expand the first project and double click the first (and only) interface (the icon with two green arrows, pointing left and right) - the Interface Viewer appears with correct data, including the third tab named "WSDL Content", which shows the correct WSDL - now expand the second project and double click the first (and only) interface there - the Interface Viewer appears with correct data in the first tab (named "Overview"), but the third tab named "WSDL Content", shows the WSDL from the first project! Most things work, but if a TestCase in second project has a "Schema Compliance" assertion, it will fail, as the schema in the wrong WSDL is used and it does not match the actual test case result for a web service response. It is similar, if I first open the Interface Viewer for the second project, ie: - close SoapUI - open SoapUI - expand the second project and double click the interface - the Interface Viewer appears with correct data, including the third tab named "WSDL Content", which shows the correct WSDL - now expand the first project and double click the interface there - the Interface Viewer appears with correct data in the first tab (named "Overview"), but the third tab named "WSDL Content", shows the WSDL from the second project! After exiting SoapUI, the wrong WSDL is not saved. Also, if I don't open the Interface Viewer after starting SoapUI but just run the test suites, a similar thing happens: if I first run the test suites from first project, and then the tests from second project, the second project tests will fail with "Schema Compliance" assertions, as again, the second WSDL is "overwritten" with the first. The problem appears also when running testcases from java (using class com.eviware.soapui.SoapUI from soapui.jar): if first project test suites are run and then second project test suites, the second project tests will have an assertion error as they will compare to the wrong WSDL schema (the one from the first project). Important detail: for both projects the WSDL URL (as shown in the first tab of Interface Viewer) is same. This is because both the projects (the servers, not the SoapUI projects) were developed, well on my PC and they were created at different times, when running in my IDE. So both URLs are like: https://localhost:8443/foo/bar?wsdl I guess this may be related to the problem and will try a workaround by editing the SoapUI project XML file to make the URLs different. Unless a better approach is suggested...Can SoapUI help me determine WSDL errors?
I have downloaded SoapUI and I'm not sure it has the function I need. My situation is: Oracle provides an endpoint with a SOAP XML. I try to take this XML and put it into Visual Studio as a "Connected Service" Visual Studio says "Number of Services Found: 0" Can SoapUI determine why this is not recognized as a valid WSDL? Is there some other tool to do this?
SoapUI 5.7.2 stuck on splash screen
Hello! I'm using the 5.7.2. SoapUI, but every time I start, it stuck on the splash screen. The only way to close the app is to kill it in task manager. I'm installing it with Company Portal, so can't change the version, folders etc. but any help appreciated (IT couldn't figure it out) (Win 11) Thank you!
