Very large SOAP request
I'm testing out a service using a very large SOAP request.
I already have the XML of the SOAP request that I would like to use. The problem is that when I try to paste this XML into soapUI is that soapUI just stalls. It will eat all of one CPU core and never finish what it is doing.
I believe the problem is due to the size of the XML: soapUI will try to parse this large XML in order to pretty print it (or something) and this just doesn't work well. Nothing strange in that really. Many XML browsers are (for reasons unknown to me) unable to display XML large than a few hundred k's. The XML I'm using cannot be browsed by Firefox for example. (I've tried many XML browsers and you'll be surprised how many of them have problems with this: the one I've finally settled on is - surprisingly for me - Microsoft's XML Notepad).
The thing is : I do not need to look at the XML from within soapUI. I do not need soapUI to display to me the XML of the request.
I need a way to tell soapUI that for a particular named SOAP request it should load the XML to use for the request from a file and not try to interpret it nor parse it nor display it. Just fire it into the service when I ask it to.
And to make things worse: The XML that comes back (response) is also rather large, some 50 Mbytes of text. I would assume that if I solve the first problem (the request) then soapUI would probably stall on the reply as well. Again the same goes here: I do not need to physically inspect the returned XML. Anyway: let's tackle the large request problem first and then we can deal with the large reply problem later.
Can this be done? If not do you know of an alternative method of working with soapUI in the situation where the SOAP request is very large ?
Thx.
I already have the XML of the SOAP request that I would like to use. The problem is that when I try to paste this XML into soapUI is that soapUI just stalls. It will eat all of one CPU core and never finish what it is doing.
I believe the problem is due to the size of the XML: soapUI will try to parse this large XML in order to pretty print it (or something) and this just doesn't work well. Nothing strange in that really. Many XML browsers are (for reasons unknown to me) unable to display XML large than a few hundred k's. The XML I'm using cannot be browsed by Firefox for example. (I've tried many XML browsers and you'll be surprised how many of them have problems with this: the one I've finally settled on is - surprisingly for me - Microsoft's XML Notepad).
The thing is : I do not need to look at the XML from within soapUI. I do not need soapUI to display to me the XML of the request.
I need a way to tell soapUI that for a particular named SOAP request it should load the XML to use for the request from a file and not try to interpret it nor parse it nor display it. Just fire it into the service when I ask it to.
And to make things worse: The XML that comes back (response) is also rather large, some 50 Mbytes of text. I would assume that if I solve the first problem (the request) then soapUI would probably stall on the reply as well. Again the same goes here: I do not need to physically inspect the returned XML. Anyway: let's tackle the large request problem first and then we can deal with the large reply problem later.
Can this be done? If not do you know of an alternative method of working with soapUI in the situation where the SOAP request is very large ?
Thx.
