Use DefaultConfigurationBuilder instead; this class
provides the same features as ConfigurationFactory plus some more; it can
also process the same configuration definition files.
Use DefaultConfigurationKey
instead. It is associated with a DefaultExpressionEngine and thus
can produce correct keys even if key separators have been changed.
Adding new properties is now to a major part delegated to the
ExpressionEngine associated with this configuration instance.
This method will no longer be called. Developers who want to modify the
process of adding new properties should consider implementing their own
expression engine.
Adding new properties is now to a major part delegated to the
ExpressionEngine associated with this configuration instance.
This method will no longer be called. Developers who want to modify the
process of adding new properties should consider implementing their own
expression engine.
Adding new properties is now to a major part delegated to the
ExpressionEngine associated with this configuration instance.
This method will no longer be called. Developers who want to modify the
process of adding new properties should consider implementing their own
expression engine.
Property keys are now evaluated by the expression engine
associated with the configuration; this method will no longer be called.
If you want to modify the way properties are looked up, consider
implementing you own ExpressionEngine implementation.