Description
Currently the jdbc commands for the data sources create blueprint files from templates for some supported databases.
The problem with this is that we need to maintain these templates and have a quite tight coupling to these database implementations.
So if the database changes a class name we use we might even need to support two templates for the same database.
A better way would be to us pax-jdbc-config and pax-jdbc-pool. These modules allow to create datasources including pooling and XA support just by adding configurations.
The jdbc commands could help with that by providing a simple way to create or delete the configs. We can also provide features for the most common databases that install all needed bundles.