hbjastad
Contributor
Joined 9 years ago
User Profile
User Widgets
Contributions
Re: WSDL not displaying when hitting WAR
Switching on the web UI helped debug the problem - the context path had been added in the Virt, so that it was needed twice: /abc/abc?WSDL The solution was to change the context path in the virt to just /9 years agoPlace ReadyAPI QuestionsReadyAPI Questions3.5KViews1like0CommentsRe: WSDL not displaying when hitting WAR
Digging for a solution in the documentation, I found this (https://www.soapui.org/soap-mocking/deploying-mock-services-as-war-files.html): If you plan to use the ?WSDL exposure functionality of the MockService you will need to set the MockService Endpoint to the external endpoint to be used in related port addresses. Could someone explain exactly what this means? I guess I should add that I have 3 other virts, which are created exactly the same way as this 4th one, yet the first 3 work well even with '?wsdl' and this 4th one doesn't. My suspicion now goes in the direction of actual endpoints availability: I am behind a firewall and the first 3 services are accessible from within the firewall. The 4th service is NOT available from within the firewall, but I have downloaded the WSDL+XSD files and placed them alongside the Ready!API project file. Since this setup works within Ready!API, could the problem be that Ready!API is smart enough to access the local files...while the war file is trying to access the remote endpoint? If my assumption above is correct, is there a way to package WSDL+XSD inside the war file and have the mock-as-war use those?9 years agoPlace ReadyAPI QuestionsReadyAPI Questions3.5KViews0likes1CommentWSDL not displaying when hitting WAR
I have created a Virt from WSDL, and it works well within Ready!API. I can access the SOAP interface, and I can add '?wsdl' to retrieve the WSDL. But when I package the Virt as war and try to hit it with the added '?wsdl' I only get "Log is disabled." and no WSDL. The server log shows the following, which leads me to believe that Ready!API tries to provide the WSDL: [WsdlMockDispatcher] Mounted WSDL for interface [ABCEndpoint] at [/abc?WSDL]Solved9 years agoPlace ReadyAPI QuestionsReadyAPI Questions3.5KViews0likes2CommentsRe: Turning off "Accept compressed responses from host" programmatically
nmrao, you keep pointing to the GUI. My question is about the API, not the GUI. I don't have any issues running accessing services from the GUI, but I struggle to decode the response from Java/Groovy code when using SoapUI as an API.9 years agoPlace ReadyAPI QuestionsReadyAPI Questions6KViews0likes3CommentsRe: Turning off "Accept compressed responses from host" programmatically
In case the content is base64 encoded, I even tried String zippedBase64Str = response.getContentAsString(); byte[] bytes = Base64.decodeBase64(zippedBase64Str); GZIPInputStream gis = new GZIPInputStream(new ByteArrayInputStream(bytes)); But the result is the same - "Not in GZIP format"9 years agoPlace ReadyAPI QuestionsReadyAPI Questions6KViews0likes0CommentsRe: Turning off "Accept compressed responses from host" programmatically
What do you mean by "one time configuration using preferences"? I need to get this working in code, not the GUI. The best solution would be to be able to decode the response, which is gzip. I have tried the following alternatives, but they all result in 'java.util.zip.ZipException: Not in GZIP format': GZIPInputStream gis = new GZIPInputStream(new ByteArrayInputStream(((WsdlSinglePartHttpResponse) response).getRawResponseBody())); GZIPInputStream gis = new GZIPInputStream(new ByteArrayInputStream(response.getRawResponseData())); GZIPInputStream gis = new GZIPInputStream(new ByteArrayInputStream(response.getContentAsString().getBytes())); Does anyone have code that either turns off the ability to accept compressed responses, or that can decompress a compressed response?9 years agoPlace ReadyAPI QuestionsReadyAPI Questions6KViews0likes6CommentsTurning off "Accept compressed responses from host" programmatically
Hi, I am trying to write an integration test in Java using SoapUI and the following code is able to do that: // create new project WsdlProject project = new WsdlProject(); // import WSDL WsdlInterface wsdl = WsdlInterfaceFactory.importWsdl(project, endpoint.getWsdlUrl(), true)[0]; // get desired operation WsdlOperation operation = wsdl.getOperationByName(operationName); // create a new empty request for that operation WsdlRequest request = operation.addNewRequest("My request"); //WsdlRequest request = operation.getRequestAt(0); request.setEndpoint(endpoint.getEndpoint()); // generate the request content from the schema request.setRequestContent(operation.createRequest(true)); // submit the request WsdlSubmitContext submitContext = new WsdlSubmitContext(request); WsdlSubmit submit = request.submit(submitContext, false); // wait for the response Response response = submit.getResponse(); // validate the response String content = response.getContentAsString(); System.out.println(content); But when I look at the content, it is scrambled. The following 2 posts suggests that the solution is to turn off "Accept compressed responses from host": https://community.smartbear.com/t5/SoapUI-NG/soapui-unable-to-parse-responses-with-XML-embedded-as-strings/td-p/11716 https://community.smartbear.com/t5/SoapUI-Open-Source/Getting-unrecognized-character-on-webservice-response/td-p/9706 But I need to do this programmatically, not from the UI. How can I achieve the same programmatically?Solved9 years agoPlace ReadyAPI QuestionsReadyAPI Questions6.1KViews0likes8CommentsRe: Will there be another release of SoapUI open source?
Hi Rao, there might not be any reason for doing it this way - it was just an observation. But the question about the future of the open source version of SoapUI is key: When deciding on a test strategy for a large number of users, it's imperative to know if the product has a future or if it's already a dead end. In other words - should SoapUI open source be evaluated as a solution alternative, or is Ready!API the only offering SmartBear will provide?1.9KViews1like1CommentWill there be another release of SoapUI open source?
I am trying to understand SmartBear's strategy with SoapUI (and the newReady!API platform)... Previously, it was quite simple - there was a free, open source version of SoapUI and then there was a paid version (SoapUI Pro) with some additional features. When I look at the landscape now, I see * The open source version of SoapUI has not been updated for almost a year -https://github.com/SmartBear/soapui - with the latest release version being 5.2.1. Are there any plans to maintain this? Will there be any new releases, particularly for the new 6.0.0 file format that is being used by Ready!API? * Ready!API/SoapUI NG Pro moves forward with frequent releases. Ready!API can not be started without a license, so I assume this is only intended to be a paid version. If I try to create a project using Ready!API and then run the tests using the open source version of SoapUI, there is a warning about the new file format 6.0.0 being newer than the SoapUI version WARN [WsdlProject] Project 'Simulator UDI' is from a newer version (6.0.0) of SoapUI than this (5.2.1) and parts of it may be incompatible or incorrect. Saving this project with this version of SoapUI may cause it to function differently. When choosing which product to use, it would be good to hear from SmartBear what the strategy is... Will there be updates to SoapUI open source? Or is Ready!API the only way forward?2KViews2likes3Comments