• To: Henri Sivonen <hsivonen@i...>
• Subject: Re: Have JDOM / XOM / etc. failed? If so, why?
• From: Chris Burdess <d09@h...>
• Date: Fri, 31 Mar 2006 10:27:57 +0100
• Cc: xml-dev <xml-dev@l...>
• In-reply-to: <EE9176F3-ED3F-4351-84EC-3AAD2E47333A@i...>
• References: <BAY107-W3141174C75D52E999860B99D10@p...> <EE9176F3-ED3F-4351-84EC-3AAD2E47333A@i...>

Henri Sivonen wrote:
> ... However, DOM was poison I already knew from JavaScript.

I think it's worth pointing out at this stage that JavaScript  
programmers don't appear to seek or design alternatives to DOM at all.

> ... GNU JAXP had a fatal NullPointerException crasher, and I was  
> unable to figure out how the null got there. In the end, we indeed  
> had to switch implementations to Xerces.)

Is this still an issue? If so please file a PR for it, we can't fix  
what we don't know about.
-- 
ç?¬ Chris Burdess
   "They that can give up essential liberty to obtain a little safety
   deserve neither liberty nor safety." - Benjamin Franklin

• Follow-Ups:
  • DOM's javascript roots (was Re: Have JDOM / XOM / etc. failed?)
    • From: Tatu Saloranta <cowtowncoder@y...>

• References:
  • Have JDOM / XOM / etc. failed? If so, why?
    • From: "Michael Champion" <michael.champion@h...>
  • Re: Have JDOM / XOM / etc. failed? If so, why?
    • From: Henri Sivonen <hsivonen@i...>

• Prev by Date: Re: Have JDOM / XOM / etc. failed? If so, why?
• Next by Date: RE: Have JDOM / XOM / etc. failed? If so, why?
• Previous by thread: Re: Have JDOM / XOM / etc. failed? If so, why?
• Next by thread: DOM's javascript roots (was Re: Have JDOM / XOM / etc. failed?)
• Index(es):
  • Date
  • Thread