XML files got corrupted
SoapUI got closed abruptly and corrupted all important xml files? What should I do now?
Forum Discussion
I've had some luck with loading the XML file into notepad++. Notepad++ has an XML plugin that can check syntax and whatnot for you. You might be able to find and fix the corrupted parts. Definitely make a copy and work off of that, though, just in case.
Hi, another cause of the file being corrupted that I encountered was when we were merging the project file at Git. Some tags were not closed properly after another person did a merge. Anyway, I agree with msiadak, sometimes you have to load it in Notepad++. It would also help if you have the following:
- Pretty Print option enabled - so that it's easy to compare since this will display the codes line by line, making it more organized. In case another person changed it, you can easily compare based on the lines and tags modified.
- The codes stored in a repository (Git or CVS), this way, when the project file gets corrupted, you can get back to the latest (or even previous ones) version of the code that was saved before it got corrupted. When you check the change log, there are also tools to compare the changes made to the previous version per line.
Another feature I've made use of is that ReadyAPI can make backups of the projects before saving them. Sometimes this will give you an extra copy to play with. It should be an option in the Preferences menu.
When I open from Notepad++ it says NULL all around the script
Unfortunately, unless you are comfortable and/or familiar enough with XML to try to rebuild the corrupted part of the XML project file, there may not be much you can do. Do you have a backup and/or repository you push to?
I've gotten into the habit of committing at least once an hour and pushing at least the end of every day.
Hi, I supposed you are using Ready!API with SoapUI NG Pro tab because you posted here instead of the Open Source Forum page. Our client using Ready!API told me that support comes with the application/tool subscription. If it got corrupted so much that you can't fix it on your own, maybe you could send it over to them or show them selected part of what you are seeing in the file (if you are working in a company that wants confidentiality for codes) so that they can help you fix it. Here's the link: Customer Support If I were a SoapUI dev, I would also be interested to know what happened before the file got corrupted so that I can patch the app for a fix and come up with solution for users like you who encountered the same issue. In SoapUI Open Source, there is an option there to send statistics or usage details. Maybe they also have a way to track it on your application?
