From: James A. <jam...@gm...> - 2009-03-28 20:18:24
|
Would ikvm work here? The only usage I'm aware of is Saxon - I've no experience with it myself. 2009/3/25 Stefan Bodewig <bo...@ap...>: > On 2009-03-24, Maxim Filimonov <tpa...@gm...> wrote: > >> I plan to use Xml Unit for .net in my current testing of XSLT processing as >> main testing framework. >> I have some experience with Java version of Xml Unit after i migrate to .net >> version i'm shocked a bit that so much difference between java and .net >> version exists. > > Once you dive deeper into it, you'll see that many features of the > Java version cannot be easily added without rewriting the difference > engine completely - the Java version uses DOM while the .NET version > uses a forward only pull parser, which makes things like > ElementQualifier very hard to implement. > > Current svn trunk contains some unreleased fixes for the .NET version, > BTW. > >> Java version is mature and solid and it contains real value to use it. >> .net version is not mature enough for us at least. >> I will port Java version of XPathNodeTracker and referenced items to make >> testing results more valuable. >> Is anybody interested in this solution to be shared ? > > Yes. > > There is a task on my ever growing TODO list that says "rewrite > XMLUnit.NET", but I have very little hope of ever getting there > without help of more people. > > Stefan > Things that spring to mind: 1) ikvm. The only usage that I'm aware of is Saxon, but thought I'd throw it out there. 2) ANTLR. Developed in Java; there is a C# version. Not sure how that was ported, but given the nature of the project, I'm curious if they managed to get some source-to-source translation thing going. I'm on the antlr-users list, so I'll ask there and let you know. Cheers, James |