NSXMLparser: How to catch an end element tag (<foo/>) when there is no start element tag
I've set up a parser that is consuming an asmx web service, and .NET is creating a close element tag. Here's a clip from the log:

    <Name>This is the Name</Name>
    <EmptyString1 />
    <EmptyString2 />
    <Name2>This is Name2</Name2>

When I get to the foundCharacters method, there are no found characters, and the empty element is being populated by the most recent found characters.  

For instance, the string for <EmptyString1 /> and <EmptyString2 /> is "This is the Name" when I want it to be an empty string or return a string that says "N/A".

It seems like NSXMLparser doesn't support this type of end tag, as it is just skipping over it.  You would think it would be catchable in didEndElement method, but it never gets there because it doesn't see it when the slash is at then end instead of </EmptyString1>.

How can I tell the parser to return a string when it hits this form of end tag?
NSXMLparser: How to catch an end element tag (<foo/>) when there is no start element tag
===

I've set up a parser that is consuming an asmx web service, and .NET is creating a close element tag. Here's a clip from the log:

    <Name>This is the Name</Name>
    <EmptyString1 />
    <EmptyString2 />
    <Name2>This is Name2</Name2>

When I get to the foundCharacters method, there are no found characters, and the empty element is being populated by the most recent found characters.  

For instance, the string for <EmptyString1 /> and <EmptyString2 /> is "This is the Name" when I want it to be an empty string or return a string that says "N/A".

It seems like NSXMLparser doesn't support this type of end tag, as it is just skipping over it.  You would think it would be catchable in didEndElement method, but it never gets there because it doesn't see it when the slash is at then end instead of </EmptyString1>.

How can I tell the parser to return a string when it hits this form of end tag?