Alasdair, gzun...@googlemail.com wrote on 07/19/2011 05:48:30 PM:
> > While it may defy your intuition it isn't something that is > guaranteed by the spec. > > To be fair, it's not just me... as you've pointed out, this question > is perennial and you've been answering it for years :-) Right. I didn't mean you specifically, but "one's intuition". :-) There's a lot about DOM (and many other W3C specs for that matter) that isn't intuitive. For example, (n instanceof Element) does not imply (n.getNodeType() == Node.ELEMENT_NODE). Usually behaves how you'd expect but no guarantee it will. Some node implementations implement multiple interfaces (e.g. [1]). > > In general JAXB objects are not guaranteed to be thread-safe > either. In particular, DOM is used by default for representing > wildcard content (i.e. unknown elements). > > I didn't know this, probably because the schema we used fully > specified the documents, so the generated Java has been relatively > clean and simple. > > Finally, I'd just like to thank you for your efforts over the years - > I really do appreciate Xerces and what it's been able to do for me. Thanks. > --------------------------------------------------------------------- > To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org > For additional commands, e-mail: j-users-h...@xerces.apache.org [1] http://markmail.org/message/ify2wid2ux355fqi Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: mrgla...@ca.ibm.com E-mail: mrgla...@apache.org
