xmlunit-general — Everything XMLUnit ;0)

[Xmlunit-general] [ANN] XMLUnit for Java 1.3 Released

[Stefan B. <bo...@ap...>]

This new release of XMLUnit for Java fixes a few bugs and provides a new
option to control what happens when the documents that are compared
contain two XML elements that cannot be matched against each other.

The release is available in source and binary form at
<https://sourceforge.net/projects/xmlunit/files/xmlunit%20for%20Java/XMLUnit%20for%20Java%201.3/>,
checksums and OpenPGP signatures should be downloaded from
<http://xmlunit.sourceforge.net/checksums/>.

Re: [Xmlunit-general] Custom Qualifier

[Stefan B. <bo...@ap...>]

Hmm,

On 2009-09-18, Virat Gohil <vir...@gm...> wrote:

> http://sourceforge.net/tracker/?func=detail&aid=2758280&group_id=23187&atid=377768

given that I'm currently spending way too much time on Ant to actually
get something done on XMLUnit2 and given that two people have
encountered

http://sourceforge.net/tracker/?func=detail&aid=2807167&group_id=23187&atid=377768

by now it may be a good idea to implement Virat's suggested fix with a
new option and release XMLUnit-Java 1.3.  I'll see whether I can find
some spare time next week.

Stefan

Re: [Xmlunit-general] Custom Qualifier

[Stefanos K. <ste...@im...>]

Wow, thanks for the superfast reply.

This worked for me.

Greatly appreciated

Virat Gohil escribió:
> Hi Stefanos,
>
> I think you are facing the effects of the following defect:
>
> http://sourceforge.net/tracker/?func=detail&aid=2758280&group_id=23187&atid=377768 
> <http://sourceforge.net/tracker/?func=detail&aid=2758280&group_id=23187&atid=377768>
>
> You may use the fix provided in the discussion unless you do not have 
> any code depending on the current behavior.
>
> Thanks,
>
> Virat
>
>
>
> On Fri, Sep 18, 2009 at 1:01 PM, Stefanos Kollias <ste...@im... 
> <mailto:ste...@im...>> wrote:
>
>     Hi there
>
>     I have been trying to work out how to get xmlunit to do what I want.
>
>     I have the following xml
>
>     String xml1 = "<parent><child id=\"1\">value1</child><child
>     id=\"2\">value2</child></parent>";
>     String xml2 = "<parent><child id=\"3\">value3</child><child
>     id=\"1\">value1 changed</child></parent>";
>
>     What I want is to make xmlunit find a differences between elements
>     that
>     have the same id (1) and inform me of missing or new elements (2,3)
>     using the id attribute.
>
>     I have implemented a custom qualifier that returns false if the
>     element
>     tag names dont match or if the ids dont match but xmlunit doesnt
>     seem to
>     be taking notice of it.
>     I have also tried the ElementNameAndAttributeQualifier passing "id" in
>     the constructor but I get the same result.
>
>     What it does is
>
>     Expected text value 'value1' but was 'value1 changed' - comparing
>     <child
>     ...>value1</child> at /parent[1]/child[1]/text()[1] to <child
>     ...>value1
>     changed</child> at /parent[1]/child[2]/text()[1]
>     Expected sequence of child nodes '0' but was '1' - comparing
>     <child...>
>     at /parent[1]/child[1] to <child...> at /parent[1]/child[2]
>     Expected sequence of child nodes '1' but was '0' - comparing
>     <child...>
>     at /parent[1]/child[2] to <child...> at /parent[1]/child[1]
>     Expected attribute value '2' but was '3' - comparing <child id="2"...>
>     at /parent[1]/child[2]/@id to <child id="3"...> at
>     /parent[1]/child[1]/@id
>     Expected text value 'value2' but was 'value3' - comparing <child
>     ...>value2</child> at /parent[1]/child[2]/text()[1] to <child
>     ...>value3</child> at /parent[1]/child[1]/text()[1]
>
>     How can I get xmlunit to say find the first difference and also inform
>     me that node child id="2" is missing and that child id="3" is new
>
>     Any help would be greatly appreciated
>
>     Thanks in advance
>
>     --
>     Stefanos Kollias
>     Departamento de Enxeñería do Software
>
>     ste...@im... <mailto:ste...@im...>
>     ----------------------------------------------------------------------
>     imaxin|software
>     Salgueiriños de Abaixo 11, L6
>
>     15703 Santiago de Compostela
>
>     Voz +34 981 554 068 Fax +34 981 554 988
>     im...@im... <mailto:im...@im...>
>     ----------------------------------------------------------------------
>     www.imaxin.com <http://www.imaxin.com>
>
>
>     ------------------------------------------------------------------------------
>     Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
>     is the only developer event you need to attend this year.
>     Jumpstart your
>     developing skills, take BlackBerry mobile applications to market
>     and stay
>     ahead of the curve. Join us from November 9&#45;12, 2009. Register
>     now&#33;
>     http://p.sf.net/sfu/devconf
>     _______________________________________________
>     Xmlunit-general mailing list
>     Xml...@li...
>     <mailto:Xml...@li...>
>     https://lists.sourceforge.net/lists/listinfo/xmlunit-general
>
>


-- 
Stefanos Kollias
Departamento de Enxeñería do Software

ste...@im...
---------------------------------------------------------------------- 
imaxin|software
Salgueiriños de Abaixo 11, L6

15703 Santiago de Compostela

Voz +34 981 554 068 Fax +34 981 554 988
im...@im...
---------------------------------------------------------------------- 
www.imaxin.com

Re: [Xmlunit-general] Custom Qualifier

[Virat G. <vir...@gm...>]

Hi Stefanos,

I think you are facing the effects of the following defect:

http://sourceforge.net/tracker/?func=detail&aid=2758280&group_id=23187&atid=377768

You may use the fix provided in the discussion unless you do not have any
code depending on the current behavior.

Thanks,

Virat



On Fri, Sep 18, 2009 at 1:01 PM, Stefanos Kollias <ste...@im...>wrote:

> Hi there
>
> I have been trying to work out how to get xmlunit to do what I want.
>
> I have the following xml
>
> String xml1 = "<parent><child id=\"1\">value1</child><child
> id=\"2\">value2</child></parent>";
> String xml2 = "<parent><child id=\"3\">value3</child><child
> id=\"1\">value1 changed</child></parent>";
>
> What I want is to make xmlunit find a differences between elements that
> have the same id (1) and inform me of missing or new elements (2,3)
> using the id attribute.
>
> I have implemented a custom qualifier that returns false if the element
> tag names dont match or if the ids dont match but xmlunit doesnt seem to
> be taking notice of it.
> I have also tried the ElementNameAndAttributeQualifier passing "id" in
> the constructor but I get the same result.
>
> What it does is
>
> Expected text value 'value1' but was 'value1 changed' - comparing <child
> ...>value1</child> at /parent[1]/child[1]/text()[1] to <child ...>value1
> changed</child> at /parent[1]/child[2]/text()[1]
> Expected sequence of child nodes '0' but was '1' - comparing <child...>
> at /parent[1]/child[1] to <child...> at /parent[1]/child[2]
> Expected sequence of child nodes '1' but was '0' - comparing <child...>
> at /parent[1]/child[2] to <child...> at /parent[1]/child[1]
> Expected attribute value '2' but was '3' - comparing <child id="2"...>
> at /parent[1]/child[2]/@id to <child id="3"...> at /parent[1]/child[1]/@id
> Expected text value 'value2' but was 'value3' - comparing <child
> ...>value2</child> at /parent[1]/child[2]/text()[1] to <child
> ...>value3</child> at /parent[1]/child[1]/text()[1]
>
> How can I get xmlunit to say find the first difference and also inform
> me that node child id="2" is missing and that child id="3" is new
>
> Any help would be greatly appreciated
>
> Thanks in advance
>
> --
> Stefanos Kollias
> Departamento de Enxeñería do Software
>
> ste...@im...
> ----------------------------------------------------------------------
> imaxin|software
> Salgueiriños de Abaixo 11, L6
>
> 15703 Santiago de Compostela
>
> Voz +34 981 554 068 Fax +34 981 554 988
> im...@im...
> ----------------------------------------------------------------------
> www.imaxin.com
>
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Xmlunit-general mailing list
> Xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlunit-general
>

[Xmlunit-general] Custom Qualifier

[Stefanos K. <ste...@im...>]

Hi there

I have been trying to work out how to get xmlunit to do what I want.

I have the following xml

String xml1 = "<parent><child id=\"1\">value1</child><child 
id=\"2\">value2</child></parent>";
String xml2 = "<parent><child id=\"3\">value3</child><child 
id=\"1\">value1 changed</child></parent>";

What I want is to make xmlunit find a differences between elements that 
have the same id (1) and inform me of missing or new elements (2,3) 
using the id attribute.

I have implemented a custom qualifier that returns false if the element 
tag names dont match or if the ids dont match but xmlunit doesnt seem to 
be taking notice of it.
I have also tried the ElementNameAndAttributeQualifier passing "id" in 
the constructor but I get the same result.

What it does is

Expected text value 'value1' but was 'value1 changed' - comparing <child 
...>value1</child> at /parent[1]/child[1]/text()[1] to <child ...>value1 
changed</child> at /parent[1]/child[2]/text()[1]
Expected sequence of child nodes '0' but was '1' - comparing <child...> 
at /parent[1]/child[1] to <child...> at /parent[1]/child[2]
Expected sequence of child nodes '1' but was '0' - comparing <child...> 
at /parent[1]/child[2] to <child...> at /parent[1]/child[1]
Expected attribute value '2' but was '3' - comparing <child id="2"...> 
at /parent[1]/child[2]/@id to <child id="3"...> at /parent[1]/child[1]/@id
Expected text value 'value2' but was 'value3' - comparing <child 
...>value2</child> at /parent[1]/child[2]/text()[1] to <child 
...>value3</child> at /parent[1]/child[1]/text()[1]

How can I get xmlunit to say find the first difference and also inform 
me that node child id="2" is missing and that child id="3" is new

Any help would be greatly appreciated

Thanks in advance

-- 
Stefanos Kollias
Departamento de Enxeñería do Software

ste...@im...
---------------------------------------------------------------------- 
imaxin|software
Salgueiriños de Abaixo 11, L6

15703 Santiago de Compostela

Voz +34 981 554 068 Fax +34 981 554 988
im...@im...
---------------------------------------------------------------------- 
www.imaxin.com

Re: [Xmlunit-general] How to get it running in Visual Studio 2008

[Maxim F. <tpa...@gm...>]

Hello Henric.
Welcome to XMLUnit Community!
Could you describe scenario for which you want to use XMLUnit, Please?
In general there is no any settings required for XMLUnit you just add
reference to XMLUnit dll from "Add Reference" dialog and use it in your
NUnit tests.
With kind regards,
Maxim Filimonov

2009/8/17 Henrik Andersson <hen...@ap...>

>  Hi everyone !
>
> I’m a tester than don’t has that much experience in software development. I
> was out on the internet and see that xmlunit will solve my problems.
>
>
>
> So how do I ‘install’ and make it running in my Visual Studio 2008.  Where
> do I put my file, my setting ?
>
>
>
> Thanks   !
>
>
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Xmlunit-general mailing list
> Xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlunit-general
>
>

[Xmlunit-general] How to get it running in Visual Studio 2008

[Henrik A. <hen...@ap...>]

Hi everyone !

I'm a tester than don't has that much experience in software
development. I was out on the internet and see that xmlunit will solve
my problems. 

 

So how do I 'install' and make it running in my Visual Studio 2008.
Where do I put my file, my setting ?

 

Thanks   !

 

Re: [Xmlunit-general] Help me package xmlunit 1.2 for Debian

[Stefan B. <bo...@ap...>]

On 2009-07-29, Ludovic Claude <lud...@la...> wrote:

> I'm trying to package xmlunit for Debian.
> My problem is that xmlunit is using the xsl for Docbook version 1.72,
> and Debian has packaged Docbook 1.73.2.

That's not quite true.  The build file talks about 1.72 since that was
the first version I used but I'm pretty sure I've used 1.73.2 when I
re-created the user guide for XMLUnit 1.2 (since this is the only
version I can currently find on the machine I used to create the
release).

> When I run the ant build against this version, I get the following
> error messages:

>      [xslt] : Warning!
> file:/usr/share/xml/docbook/stylesheet/nwalsh/html/autoidx.xsl: line
> 476: L'attribut 'href' est à l'extérieur de l'élément.

I don't speak french but I think I've seen similar messages as well.  It
turned out to not be a problem with the stylesheets but with the XSLT
processor I used.  In my case I ensured I had a recent version of Xalan
when building the userguide (2.7.1 at that time) since the XSLT
transformers of JDK 1.4 or even worse 1.5 and later couldn't work with
the stylesheets.

I'd assume xsltproc or saxon would work as well - but you'd need to
modify the build file to use xsltproc.

Stefan

[Xmlunit-general] Help me package xmlunit 1.2 for Debian

[Ludovic C. <lud...@la...>]

Hello,

I'm trying to package xmlunit for Debian.
My problem is that xmlunit is using the xsl for Docbook version 1.72,
and Debian has packaged Docbook 1.73.2. When I run the ant build against
this version, I get the following error messages:

users-guide-html:
    [mkdir] Created dir:
/home/ludo/Projects/onLaunchpad/uj/build-area/xmlunit-1.2/build/doc/userguide/html
     [xslt] Transforming into
/home/ludo/Projects/onLaunchpad/uj/build-area/xmlunit-1.2/build/doc/userguide/html
     [xslt] Processing
/home/ludo/Projects/onLaunchpad/uj/build-area/xmlunit-1.2/src/user-guide/XMLUnit-Java.xml
to
/home/ludo/Projects/onLaunchpad/uj/build-area/xmlunit-1.2/build/doc/userguide/html/XMLUnit-Java.html
     [xslt] Loading stylesheet
/usr/share/xml/docbook/stylesheet/nwalsh/html/chunk.xsl
     [xslt] : Warning!
file:/usr/share/xml/docbook/stylesheet/nwalsh/html/autoidx.xsl: line
476: L'attribut 'href' est à l'extérieur de l'élément.
     [xslt] : Warning!
file:/usr/share/xml/docbook/stylesheet/nwalsh/html/autoidx.xsl: line
514: L'attribut 'href' est à l'extérieur de l'élément.
     [xslt] : Warning!
file:/usr/share/xml/docbook/stylesheet/nwalsh/html/autoidx.xsl: line
537: L'attribut 'href' est à l'extérieur de l'élément.
     [xslt] : Warning!
file:/usr/share/xml/docbook/stylesheet/nwalsh/html/callout.xsl: line
105: L'attribut 'href' est à l'extérieur de l'élément.
     [xslt] : Warning!
file:/usr/share/xml/docbook/stylesheet/nwalsh/html/xref.xsl: line 177:
L'attribut 'href' est à l'extérieur de l'élément.
     [xslt] : Warning!
file:/usr/share/xml/docbook/stylesheet/nwalsh/html/xref.xsl: line 968:
L'attribut 'href' est à l'extérieur de l'élément.
     [xslt] : Warning!
file:/usr/share/xml/docbook/stylesheet/nwalsh/html/inline.xsl: line 88:
L'attribut 'href' est à l'extérieur de l'élément.
     [xslt] : Warning!
file:/usr/share/xml/docbook/stylesheet/nwalsh/html/inline.xsl: line 129:
L'attribut 'href' est à l'extérieur de l'élément.
     [xslt] : Warning!
file:/usr/share/xml/docbook/stylesheet/nwalsh/html/inline.xsl: line 153:
L'attribut 'href' est à l'extérieur de l'élément.
     [xslt] : Warning!
file:/usr/share/xml/docbook/stylesheet/nwalsh/html/inline.xsl: line 679:
L'attribut 'href' est à l'extérieur de l'élément.
     [xslt] : Warning!
file:/usr/share/xml/docbook/stylesheet/nwalsh/html/inline.xsl: line 894:
L'attribut 'href' est à l'extérieur de l'élément.
     [xslt] : Warning!
file:/usr/share/xml/docbook/stylesheet/nwalsh/html/inline.xsl: line
1019: L'attribut 'href' est à l'extérieur de l'élément.
     [xslt] : Warning!
file:/usr/share/xml/docbook/stylesheet/nwalsh/html/inline.xsl: line
1150: L'attribut 'href' est à l'extérieur de l'élément.
     [xslt] : Warning!
file:/usr/share/xml/docbook/stylesheet/nwalsh/html/inline.xsl: line
1251: L'attribut 'href' est à l'extérieur de l'élément.
     [xslt] : Warning!
file:/usr/share/xml/docbook/stylesheet/nwalsh/html/glossary.xsl: line
257: L'attribut 'href' est à l'extérieur de l'élément.
     [xslt] : Warning!
file:/usr/share/xml/docbook/stylesheet/nwalsh/html/glossary.xsl: line
319: L'attribut 'href' est à l'extérieur de l'élément.
     [xslt] : Warning!
file:/usr/share/xml/docbook/stylesheet/nwalsh/html/annotations.xsl: line
117: L'attribut 'onClick' est à l'extérieur de l'élément.
     [xslt] : Error! Erreur de syntaxe dans '* or $generate.index != 0'.
     [xslt] : Error! (syntax error)
file:/usr/share/xml/docbook/stylesheet/nwalsh/html/autotoc.xsl: line
373: Erreur d'analyse de l'expression XPath '* or $generate.index != 0'.
     [xslt] : Error!
file:/usr/share/xml/docbook/stylesheet/nwalsh/html/autotoc.xsl: line
373: L'attribut obligatoire 'test' est absent.
     [xslt] : Error! Erreur de syntaxe dans '* or $generate.index != 0'.
     [xslt] : Error!
file:/usr/share/xml/docbook/stylesheet/nwalsh/html/autotoc.xsl: line
492: Erreur d'analyse de l'expression XPath '* or $generate.index != 0'.
     [xslt] : Error!
file:/usr/share/xml/docbook/stylesheet/nwalsh/html/autotoc.xsl: line
492: L'attribut obligatoire 'test' est absent.
     [xslt] : Fatal Error! Impossible de compiler la feuille de style
     [xslt] Failed to process null

It is complaining about the expression '* or $generate.index != 0' and a
missing 'test' attribute. I know nothing about Docbook, so I would
appreciate some help here.

The Debian packaging code is available here:
https://code.launchpad.net/~ludovicc

Thanks,

Ludovic

Re: [Xmlunit-general] XMLUnit2 Updates

[Stefan B. <bo...@ap...>]

On 2009-06-08, Maxim Filimonov <tpa...@gm...> wrote:

> Hi Stefan.I'm thinking more about xslt processors there a couple of them,
> but for validation huh.

Currently I don't plan to do more WRT XSLT than providing the inut
builder method that applies a transformation to a different source.

> Ok can you give me you next planned steps to be clear what i can
> start to implement?

API-wise I'd probably look at XPath next since the difference engine
is a complex beast and I'd like to feel my way around it first.

>From the implementation POV validation isn't really done, yet.  The
"old" XMLUnit validation code can do a few tricks we don't support in
XMLUnit2 for now:

* user specified resolvers for entities and/or URIs.  This is
  important IMHO, we need to figure out a nice API for it, though.  A
  setter or two might be enough, not sure.

* validation against a DTD for documents with no DOCTYPE declaration
  at all or even against a different DTD than the one of the DOCTYPE.
  Not sure how many people use the feature, but I'd like to at least
  keep the DOCTYPE-less use-case.

* tests

* some minor API details like the type of exception we want to throw
  if the user uses validateSchema on a DTD (we don't know how to do
  that).

Stefan

Re: [Xmlunit-general] XMLUnit2 Updates

[Stefan B. <bo...@ap...>]

On 2009-06-08, David Carver <dc...@st...> wrote:

> SAXON also runs on .NET and if you have the pay version, you get XML
> Schema Validation as well. So yes, there are alternatives besides just
> the Microsoft parser and validator.

Understood.

But until anybody writes a validtor implementation using SAXON.NET we
only have a single implementation and don't need to artifically split
the current class into two with one being abstract and the other being
the only subclass.

Stefan

Re: [Xmlunit-general] XMLUnit2 Updates

[David C. <dc...@st...>]

SAXON also runs on .NET and if you have the pay version, you get XML 
Schema Validation as well. So yes, there are alternatives besides just 
the Microsoft parser and validator.

Dave

Stefan Bodewig wrote:
> On 2009-06-06, Maxim Filimonov <tpa...@gm...> wrote:
>
>   
>> I'm looking at the .net version of Validator class now
>>     
>
> great
>
>   
>> and it's quite strange for me that this class contains
>> implementation of validation while java version is only abstract
>> class without knowledge of any validation API.
>>     
>
> In the Java case I knew there'd be (at least) two implementations,
> while I only expected a single implementation for .NET.  Do you
> envision a different validation API (I may just not be aware of
> alternatives so please bear with me) for .NET as well?
>
> If there is more than one implementation for .NET then we can and
> should split Validator the same way we did for Java, otherwise I'd
> feel it would be speculative design and defer the decision to later
> (YAGNI).
>
> If we leave Validator as it is it may be a good idea to remove the
> public constructor, though.  That way people would be forced to use
> the factory method and we'd be free to change the implementation
> later.
>
> If you feel my code is wrong, please don't hesitate to jump in and fix
> it 8-)
>
> Stefan
>
> ------------------------------------------------------------------------------
> OpenSolaris 2009.06 is a cutting edge operating system for enterprises 
> looking to deploy the next generation of Solaris that includes the latest 
> innovations from Sun and the OpenSource community. Download a copy and 
> enjoy capabilities such as Networking, Storage and Virtualization. 
> Go to: http://p.sf.net/sfu/opensolaris-get
> _______________________________________________
> Xmlunit-general mailing list
> Xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlunit-general
>
>   

Re: [Xmlunit-general] XMLUnit2 Updates

[Maxim F. <tpa...@gm...>]

Hi Stefan.I'm thinking more about xslt processors there a couple of them,
but for validation huh.
Think that you are right about only one way for .net.
Ok can you give me you next planned steps to be clear what i can start to
implement?

2009/6/8 Stefan Bodewig <bo...@ap...>

> On 2009-06-06, Maxim Filimonov <tpa...@gm...> wrote:
>
> > I'm looking at the .net version of Validator class now
>
> great
>
> > and it's quite strange for me that this class contains
> > implementation of validation while java version is only abstract
> > class without knowledge of any validation API.
>
> In the Java case I knew there'd be (at least) two implementations,
> while I only expected a single implementation for .NET.  Do you
> envision a different validation API (I may just not be aware of
> alternatives so please bear with me) for .NET as well?
>
> If there is more than one implementation for .NET then we can and
> should split Validator the same way we did for Java, otherwise I'd
> feel it would be speculative design and defer the decision to later
> (YAGNI).
>
> If we leave Validator as it is it may be a good idea to remove the
> public constructor, though.  That way people would be forced to use
> the factory method and we'd be free to change the implementation
> later.
>
> If you feel my code is wrong, please don't hesitate to jump in and fix
> it 8-)
>
> Stefan
>
>
> ------------------------------------------------------------------------------
> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
> looking to deploy the next generation of Solaris that includes the latest
> innovations from Sun and the OpenSource community. Download a copy and
> enjoy capabilities such as Networking, Storage and Virtualization.
> Go to: http://p.sf.net/sfu/opensolaris-get
> _______________________________________________
> Xmlunit-general mailing list
> Xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlunit-general
>

Re: [Xmlunit-general] XMLUnit2 Updates

[Stefan B. <bo...@ap...>]

On 2009-06-06, Maxim Filimonov <tpa...@gm...> wrote:

> I'm looking at the .net version of Validator class now

great

> and it's quite strange for me that this class contains
> implementation of validation while java version is only abstract
> class without knowledge of any validation API.

In the Java case I knew there'd be (at least) two implementations,
while I only expected a single implementation for .NET.  Do you
envision a different validation API (I may just not be aware of
alternatives so please bear with me) for .NET as well?

If there is more than one implementation for .NET then we can and
should split Validator the same way we did for Java, otherwise I'd
feel it would be speculative design and defer the decision to later
(YAGNI).

If we leave Validator as it is it may be a good idea to remove the
public constructor, though.  That way people would be forced to use
the factory method and we'd be free to change the implementation
later.

If you feel my code is wrong, please don't hesitate to jump in and fix
it 8-)

Stefan

Re: [Xmlunit-general] XMLUnit2 Updates

[Maxim F. <tpa...@gm...>]

Hi Stefan.
I'm looking at the .net version of Validator class now and it's quite
strange for me that this class contains implementation of validation while
java version is only abstract class without knowledge of any validation API.

Why you decide to split them like this ? If it's error i can fix it by
splitting implementation with default microsoft parser to separate class
that extends Validator.

2009/5/27 Stefan Bodewig <bo...@ap...>

> Hi,
>
> I've added tests for the input builder sometime last week and learned
> that SAXSource.sourceToInputSource doesn't work for DOMSource - I
> haven't tried a STaXSource, yet.  No big problem but something to look
> out for.
>
> The API for validation I proposed is in place for both platforms.  The
> class encapsulating errors/warnings is called ValidationProblem
> (better names are always welcome) and now holds an enum property
> indicating whether it represents an error or a warning.
>
> There is no implementation of that API, yet.  I'll start with the JAXP
> 1.3 implementation and make the legacy jaxp13.Validator class use it.
>
> Stefan
>
>
> ------------------------------------------------------------------------------
> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
> is a gathering of tech-side developers & brand creativity professionals.
> Meet
> the minds behind Google Creative Lab, Visual Complexity, Processing, &
> iPhoneDevCamp as they present alongside digital heavyweights like Barbarian
> Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com
> _______________________________________________
> Xmlunit-general mailing list
> Xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlunit-general
>

Re: [Xmlunit-general] XMLUnit2 Updates

[Stefan B. <bo...@ap...>]

On 2009-05-27, Stefan Bodewig <bo...@ap...> wrote:

> There is no implementation of that API, yet.  I'll start with the JAXP
> 1.3 implementation and make the legacy jaxp13.Validator class use it.

Done.

Stefan

Re: [Xmlunit-general] XMLUnit2 Updates

[Stefan B. <bo...@ap...>]

On 2009-05-27, David Carver <dc...@st...> wrote:

> Thanks, for some reason I thought it was under LGPL, maybe that was
> the 1.0 code.

I haven't been around before 1.1, but I'm pretty sure all code has
always been Apache licensed.  The first revision of the license file
(Apache 1.1) in svn is revision 38 and the comment says "0.6 release".

Anyway.

> Anyways, Apache 2.0 license will help, but I think the big issue was
> pedigree concerns with the 1.0 code. However it looks like the 1.2
> code base has made it through IP review and is approved for
> use. 

Great.

Enjoy using XMLUnit and and finding bugs 8-)

Stefan

Re: [Xmlunit-general] XMLUnit2 Updates

[David C. <dc...@st...>]

Thanks, for some reason I thought it was under LGPL, maybe that was the 
1.0 code. Anyways, Apache 2.0 license will help, but I think the big 
issue was pedigree concerns with the 1.0 code. However it looks like the 
1.2 code base has made it through IP review and is approved for use. 
Helps if I do some checking before asking.

Dave

Stefan Bodewig wrote:
> On 2009-05-27, David Carver <dc...@st...> wrote:
>
>   
>> I'm wondering if we could also think of possibly dual licensing the
>> code base if there are significant portions being rewritten.
>>     
>
> I have already changed the license of the new code to Apache
> License 2.0.
>
>   
>> There are a couple of projects at Eclipse that would would like to
>> use XMLUnit but unfortunately the current license isn't
>> compatible.
>>     
>
> Huh?  XMLUnit 1.x is under the Apache License 1.1 which I'd think
> should be pretty compatible with Eclipse.  They didn't have any
> problems with the license when it was used by the Apache libraries a
> few years ago.
>
>   
>> I look forward to testing out the new version,
>>     
>
> I'm not moving terribly fast right now.  Part of this is that I have
> only so much time (and Ant and Gump and ...) and part of the reason is
> that I want to leave room for others to participate 8-)
>
>   
>> and would love to use it on the Eclipse PsychoPath XPath 2.0 project
>> but current licensing keeps me from doing so.
>>     
>
> Which pieces of XMLUnit would you use?  The difference engine, XPath
> support, anything else?
>
> Stefan
>
> ------------------------------------------------------------------------------
> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT 
> is a gathering of tech-side developers & brand creativity professionals. Meet
> the minds behind Google Creative Lab, Visual Complexity, Processing, & 
> iPhoneDevCamp as they present alongside digital heavyweights like Barbarian 
> Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com 
> _______________________________________________
> Xmlunit-general mailing list
> Xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlunit-general
>
>   

Re: [Xmlunit-general] XMLUnit2 Updates

[David C. <dc...@st...>]

Stefan,

I'm wondering if we could also think of possibly dual licensing the code 
base if there are significant portions being rewritten. There are a 
couple of projects at Eclipse that would would like to use XMLUnit but 
unfortunately the current license isn't compatible. Almost anything 
other than the LGPL or GPL license would work. Of course there still 
might be pedigree concerns from the Eclipse IP lawyers.

I look forward to testing out the new version, and would love to use it 
on the Eclipse PsychoPath XPath 2.0 project but current licensing keeps 
me from doing so.

Dave


Stefan Bodewig wrote:
> Hi,
>
> I've added tests for the input builder sometime last week and learned
> that SAXSource.sourceToInputSource doesn't work for DOMSource - I
> haven't tried a STaXSource, yet.  No big problem but something to look
> out for.
>
> The API for validation I proposed is in place for both platforms.  The
> class encapsulating errors/warnings is called ValidationProblem
> (better names are always welcome) and now holds an enum property
> indicating whether it represents an error or a warning.
>
> There is no implementation of that API, yet.  I'll start with the JAXP
> 1.3 implementation and make the legacy jaxp13.Validator class use it.
>
> Stefan
>
> ------------------------------------------------------------------------------
> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT 
> is a gathering of tech-side developers & brand creativity professionals. Meet
> the minds behind Google Creative Lab, Visual Complexity, Processing, & 
> iPhoneDevCamp as they present alongside digital heavyweights like Barbarian 
> Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com 
> _______________________________________________
> Xmlunit-general mailing list
> Xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlunit-general
>
>   

Re: [Xmlunit-general] XMLUnit2 Updates

[Stefan B. <bo...@ap...>]

On 2009-05-27, David Carver <dc...@st...> wrote:

> I'm wondering if we could also think of possibly dual licensing the
> code base if there are significant portions being rewritten.

I have already changed the license of the new code to Apache
License 2.0.

> There are a couple of projects at Eclipse that would would like to
> use XMLUnit but unfortunately the current license isn't
> compatible.

Huh?  XMLUnit 1.x is under the Apache License 1.1 which I'd think
should be pretty compatible with Eclipse.  They didn't have any
problems with the license when it was used by the Apache libraries a
few years ago.

> I look forward to testing out the new version,

I'm not moving terribly fast right now.  Part of this is that I have
only so much time (and Ant and Gump and ...) and part of the reason is
that I want to leave room for others to participate 8-)

> and would love to use it on the Eclipse PsychoPath XPath 2.0 project
> but current licensing keeps me from doing so.

Which pieces of XMLUnit would you use?  The difference engine, XPath
support, anything else?

Stefan

[Xmlunit-general] XMLUnit2 Updates

[Stefan B. <bo...@ap...>]

Hi,

I've added tests for the input builder sometime last week and learned
that SAXSource.sourceToInputSource doesn't work for DOMSource - I
haven't tried a STaXSource, yet.  No big problem but something to look
out for.

The API for validation I proposed is in place for both platforms.  The
class encapsulating errors/warnings is called ValidationProblem
(better names are always welcome) and now holds an enum property
indicating whether it represents an error or a warning.

There is no implementation of that API, yet.  I'll start with the JAXP
1.3 implementation and make the legacy jaxp13.Validator class use it.

Stefan

Re: [Xmlunit-general] Custom Exceptions in .NET?

[Stefan B. <bo...@ap...>]

On 2009-05-13, Филимонов Максим Сергеевич <tpa...@gm...> wrote:

> I think maybe there is some additional value in wrapping
> SystemExceptions into XmlUnit exceptions:
> 1) We would be more decoupled from .net if we will wrap our exceptions
> with XmlUnit exception and can share code between java/.net in high
> level easily.

True.

> 3) Will be much easier to share tests , remember your idea , huh ? :)

tests, what tests? ;-)

> Also i want to suggest use another class not XMLUnit Exception maybe
> something like XMLUnitPersistanceException or something like that.

Right now the Java trunk has XMLUnitRuntimeException (happy to use a
different name) as the more general case and ConfigurationException
that is used to wrap the various JAXP ConfigurationException classes:
<http://xmlunit.svn.sourceforge.net/viewvc/xmlunit/trunk/xmlunit/src/main/java-core/net/sf/xmlunit/exceptions/>

Java 1.2 also has a specific XPathException.

We can invent new XMLUnitRuntimeException subclasses as we go IMHO.

Stefan

Re: [Xmlunit-general] Validation API for XMLUnit 2

[Stefan B. <bo...@ap...>]

On 2009-05-13, Филимонов Максим Сергеевич <tpa...@gm...> wrote:

> Hi Stefan.
> My comments below.

> 13.05.2009, в 8:06, Stefan Bodewig написал(а):

>> class ValidationError {
>>    readonly int line; // with a negative constant for UNKNOWN
>>    readonly int column; // ditto
>>
>>    readonly String message;
>> }

>> .NET knows warnings in addition to errors, I'm not sure how we should
>> handle them.

>> class ValidationResult {
>>    readonly bool valid;
>>    readonly Iterable/IEnumerable<ValidationError> errors;

> I think warning is important

OK

> what about use

> IEnumerable<ValidationWarning> warnings

> and

> ValidationError : ValidationWarning

> or

> ValidationWarning : ValidationIncostistency ,
> ValidationError:ValidationIncostistency?

Maybe an enum with Error and Warning and an attribute in
ValidationError would do (together with renaming the class)?

>> Since the Java code will be prettier if it uses different
>> implementations for DTDs and W3C Schema I suggest to add a factory
>> method

>> class Validator {
>>    static Validator forLanguage(String);

> What about pass enum not a string than user will know what validation
> sets are supported and didn't try to pass something not supported.

javax.xml.validation can be extended by additional libraries that add
support for new schema languages, see
<https://jaxp-sources.dev.java.net/nonav/docs/api/javax/xml/validation/SchemaFactory.html#newInstance(java.lang.String)>

I've successfully used RelaxNG
<http://stefan.samaflost.de/blog/en/oss/XMLUnit/relax_ng_validation_in_xmlunit.html>

An enum would limit the choices to the schema langauges we know at the
time of writing the enum, a string allows us to be forward compatible.

Stefan

Re: [Xmlunit-general] Custom Exceptions in .NET?

[Филимонов М. С. <tpa...@gm...>]

Hi Stefan.
I think maybe there is some additional value in wrapping  
SystemExceptions into XmlUnit exceptions:
1) We would be more decoupled from .net if we will wrap our exceptions  
with XmlUnit exception and can share code between java/.net in high  
level easily.
2) Not sure about this, but as i understood IOException can't be  
wrapper as Assertion Exception , maybe we will need some kind of  
functionality in future and it's nice to have such possibility IMO.
3) Will be much easier to share tests , remember your idea , huh ? :)

Also i want to suggest use another class not XMLUnit Exception maybe  
something like XMLUnitPersistanceException or something like that.
12.05.2009, в 8:09, Stefan Bodewig написал(а):

> Hi,
>
> I've implemented some basic builders for the most common input sources
> in trunk (both platforms).
>
> For the Java versions I've not yet wrapped the exceptions that may be
> thrown into XMLUnit-specific RuntimeException but will do so like I
> did in XMLUnit 1.x.
>
> For the .NET code the main reason for XMLUnit's own exception classes
> (checked exceptions) doesn't exist.  Is there still some additional
> value in wrapping exceptions in XMLUnit exceptions or do we simply not
> handle exceptions like XmlException or IOException at all?
>
> Stefan
>
> ------------------------------------------------------------------------------
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances!  
> Your
> production scanning environment may not be a perfect world - but  
> thanks to
> Kodak, there's a perfect scanner to get the job done! With the NEW  
> KODAK i700
> Series Scanner you'll get full speed at 300 dpi even with all image
> processing features enabled. http://p.sf.net/sfu/kodak-com
> _______________________________________________
> Xmlunit-general mailing list
> Xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlunit-general

Re: [Xmlunit-general] Validation API for XMLUnit 2

[Филимонов М. С. <tpa...@gm...>]

Hi Stefan.
My comments below.
13.05.2009, в 8:06, Stefan Bodewig написал(а):


> class ValidationError {
>    readonly int line; // with a negative constant for UNKNOWN
>    readonly int column; // ditto
>
>    readonly String message;
> }
>
> .NET knows warnings in addition to errors, I'm not sure how we should
> handle them.
>
> class ValidationResult {
>    readonly bool valid;
>    readonly Iterable/IEnumerable<ValidationError> errors;
> }
> I think warning is important what about use

> IEnumerable<ValidationWarning> warnings

> and

> ValidationError : ValidationWarning

> or

> ValidationWarning : ValidationIncostistency ,  
> ValidationError:ValidationIncostistency?
> class Validator {
>    String schemaURI; // should that be an URI instead? probably  
> wouldn't
>                      // work for DTDs then
>    Source[] schemaSources;
>
>    ValidationResult validateSchema();
>    ValidationResult validateInstance(Source);
> }
>
> Since the Java code will be prettier if it uses different
> implementations for DTDs and W3C Schema I suggest to add a factory
> method
>
> class Validator {
>    static Validator forLanguage(String);
> }
What about pass enum not a string than user will know what validation  
sets are supported and didn't try to pass something not supported.