From: Филимонов М. С. <tpa...@gm...> - 2009-05-13 15:38:26
|
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 |