My original idea was something like this:
Module foo:
list foo {
...
container service-data {
}
}
Module bar:
augment /foo:foo/foo:service-data {
uses bar-grouping;
}
list bar {
uses bar-grouping;
}
grouping bar-grouping {
...
}
The idea is to have multiple implementations similar the second module, so that multiple modules can augment the functionality of the first module.
And then have a generic piece of code in the first module that copies the data from instances of the list in the first module to instances of modules that augment it.
This turned out not to work with copy_tree (shared or not) - no error message, but nothing is copied.
Eventually, I suspected that maybe the change of namespace between the service-data container to whatever is inside it has caused this behavior.
To confirm, I moved the service-data container into the augmenting module and then copy was successful.
This is not ideal, as it requires a slightly less generic implementation.
For now, it seems as I can live with it, but been trying to think of alternatives at the same time.
