Lists Home |
Date Index |
Elliotte Rusty Harold wrote:
> At 10:27 AM -0800 2/22/04, Dennis Sosnoski wrote:
>> Can you mention what the main flaws are for Piccolo? I've seen a
>> number of companies using it, and from what I remember it's also the
>> basis of the parser used by BEA's NetBeans (now part of Apache, so
>> that may be changing). Many people would consider BEA's main XML
>> infrastructure project to be serious work. :-)
i think Apache XmlBeans no longer use Piccolo because of concerns over
its LGPL license.
> Come here me talk at XML Europe in a couple of months and I'll give
> you the complete rundown on a whole bunch of SAX parsers and exactly
> where each one screws up.
i hope you publish your presentation as not everybody can make to XML
> But several problems with Piccolo include:
> 1. Inability to recognize ignorable white space.
> 2. Use of non-standard ENUMERATION attribute type instead of NMTOKEN
> 3. Failure to handle document type declarations that only contain a
> root element name
> 4. Frequent throwing of ArrayIndexOutOfBoundsExceptions when
> encountering various kinds of well-formedness errors
> 5. It treats <name/> and <name></name> differently. For <name></name>
> it calls characters() between startElement and endElement and sets
> length to 0.
> Arguably 1 and 5 are acceptable. I'd love to hear peoples' opinions
> about 5. Is this legitimate?
i think 5. is fine and smart hack to signal out of band information. i
use the same approach in XPP3 XmlSerializer to tell it what kind of
output i want i.e startTag();text("")*;endTag().
The best way to predict the future is to invent it - Alan Kay