I have been working on the Configuration system in the wms-merge branch and have run across the following in
DataStoreConfig:
By now just uses DataStoreFinder to find a new instance of a DataStore
capable of process <code>connectionParams</code>. In the future we can
see if it is better to cache or pool DataStores for performance, but
definitely we shouldn't maintain a single DataStore as instance
variable for synchronizing reassons
We do actually need to keep a single DataStore instance for the application: transaction and locking information depend on this. The DataStore is in charge of the synchronization issues surrounding its content.
The gt2 Catalog interface is supposed to manage the pool of DataStores according to namespace, and should gradually be able to supply the metadata we require for GeoServer.
Cheers,
Jody