Differentiate <error> and element <error> not found about aexml HOT 5 CLOSED

I think that the best solution is just to 'namespace' internal error element in AEXML, so it's called 'AEXMLError' instead of 'error', and this could not happen in that case, do you agree?

from aexml.

AEXMLError sounds better alternative for errors pertaining to parsing or writing XML. But that's a different issue.

I think AEXML should not be bothered to check for <error> in the XML. Let the end-developer think about what goes in the XML content.

from aexml.

I now see how AEXMLError is related to this issue and hard to separate since at the moment AEXML returns any error in the form of AEXMLElement("error", ..).

from aexml.

For the time being, I'm using:

if xmlDoc.root["error"].name == "error" && xmlDoc.root["error"].stringValue != "element <error> not found" {
    ...
}

from aexml.

Hi, this is fixed.

Now you have errorElementName class property on AEXMLElement,
so you can check against it if some element doesn't exist, and parse element like any other.

Thanks for the feedback,
// T

from aexml.