|
From: Maxim F. <tpa...@gm...> - 2009-06-06 16:23:00
|
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 > |