Re: [HtmlUnit] HTML DOM implementation

[Christian S. <chr...@ne...>]

Mike Bowler wrote:
> Christian Sell wrote:
> 
>> I'd like to get back to this question, as it was not answered.
> 
> 
> I've actually been trying to respond but your ISP is blocking emails 
> coming from my ISP, apparently because of "net abuse" which my ISP 
> claims they can't do anything about.

you must be on packard bell!? I had a lengthy discussion with my 
provider, whether their spam strategy was appropriate - simply blocking 
out half the internet community... Anyway, my intention was never to 
send private email - the reply-to setting of this list caused it.

> 
>> Would it make sense to unify the HtmlElement and Element hierarchies? 
>> It seems to me there would be some potential for both maintenance and 
>> resource optimization.
> 
> 
> I assume from your last private email that NekoHTML can be configured to 
> build a DOM tree from HtmlElement classes rather than from the w3c DOM 
> classes.  Is this correct?  If so, where would I find information on it?
> 

well, I see 2 ways to achieve this:

1. Use Nekos SAX interface. This would allow you to build your own 
custom hierarchy without ever caring about the w3c interfaces.

2. Use the DOM interface. There is a property in neko/xerces that allows 
you to set the org.w3c.dom.Document implementation implementation class. 
That classes methods are called during parsing to create the individual 
nodes. Of course this would mean you have to implement the full 
org.w3c.dom interfaces.

The property name is
"http://apache.org/xml/properties/dom/document-class-name"

regards,
Christian