NovusDataSourceContainer upgrade?

Kate Percival

Currently the NovusDataSourceContainer takes a single dataSourceCollection in its constructor (the ref bean metadata-collection).

This means that, because India (WLIN) and Malaysia (WLMY) have access to UK data, all the WLIN and WLMY collection sets have to be included in the UK_SMG_COLL_METADATA, which further means that the WLUK app has to wade through all the IN/MY collection sets (to which our users have no access) each time we go to do billing.

I would like to see standalone IN_SMG_COLL_METADATA and MY_SMG_COLL_METADATA, so what's the simplest way of getting the ref bean metadata-collection to read in UK data as well as its own?

Emiliano Claria

The DataSourceContainer that is used to configure where the list of datasources is loaded from is only used from a DataSourceService implementation. So you could use CompositeDataSourceService to allow for a merged behaviour of two different DataSourceService implementations that use different DataSourceContainers, each pointing to a different collection. CPW and WLAUNZ do a similar thing caused by the need of using two different CSLoc domains, but if you look at the configuration, you'll see that they are getting a "merged" behaviour from two different DataSourceContainers.

By doing this, there wouldn't be any gain whatsoever since every call to the DataSourceService will represent two calls to InPlan, thus increasing the actual response time (probably, I haven't actually measured it)

A possible solution would be to replicate the way that CompositeDataSourceService behaves for DataSourceContainer, allowing it to wrap two different DataSourceContainers, each pointing to a different collection to get the list from.