Skip Menu |

This queue is for tickets about the XML-Compile CPAN distribution.

Report information
The Basics
Id: 74048
Status: resolved
Priority: 0/
Queue: XML-Compile

People
Owner: Nobody in particular
Requestors: BBYRD [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 1.24
Fixed in: (no value)



Subject: Error not helpful: element `{http://www.opengis.net/kml/2.2}Document' not processed
element `{http://www.opengis.net/kml/2.2}Document' not processed trace: using preparsed XML node <{http://www.opengis.net/kml/2.2}kml> error: element `{http://www.opengis.net/kml/2.2}Document' not processed at {http://www.opengis.net/kml/2.2}kml at /opt/local/lib/perl5/XML/Compile/Translate/Reader.pm line 608 XML::Compile::Translate::Reader::__ANON__(XML::Compile::Iterator=HASH(0x256eb48)) at /opt/local/lib/perl5/XML/Compile/Translate/Reader.pm line 497 XML::Compile::Translate::Reader::__ANON__(XML::Compile::Iterator=HASH(0x256eb48)) at /opt/local/lib/perl5/XML/Compile/Translate/Reader.pm line 92 XML::Compile::Translate::Reader::__ANON__(XML::LibXML::Element=SCALAR(0x1705378)) at /opt/local/lib/perl5/Geo/KML.pm line 187 Geo::KML::from("Geo::KML", "CustData.kml") at ./kml-decode.pl line 30 Even with debugs turned on, this error message appears to be fairly unhelpful in debugging problems with the XML. The issue has nothing to do with Document, but with something within the xAL XML in Document->Placemark->xal:AddressDetails. The lack of detail in the error message has forced me to resort to trial and error (removing code piece by piece). I would patch it myself, but I'm not sure exactly where the problem lies with the reporting routines. It seems like Reader should error sooner, when it encounters the problem tag.
On Mon Jan 16 16:00:08 2012, BBYRD wrote: Show quoted text
> Even with debugs turned on, this error message appears to be fairly > unhelpful in debugging problems with the XML. The issue has nothing > to do with Document, but with something within the xAL XML in > Document->Placemark->xal:AddressDetails. The lack of detail in the > error message has forced me to resort to trial and error (removing > code piece by piece).
Some features of schema's make it impossible to produce understandable error messages when the messages do not validate... whether the failure of validation is cause by the message itself or the code interpreting the error. In this case, it is a problem with interpreting the AddressDetails being a mixed element. I have investigated this before: there is no generic way to improve error messages when the schema is this vague on what it expects in the message. The bug-report is for Geo::KML