A lot of responseContent tags in project file
Hello! In the following screenshot you see the content of the xml file of one of our projects: 1. Why are so many of these created? 2. How can I prevent this from happening, since i...
Forum Discussion
Hey Raven25,
I had a look at a couple of my projects' xml and it appears that the con:responseContent is generated when you create a virt.
Did you perhaps create some virts and then remove them? If this is the case, then this might leave behind empty responseContent elements like in your screenshot.
You do have to be careful editing a project .xml (very easy to corrupt the file), so if i were you, i'd take a copy (just to be safe) and then remove the EMPTY elements with value of <namespace:responseContent />
Strictly speaking these are empty elements and so shouldn't have any impact on the wellformedness of your project .xml if you remove them.
Once deleted, open your edited project .xml in an app with an xmlparser (IE, Notepad++ (if xmlplugin installed), xmlspy, etc.) If the edited .xml file opens successfully in the app without any errors reported, you'll have maintained the wellformdness and so the file should then open in ReadyAPI but with a slightly smaller file size.
One thing: is this the only content you want to remove? How many empty element rows are there? Depending on the size of your project file compared with the relative total byte size of empty elements, the risk of editing the project .xml file might not be worth the risk/effort/hassle.
Ok, that's all i got!
Cheers,
Rich
I had a look at a couple of my projects' xml and it appears that the con:responseContent is generated when you create a virt.
Did you perhaps create some virts and then remove them? If this is the case, then this might leave behind empty responseContent elements like in your screenshot.
You do have to be careful editing a project .xml (very easy to corrupt the file), so if i were you, i'd take a copy (just to be safe) and then remove the EMPTY elements with value of <namespace:responseContent />
Strictly speaking these are empty elements and so shouldn't have any impact on the wellformedness of your project .xml if you remove them.
Once deleted, open your edited project .xml in an app with an xmlparser (IE, Notepad++ (if xmlplugin installed), xmlspy, etc.) If the edited .xml file opens successfully in the app without any errors reported, you'll have maintained the wellformdness and so the file should then open in ReadyAPI but with a slightly smaller file size.
One thing: is this the only content you want to remove? How many empty element rows are there? Depending on the size of your project file compared with the relative total byte size of empty elements, the risk of editing the project .xml file might not be worth the risk/effort/hassle.
Ok, that's all i got!
Cheers,
Rich
- Oh! One thing. If you still have virts, but without any responseContent defined, then deleting the empty elements is NOT advisable! 😉