> Andy Clark wrote: > > BasicParserConfiguration recognizes "validation" feature, IMO it should not > > recognize "validation" feature as this class is supposed to be reusable as much > > as possible, and different applications are encouraged to write their custom > > Recognizing the value and using it are different things.
As per SAX, XMLReader does not _recognize_ a feature if it can't get or set http://www.saxproject.org/?selected=get-set (both) the value for. If XNI means _recognize_ in the same sense that means any configuration extending "BasicParserConfiguration" should allow to (capable of) get or set (both) any recognized feature of BasicParserConfiguration. But changing(setting) the value of feature won't have any effect on the behavior of parser. Any application using particular configuration (say _NonValidatingConfiguration_ or any Custom Configuration) won't be able to know the reason for not getting the desired behavior, after setting particular feature. One unclean solution would be to throw XMLConfigurationException for querying or setting the value for desired feature, even this means that particular feature is in the list of recognized feature but an exception is thrown when querying or setting the particular feature. Extending configuration has to remove the feature from the (base class) list of recognized features which is quite a burden for derived configuration. > And I think most applications assume that "validation" and > "namespaces" will always be accepted. I think differnt people will have different opinion. There are quite number of applications which do not really require "validation" but recognizing the feature in (abstract)base class adds it to the list of all derived (even non-validating) configurations. Thanks, Neeraj --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
