XML Nanny App Reviews

Oxygen editor validates my document but XML Nanny detects errors (and obviously it is a valid document)! Error message is not meaningful.

XML Nanny isnt able so simple show XML files. Its not implemented.

The source XML file as well as all parts of the schema (including all xsd:include) have to be available as local files. Entering an URL will result in an I/O error. When entering an invalid local file (e.g. a directory) - but even when everything is setup correctly - parsing will take age without any CPU activity. I guess the program still tries to open a network connection and fails eventually. I do consider the possibility to check one URL with a XML document against another URL with a XSD as a rather important feature. The program will validate correctly, when all files are local. Id also like the option to validate a bunch of files per wildcard. All these seems like rather minor work compared to the available functionality but impede usability significantly. I will definitely improve my rating when / if these issues are resolved (especially the I/O errors with URLs).

The reason I bought this program was because I wanted to validate my XML documents against a Schematron file. Unfortunately the program crashes instantly as soon as you try to parse a Schematron file, at least on my machine (MacBook Pro early 11 10.8) Schema and DTD work as expected but Schematron doesnt work at all.

This is EXACTLY what I was looking for. Thanks!

I purchased this application in order to validate information returned from a remote procedure call. Unfortunatly it crashes a lot and did not provide me with the information I was trying to gain. to the developer: Use Case! Test, Test, TEST........then test more

Purchased the program to test XML agains XSD. The program just does not work - no messages are display. Tried valid XML, broken XML. My recommendation stay away.

This little tool helped me a lot with XML based API integration. Does exactly what it says it does.

This app makes it easier to validate local XML files. It works well for the task it was designed for. However, it is extremely slow for validating XHTML files. Part of this is because loading the XHTML DOCTYPE from the internet takes quite a long time, even if you try to go there yourself. Overall I am pleased with this app, especially if someone wants to validate XML files that are not XHTML. I might try downloading all the parts of the XHTML doctype to speed up the process - perhaps including the XHTML 1.0 DOCTYPE in the program would be a beneficial update?

I am an XML student and have to validate my homework. With little to no experience doing this, XML Nanny showed me my errors in a clear way, I fixed them, and my homework is done. Validation has been made easy with this app.

I had greater expectations for this app. I imagine I would be able to put the XML, the XSD, see where the validation didnt go well and be able to edit the file and fix it inside the software, but thats not possible. The software will only validate and show me line numbers and mistakes then I have to correct it in an external editor and reparse the file. If you already have some IDE youll probably have this functionality there (as I have in Visual Studio).

I was expecting to be able to collapse nodes of the XML in this tool. It does not do that. The screen shots made it appear like it would.

I was having some problems geting some xml going in php with explode. I set up tidy on the server to see if that would help but it only resulted in xml being formatted differently and php was still dying on explode. Enter Nanny. I found the offending xml and threw it at Nanny and it told me exactly what was wrong. Now I know what needs to be stripped and can do so before explode. My only request: Retina support.

Its a piece of junk. Doesnt seem to be well maintained. "Printing" does nothing. Dont waste your time.

If you need to validate xml files for integrity, or against a schema or DTD this tool is great. If your looking to do something else, then this isnt what you need.

This is usless if you need to find a section in a long XML, all it seems to do is validate the XML. The Text Edit app that comes with your Mac is a far better tool to review the XML and find specific elements and ennumerations.

I have a MAMP PHP server that is serving dynamic XSD docs. That means that they use PHP to supply stuff like the namespace (its a dynamic schema). That also means that I would like to be able to enter a URI in the schema field, like so: http://localhost/xsd/TestSchema.php Unfortunately, the app renders the URI like so: http:/localhost/xsd/TestSchema.php <- NOTE: Missing second forward-slash in "http://". That means that I cant do dynamic network schema validation, and have to save the rendered schema document, then validate against that. I guess that you get what you pay for...

All this does is validate. It’s not an editor. But that one thing it does, it does very well. If you have a definition document, it will validate against that; if you don’t it will simply check your XML for well-formedness. It handles all four main definition document types, (including two lesser known ones.) Just what I needed.