Contributions
Zip file vs. REST Service
Hi everybody, I'm struggling with SoapUI to successfully process a zip request and response of a REST service I have (as part of a bigger infrastructure). The REST service exposes two functions. - One takes a zip file as input as content of the REST call - One returns a zip file as response of the REST call With the first one I have been unable to successfully send a zip file to the service with multiple zip related error messages from the server (depending on the selected encoding of the request). The mime type of the request is set to "application/octet-stream", because that is what the REST Service expects. I have loaded the Zip file through the "LoadFrom..." entry in the context menu and also tried to load it by hand and assign it to the request property, but to no avail. With the second one I am unable to write the response Zip file correctly to a File. The closest I get to sucessfully dumping the response to a file, is that I can successfully obtain the Names of the files included in the dumped zip file, but unzipping fails with checksum errors (which lead me to believe there might be encoding issues involved, but I'm not sure). Both of the above work successfully in the bigger context of the complete application this service is part of, so I'm rather sure this is some issue between me and SoapUI Is there any obvious support for sending/receiving zipped data in SoapUI I'm missing ? Or if not, does anybody have experiences concerning these issues he/she could share ? kind regards René2.4KViews0likes2CommentsModifying Request Attachment through Groovy
Hi everybody, I'm looking for a way to modify an attachment of a request through a groovy script. I need to add some data to the attachment obtained from a prior test Step. I could probably modify the file representing the attachment in the filesystem and not cache it in the request, but I'm having a hard time figuring out how to do that. Has anybody already done something like this and can shed some light (share some code ) on this ? René2.6KViews0likes2CommentsProperty Transfer reset on Query Prameter named username
Hi, I have an issue when using a Property Transfer to a query Parameter named "username" (all lowercase). This seems to interfere with the "Username" property of the authentification. When I (re)create the username query param I get it in the Property dropdown, can select it and it works. But when saving and restarting SoapUI, it is gone. Is the code behind this maybe case-insensitive ? kind regards René16 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.9KViews0likes1CommentNo Response received when sending Large Attachments
Hi, I need to verify my service can cope with large (100MB) attachments being sent to it. So I created a TestStep that sends it an attachment with that size. Now verifying on the server side shows everything went fine, i.e. the huge attachment got sent fine. The response from the server if everything went fine is an empty response document with HTTP Status OK. In case of an error I'm sending a rather small XML error document with HTTP Status 404. So IMHO the size of the response should not be the culprit. The Problem I'm faced with is the TestStep within SoapUI never returns with a valid response (eventually it times out). If I reduce the size of the attachment to 30MB, then everything works as expected again. The funny thing is, when I take a look at the RAW response, in case I had an error on the server side, the RAW response is shown, but the Test Step is still shown as executing (and no Test assertions are executed). I'm currently using Build soapui-core-daily-2009-04-17-[1], Build Date 2009/04/17 02:05 Any Ideas what could cause this? kind regards René16 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.7KViews0likes0CommentsRe: -> Invalid xsi:type qname: 'n2:articlelistResponse'
I'm having the same issue, although with a different xsi:type obviously What is rather strange in my case though is the following. The ServiceResponse contains multiple Response Elements of xsi:type="NormalResponse", the first Response element gives me no error in the schema compliance test. Only starting from the second element I get "Invalid xsi:type qname: 'NormalResponse' ..." errors for all following Reponse elements. I'm using SoapUI 2.5.1 Build dist-104-2009-02-01, Build Date 2009/02/01 21:22 I've attached wsdl, schemas and the response.xml if that may help. kind regards René3.2KViews0likes0CommentsRe: Re: relative reference to a project in the workspace xml
I have this actually set to $(projectDir), but still have some absolute references in the project file. ABSOLUTEPATH TO OLD LOCATION HERE file:/ABSOLUETPATHTOWSDLHERE That threw my off, but it seems it is working anyway.5KViews0likes0CommentsRe: Re: relative reference to a project in the workspace xml
My Problem is a bit beyond the one of the OP (as I did discover that setting on my own ) But what I need is relative paths in the project files themselves. When I manually change the following settings to relative paths . file:/../../PATHTOWADL and all other references to the WADL (although I'm not sure this is required) everything still works fine. On shutdown of SoapUI it then overwrites at least the . with an absolute path again, which is a bit of a nuisance. Is there an option that enforces relative paths within the project files for the above mentioned paths ? Background: Project files are required to work on different machines where the structure is identical but just the location is different. kind regards René5KViews0likes0Comments