Andy Clark wrote: > > Reviewing what is currently in Xerces2, checked into the > impl.v2.datatypes package, we have a datatype validator > factory interface for creating datatype instances and we > have a datatype validator interface for doing the actual > validation of datatype values. By using the factory design > pattern, we allow different datatype library implementations > to be used interchangeably by the parser. I see this as a > good thing. :) >
I am sorry, but it is not good - it is *great* thing, I think. :-) Thank you for it. I am looking forward to this. I think interchangeability of datatype validator implementation is very important and it is big step forward, from my point of view. I like it. I want it. :-) Datatype validator is needed while XML document is parsed from stream, validator is needed while manipulation of DOM or similar structure and validator is needed while manipulation of objects - beans generated for XML documents binding (like JAXB). Those are use cases, where datatype validator is used and it would be *very* nice to share one validator in all those use cases. And your interfaces could be good start for this. Did you looked at Kohsuke's Multi-Schema XML Validator (http://dcb.sun.com/practices/devnotebook/xml_msv.jsp, http://www.sun.com/software/xml/developers/multischema/)? What do you think about it? Could not it be reference implementation of your interfaces? And what do you think about separating interfaces from implementation? We would like to use it but without hard dependency on concrete (xerces) parser implementation. And we could depend just on JAXP and XNI. Best regards, Libor -- Libor Kramolis, Software Engineer | [EMAIL PROTECTED] NetBeans/Sun Microsystems, XML module | http://xml.netbeans.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
