Forum Discussion
13 years ago
Thank you! I had this exact same problem, and yes this same bug still occurs for me in v4.5.1. I had renamed a response inside soapUI but the XML had not been updated, even after saving it, and restarting. I had to go into the XML and search for 'Response 1' and there it was, even though 'Response 1' had been renamed inside soapUI ages ago.
I'm running on mac if that makes any difference.
I'm running on mac if that makes any difference.