Hi Andy, I've looked at your proposal and it looks good to me. So here is my +1 to put it into next Xerces release.
The only catch is -- we plan to release Xerces next Wednesday.. Do you have enough time to implement your changes? Sorry for a short notice... -- Elena Litani / IBM Toronto Andy Clark wrote: > Therefore, I propose adding the following methods to the > org.apache.xerces.xni.parser.XMLComponent interface: > > /** > * Returns the default state for a feature, or null if this > * component does not want to report a default value for this > * feature. > */ > public Boolean getFeatureDefault(String featureId); > > /** > * Returns the default state for a property, or null if this > * component does not want to report a default value for this > * property. > */ > public Object getPropertyDefault(String propertyId); > > The one thing you might immediately question is my use > of a Boolean object instead of the boolean primitive. I > use this so that the component can state that it doesn't > care what the default value should be. This would be > used in situations where the component may recognize and > use a setting common to the parser configuration and/or > other components, but where it doesn't care what the > default is. > > And in fact, only the component that "introduces" the > setting should set its default value. For example, both > "validation" and "namespaces" are system wide settings > and the parser configuration sets the default value. A > lot of the components use these values but will take > whatever default value has been established. > > What do you think? Can we roll this change into the > codebase for Xerces 2.1.0? > > -- > Andy Clark * [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
