Oliver Heger a écrit :
Yes such a constructor should be added. However it may make sense to
keep the existing parameters also because we will need something like
this when the new configuration is to be integrated into
DefaultConfigurationBuilder.
On the other hand we could implement a facto
Emmanuel Bourg schrieb:
Oliver Heger a écrit :
I have added a new method to the NodeHandler interface for
distinguishing between the node types.
Great, will that work with the getKeys() iterator and the expression
engines ?
Yes, it should. A major part of the basic functionality provided by
Oliver Heger a écrit :
I have added a new method to the NodeHandler interface for
distinguishing between the node types.
Great, will that work with the getKeys() iterator and the expression
engines ?
Based on these changes I have created an initial implementation of
PreferencesConfigurati
Oliver Heger schrieb:
Emmanuel Bourg schrieb:
I'm trying to write a PreferencesConfiguration and I'm facing some
issues with the NodeHandler interface. NodeHandler assumes the
existence of container nodes and value nodes. However this is not true
for a Preferences tree, the only node available
Emmanuel Bourg schrieb:
I'm trying to write a PreferencesConfiguration and I'm facing some
issues with the NodeHandler interface. NodeHandler assumes the existence
of container nodes and value nodes. However this is not true for a
Preferences tree, the only node available is a container node (t
I'm trying to write a PreferencesConfiguration and I'm facing some
issues with the NodeHandler interface. NodeHandler assumes the existence
of container nodes and value nodes. However this is not true for a
Preferences tree, the only node available is a container node (the
Preferences object),
