Re: Attribute values with unresolved entities

[email protected] (Elliotte Harold) writes:
>I don't see a clean solution here. Suggestions are appreciated, but I 
>think we do need to address this case in the JavaDocs. I think I'm 
>leaning toward throwing an exception, but others may feel differently.

I don't think there is a clean solution here - this is a direct result
of treating attributes as strings when they have their own complexities.

I can live with an exception, though I kind of wonder what would have
happen if an attribute happens to contain multiple unresolved entities
and how best to report that. 

Given the nature of the API, I would suggest fixing this one in
documentation only.  

(In a sense, I fixed this by changing the nature of the event pattern in
my MOE work, but that kind of solution is not appropriate in this
context.  If SAX were to start clean, I'd propose fixing this at a
structural level, but I don't think that makes sense today.  A lot of
people prefer SAX's apparent simplicity in this area in any case.)

Simon St.Laurent
http://simonstl.com


-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297
_______________________________________________
List: sax-devel, [email protected]
See:  http://www.saxproject.org/
https://lists.sourceforge.net/lists/listinfo/sax-devel