Quite interesting, but I didn't understand few things. Bret Pettichord wrote: > Using JRuby, we solved the problem in a novel way, by leveraging our > existing WATIR codebase that was used for functional tests. We > grafted a new backend onto WATIR (easier than it sounds, actually) > that talks not to IE but to the Apache Commons HTTPClient (Java) and > uses the NekoHTML parser (Java) to generate an XML DOM tree (Java). > We have a Ruby layer that emulates enough of the IE DOM on top of > that to allow WATIR to work just fine. So here we need Apache httpclient, NekoHTML and some Ruby component. Does this Ruby component expose IEBrowser? If yes, Does not it conflict with existing IE object? Do one need to change watir lib to get this working, without conflicting with existing IE Object?
Thanks and Regards, Manish _______________________________________________ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
