Hey Lightem
It took a bit of going through your message to work out the problem - for future reference if you try and lay out everything providing clear details - e.g. I am publishing a REST request (WHATEVER method - PUT, POST, GET) using this payload and this is the response etc.
Anyway - right - when you say 'incomplete response' you mean the message array in the response payload appears empty.
This is weird considering the response you get via your browser includes a populated message array in your .json response, but the response payload in ReadyAPI! is generated with an empty message array in the payload - so my first thought is you've got some eventhandler or something stripping the content in the response before it's presented - but you'd know about that if you'd gotten that setup - it's not like just hitting a checkbox by mistake!
Ok - we need a bit of help to assist diagnosing this. Have you used Telerik's Fiddler before?
You need to download that - its a packet/network sniffer like WireShark (except a lot easier to use).
Download that - what you need to do is monitor the request when you try the submission in SoapUI and then compare with when you submit the request via the browser/postman or whatever.
Essentially you are proxying the requests to Fiddler before they get to their specified endpoint - Fiddler will indicate whats going on.
So follow the instructions here to setup Fiddler as ReadyAPI!/SoapUI proxy
Once the Fiddler cert is setup and you're good to do - within Fiddler hit the 'Any Process' button to select the ReadyAPI! window as the target to proxy
Submit your request in ReadyAPI! and watch the magic happen in the traffic window
1. Within ReadyAPI!, disable the proxy (button on mainscreen below main toolbar)
2. De-select ReadyAPI! as the target process (via the Any Process button)
3. Have you browser ready and copy in the URI to be submitted.
4. <Alt>+<TAB> to Fiddler and click the 'Any Process' button and select the browser window
5. Within the browser - submit your request - traffic will be recorded
6. De-select browser as the target process (via the Any Process button)
Please post the results so we can review - RAW, HEADERS and JSON results for both the ReadyAPI and Browser requests please!
Cheers,
richie