Re: [HtmlUnit] HTML DOM implementation

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

Mike Bresnahan wrote:
>>I agree that XPath is really useful. Almost all the XPath
>>implementations I know (apache JXPath, Jaxen) support plugging in custom
>>models. The XPath implementation that comes as part of Xerces (never
>>used) probably doesnt. In any case one can assume that w3c DOM is
>>already implemented, while everything else requires more work.
>>
>>That indeed speaks for either implementing the w3c DOM interfaces (why
>>not?), or leaving everything as is, IMO.
> 
> 
> I guess I don't care which XPath implementation is used.  I wasn't actually
> aware of any other than the one that comes with xerxes.   How does the
> custom model plugging work with JXPath and Jaxen?  How much work would it be
> to plug in HtmlUnit's current data structure?

implementing a custom navigator (Jaxen terminology) is quite easy (like
1 or 2 hours). JXPath should be no different.

For using XPath with HtmlUnit as is there is no work required, because
the w3c DOM is accessible from the HtmlPage. Of course, thre is always
the mapping between Elements and HtmlElements which has to be done,
depending which one you need.

> 
> Mike
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An INetU Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
> INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> _______________________________________________
> HtmlUnit-develop mailing list
> Htm...@li...
> https://lists.sourceforge.net/lists/listinfo/htmlunit-develop
>