A general implementation of the ChildRowDataProvider interface that can be used when child row data is provided by DataProviders that do not allow for easy name spacing of child row data. An example is container based child row data using the already existing container based data providers the call backs do not specify which container they refer to. This means a mechanism for linking child row updates to a parent row is required once you have multiple child rows open.

The mechanism used is simply "wrapping" the child row data provider in a wrapper class such as caplin.grid.dataprovider.expandable.ContainerChildRowDataProviderWrapper or caplin.grid.dataprovider.expandable.SL4BSubjectChildRowDataProviderWrapper. The use of these wrapping classes means any child row data provider calls need to be proxied on to all the wrapper classes when multiple child rows are open. In other words when a grid is closed all wrapper classes need to be told to terminateUpdates. This class generalises the proxy code so both the caplin.grid.dataprovider.expandable.SL4BSubjectChildRowDataProvider and caplin.grid.dataprovider.expandable.ContainerChildRowDataProvider can use common code.