Found another thread that helped me get around this.
http://www.eviware.com/forum/viewtopic.php?t=13170Basically, the things I need to know are:
- Is SoapUI going to act like a browser and continue to send cached Cookies in every request or do I have more control over exactly which cookies get sent?
- Is that caching in the context of a single test case, a test suite, or the entire project?
- Can you fix the bug where the raw request does not show exactly what is getting sent across the wire?
- Will you provide a way to manage cookies in a UI?