Issue 65845 - configuration should support IndexContainer/Access
Summary: configuration should support IndexContainer/Access
Status: ACCEPTED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 2.0.3
Hardware: All All
: P3 Trivial (vote)
Target Milestone: AOO Later
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-29 07:58 UTC by andreas.schluens
Modified: 2017-05-20 11:31 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description andreas.schluens 2006-05-29 07:58:03 UTC
For our new feature "configured multi pathes" we need a configuration schema (and 
API) which supports an IndexContainer/Access. The following requirements exists:

a) config values must support merging of data (add, replace, modify, fuse etcpp)
b) order of values is importent (at least the order of different configuration layers must 
be stable ... ordered values inside the same layer is not a request).
c) using of index based placeholder tags isnt an option
The user of this feature is interested only on "named-value" pairs.
d) such index container must support simple (e.g. string, int, bool) and complex 
(structs, stringlist) data types.
Comment 1 Stephan Bergmann 2006-05-29 12:59:33 UTC
(d) is probably not too important, as a simple datatype can trivially be wrapped
in a group with one property.
Comment 2 Stephan Bergmann 2006-07-04 08:06:22 UTC
@as:  This is no longer needed urgently, right?
Comment 3 andreas.schluens 2006-07-04 10:13:45 UTC
AS->SB: right.
It will be required only in case any of our features need realy an ordered access ...
Till now all features dont such access ....
Please stay tuned .-)
Comment 4 Marcus 2017-05-20 11:31:39 UTC
Reset assigne to the default "issues@openoffice.apache.org".