>>>>> [email protected]:

> I think you should take a look on pax-jdbc-config.

> It can simplify a lot your stuff.

It will certainly simplify this project (and make it less bound to
postgresql), and I will try it there:
 https://github.com/steinarb/sonar-collector

But for the projects that prompted the blog post there probably won't be
much gain (most of the code is releated to liquibase and I would have
had to have 3 OSGi bundles anyway (one for the schema, one for test data
and one for initial data i a production base), the code to connect to a
base is about the same number of lines as the config, so it would boil
down to a preference between code and config (where I usually land on
code), and in addition the database service proved a nice place to put
the SQL statements that are different between derby and PostgreSQL)
 https://github.com/steinarb/authservice
 https://github.com/steinarb/ukelonn
 https://github.com/steinarb/handlereg

(changing to pax-jdbc-config *would* make it simpler to use different
databases and re-use the liquibase scripts, e.g. use h2 for the test
database and MySQL for the production base, but having that flexibility
isn't important to me for these projects)

Reply via email to