psy
Occasional Contributor
Joined 10 years ago
User Profile
User Widgets
Contributions
Re: service responses binary data
Your example from post 5 helped me to sent back a non plain text file like PDF / ZIP / JPEG or whatever, Tools.readAndWrite was the key. But due to my project usage after successfully sent back the response with "return new com.eviware.soapui.impl.rest.mock.RestMockResult(mockRequest);" my SoapUI has thrown the Exception "Failed to find MockResonse" I had to change the call of Response. Instead of return directly the content, I put the output stream response.getOutputStream()) into a requestContext variable: Tools.readAndWrite(inputS, length, response.getOutputStream()); inputS.close(); requestContext.myResponse = response.getOutputStream(); return "MockResponse"; The "MockResponse" below the MockAction contains as Body only ${myResponse} No error log entry anymore and everything works as expected. :smileyhappy:4.8KViews1like0CommentsRe: SSL Support for REST MockServices in 5.0.0
Hello Rao, same problem for me, too. The Problem exists now since years and current SoapUI 5.2.1 is still having this issue. As a counter test the Ready! API 1.7.0 is working fine with exactly same SoapUI Project. My REST MockUp is reached over SSL Connection. But I don't want to buy another heavy expensive licence just to be able to Mockup a server. Most of the time I wish there would be an alternative to that product! :-( ---- Edit: It would be great if support would mention in such requests, that there is a Feature request open for that Found here: https://community.smartbear.com/t5/SoapUI-NG/SoapUI-REST-Mock-Service-with-SSL/td-p/43051 " ......SSL is not currently supported for REST Mock Services. We have a feature request for that to be implemented in a future release (SOAP-2065). "3.5KViews0likes0CommentsRe: very large HTTP GET Requests are getting ArrayOutOfBoundException: 4096 (HTTP/1.1 413 FULL head)
Version 1.6 is out, but the fix is never mentioned up to now in any change log. But the page for "Java Virtual Machine Parameters" contains the property. Issue is solved at all :-) http://readyapi.smartbear.com/soapui/working/environment_settings/jvm_options4.4KViews0likes0CommentsRe: very large HTTP GET Requests are getting ArrayOutOfBoundException: 4096 (HTTP/1.1 413 FULL head)
Ready! API nightly build 1.4.1 contained the fix and now the version 1.5.0 is released, but no (sub) release note is mentioning this fix. http://readyapi.smartbear.com/about/release_notes/start As an improvement, it would be helpful to see all changes in release note. We have already enough fixes and features as submarine in our business applications. A tool for testing should be better. ;-)4.8KViews0likes1CommentRe: very large HTTP GET Requests are getting ArrayOutOfBoundException: 4096 (HTTP/1.1 413 FULL head)
Hello, thank you for the fix. I have downloaded the 1.4.1 Snapshot from 25.09. and the property is working again -Dsoapui.mock.connector.headerBufferSize=<my new value> I will see when it becomes public in next 1.4.2 or 1.5 release and with an entry in release note.4.9KViews0likes0CommentsRe: Any short term plan for soapui.org homepage update to offer ReadyAPI documentation?
Hello, thank you for the link to that new online help. Yes, this is was I have searched for as an entry point. As short term I would propose to place such info on www.soapui.org somewhere at the top as sticky note like "For easy changeover from SoapUI to ReadyAPI usage and Ready! API online help, please click here"3.1KViews0likes2CommentsRe: Any short term plan for soapui.org homepage update to offer ReadyAPI documentation?
It is a general issue. After working with old SoapUI GUI, it is a big change and thus not easy to find the stuff on its known places. For the location of my Mock service I took 45 minutes to recognize the new place, another 10 minutes to "see" the big "Script" button in the middle for my groovy script. Comming from SoapUI as our tool, we waste our time to realize the new locations, places of configuration, etc... A general GUI point of view with comparison of SoapUI and ReadyAPI is highly advisable. At least as short term, the getting started chapters should point to ReadyAPI.3.2KViews0likes5Commentsvery large HTTP GET Requests are getting ArrayOutOfBoundException: 4096 (HTTP/1.1 413 FULL head)
With ReadyAPI 1.3.1 I get for my very large HTTP GET request an ArrayOutOfBoundException: 4096 -- formerly known in "old" SoapUI as "HTTP/1.1 413 FULL head" Response. This is an old topic over years and was possible to bypass with a special property in .vmoptions but later-on it was not working and never fixed again. According of change log, the overwrite of Jetty connector properties was introduced with SoapUI 3.5 Beta2 fixes: 2010-03-01 : 3.5 - the Protocol Release SoapUI 3.5 adds support for JMS, JDBC and AMF for both functional and load-testing [.....] Library Updates •Jetty 6.1.22 [.....] Beta2 fixes: [.....] - Added possibility to override Jetty Connector properties via soapui.mock.connector.XX system properties But e.g. in SoapUI 4.6.2 is was not longer working, maybe it was due to update to Jetty 6.1.26? BTW: Why is SoapUI using such old and unsupported Jetty Version, while the newest and stable is 9.x ? My local hard coded fix was to get the Jetty 6.1.26 source code and to patch for my own the jetty-6.1.26.jar package to get a larger buffer. AbstractBuffers.java private int _headerBufferSize = <my new value>; Please provide a fix based on some .vmoptions Java properties -Dsoapui.mock.connector.headerBufferSize=<my new value> And almost fundamental please provide a knowledge data base, where such atypical settings are described.Solved5.1KViews0likes4CommentsAny short term plan for soapui.org homepage update to offer ReadyAPI documentation?
In past the SoapUI home page was more or less usable to get started. But now with ReadyAPI tool box it is not possible anymore with given examples. As a paid user of SoapUI pro, now called SoapUI NG pro, I not only expect to get a working tool box, but a reasonable documentation, too. Is there any plan to offer an updated home page documentation?Solved3.2KViews0likes7Comments