When the tag we are looking for contains the same tag inside it we spit out partial data.

Example input:

<article>
  <item>
    <article></article>
  </item>
</article>

Example output:

<article>
  <item>
    <article></article>

Hi, i was very happy to find this, and it all went pretty dandy until it didn't.

The source of the problem seems to be forward slashed in attribute values.

Quick example:

<ifapRohdaten>
    <Anbieter AnbieterID="8141" Firmenname="1 Alpha Pharma GmbH" Land="Deutschland" Ort="Kaiserslautern" PLZ="67663"
              Strasse="Kohlenhofstr. 10" Telefon="0631 3038893" Fax="0631 3039601" EMail="[email protected]"
              URL="www.1alphapharma.de"/>
    <Anbieter AnbieterID="11965" Firmenname="HEXAL AG" Land="Deutschland" Ort="Holzkirchen" PLZ="83607"
              Strasse="Industriestr. 25" Telefon="0800/4392527" Fax="0800/4392532" EMail="" URL=""/>
    <Anbieter AnbieterID="13590" Firmenname="Infectopharm Arzn.U.Consilium GmbH" Land="Deutschland" Ort="Heppenheim"
              PLZ="64646" Strasse="Von-Humboldt-Str. 1" Telefon="06252 957000" Fax="06252 958844"
              EMail="[email protected]" URL="www.infectopharm.com"/>
</ifapRohdaten>

I parse for "Anbieter" nodes. The library stops calling the data callbacks when arriving at the second node (in this example, I was working with more nodes in my program).

This seems to be due to the forward slash in the Telefon= and Fax= - fields, which unfortunately is pretty common in the german speaking parts of Europe.

Anyhow, I thought I'd let you know. Maybe it's the self closing tags parser? I am not sure, but I thought I'd give you a heads up.

Thanks and bye

Daniel

e.g. querying for vehicle doesn't match anything against http://webservices.nextbus.com/service/publicXMLFeed?command=vehicleLocations&a=actransit