Berin Loritsch wrote:
>
> Peter, you mentioned in another thread that the DefaultConfigurationBuilder
> was altered in a way that broke your code. I think you even included a
> ClassicConfigurationBuilder to provide a compatibility layer. Looking back
> (hindsight is always 20/20) we should make the DefaultConfigurationBuilder
> the NamespacedConfigurationBuilder, and promote ClassicConfigurationBuilder
> to DefaultConfigurationBuilder.
>
> This will make the change backwards compatible while allowing namespaces
> to be serialized as well.
Would the enclosed diff file make you happy with the Configuration package?
Basically, it is moving what is currently called SAXConfigurationHandler to
NamespacedSAXConfigurationHandler and ClassicSAXConfigurationHandler to
SAXConfigurationHandler. There are also changes to make the default XMLReader
used by the ConfigurationBuilder to be non-namespace aware (as it was previously).
However, the user may turn on namespace awareness if desired. Lastly, the
getHandler() method checks the parser to see if it is configured to be
namespace aware--and if so return the NamespacedSAXConfigurationHandler.
The only other thing I can think of is do we want to deprecate the default
constructor on DefaultConfigurationHandler in favor of the boolean version?
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
