JHunt
Community Hero
Joined 8 years ago
User Profile
User Widgets
Contributions
Re: REST request with parameters - how to avoid default Content-Transfert-Encoding:quoted-printable ?
You might have a misunderstanding in how your endpoint expects to receive its data - double check the spec. If you are to send a file as an attachment (multipart) as you are doing already, then your endpoint should be able to manage all of those Content-Transfer-Encodings, as these are well specified and I can't imagine endpoint developer is not using a standard library. Which is why I suspect they are expecting it in another way? Perhaps as a single request body, perhaps in a header, perhaps embedded into JSON? In these cases you would do the base64 encoding yourself (groovy-lang.org) and specify the data wherever it really belongs.556Views1like1CommentRe: Cannot retrieve some emoticons from database
The reply from the server is a SOAP envelope (i.e. XML), and it doesn't make sense to declare an Accept header on the request, or respond with Content-Type header with any other Content-Type besides "application/xml". It looks like your endpoint is correctly encoding the unicode characters (w3.org), which is what you see in the raw response view. SoapUI may not display those characters unescaped in the XML view, but your application (endpoint consumer) might still handle them correctly. You could try inserting your endpoint's response into the following javascript code, which you can run in your browser's web console to verify that the unicode characters display correctly: (function (){ const response = `<emojis>☺</emojis>`; return new DOMParser() .parseFromString(response, 'text/xml') .getElementsByTagName("emojis")[0] .firstChild .data; })();333Views0likes0CommentsRe: i want to add swagger for java web application,but i didt know the process can any one help me to
Your question is off topic as it's not about using SoapUI itself. It sounds like you might have already been reading some information about swagger-jaxrs, but it doesn't sound like you've completed all the steps, such as defining the servlets in web.xml (github.com). (I won't comment further on this)728Views0likes0CommentsRe: SOAP UI 5.7.0 : Java.net.socketexception : broken pipe
The problem could be on the client side (SoapUI) but is more likely to be on the server side (endpoint). In that case, the question becomes out of scope for this forum, but it sounds like one possibility to check is whether your server is running out of memory (from stackoverflow.com).530Views1like0CommentsRe: set soapUI 5.7.0 log files using maven
In SoapUI 5.5.0, logging was with log4j version 1. That release doesn't have a tag in the repository, but the log4j configuration didn't change for 5.6.0, so you can find that configuration here: (github) SoapUI 5.7.0 uses log4j2 (github), and while log4j2 has a different configuration file format, it should also support the log4j 1 configuration files (apache.org). Download the original configuration and either: replace the soapui-log4j.xml in your installation directory with it, or save it separately and set the SoapUI property: soapui.log4j.config="<path-to-file>"693Views1like1CommentRe: Trial application
Hi, You can create a MockService from your own WSDL to answer your requests. In the sample projects (normally installed into your Documents folder) are some sample projects, and these have MockServices set up too. Finally, making an API request over HTTP is the same thing as requesting a webpage. You can try requesting http://www.google.com:80/ for example.903Views1like1CommentRe: Mockservice concurrent requests failing
Hi, You shouldn't need to do any synchronization stuff. Is this a Dispatch script or an OnRequest script? In Dispatch script, I suggest you try putting the variable into requestContext instead of context. Otherwise, I'd need to know a bit more about what your scripts do and how.1.3KViews0likes0Comments